“Self-service in Practice” — Part 1
A Practical Look at the Entire Process
When a business decides to introduce a self-service system, there are usually many questions. What should the system do? What hardware is needed? Is there ready-made software, or does new software need to be developed? How will employees respond, and will customers even want to use it? The reason is simple: a self-service system is not a device that we install at a location, switch on, and forget about. It changes an existing process, connects various technical components, and requires new habits from both customers and staff. With this article, we are starting the “Self-service in Practice” series. In the following parts, we will present specific solutions and how they are implemented in different businesses. Before that, however, it is important
A Self-Service System Is Not Always a Kiosk
When we talk about self-service, most people imagine a kiosk for ordering and payment. That is just one of the possibilities.
A system can provide information, register visitors, manage a queue, or direct people to a specific service. Such solutions can also be used to send and receive parcels, documents, products, or car keys. They can manage a public laundry, parking, access to a location, or registration at a medical center.
Automation can also be entirely software-based. For example, one platform can transfer information to another without an employee entering it again.
Each of these solutions has its own logic and technical requirements. What they have in common is that the choice should not start with the device. First, we need to clearly define which process we want to change and why.
Implementation Does Not End with Installation
Hardware is only the visible part of the system. Behind it, there are usually several connected components that need to work as one.
In a restaurant, for example, the process may seem simple: the customer places an order, the kitchen receives it, and then the customer sees or hears that it is ready. However, behind these few actions there may be a payment system, fiscalization, point-of-sale and kitchen software, menu management, printers, displays, and notifications.
If one part of this chain stops working or transmits incorrect information, the problem affects the entire process.
Sometimes there is a ready-made solution that only needs to be configured. In other cases, adaptation, integration with existing software, or the development of new functionality is necessary. Something that looks like a small change on the screen may require additional logic, connections to external systems, and extensive testing.
That is why software development must be planned with realistic timelines and a realistic budget. A quick solution is rarely a good one when the operation of the entire location depends on it.
We Start with the Problem, Not the Device
Many inquiries begin with a solution that has already been chosen: “I want a kiosk,” “I want automated payment,” or “I want the system to replace a specific position.” Our work often begins by taking one step back and asking: “What problem are we actually trying to solve?”
It could be a lack of staff, an overloaded team, long queues, errors when taking orders, weak oversight, or the need for a service to be available outside working hours. Each of these problems requires a different approach. A kiosk is not a universal answer, and automation does not always mean removing people from the process.
The next step is to examine the user’s entire journey. How does the service begin? What does the customer do? How is the request processed? Who receives the information, and what do they need to do with it?
We also need to consider situations in which something goes wrong. What happens if the internet connection is interrupted, the payment is declined, the device stops working, or the customer does not understand the next step? Sometimes, during this discussion, it becomes clear that the original idea cannot be implemented as easily or as cheaply as expected. This is not a failure of the project. On the contrary, it is better to identify the limitations before making the investment.
In such cases, the project can start with a smaller scope. The solution is tested in a real environment, data is collected, and only then is it expanded.
Employees Are Part of the Implementation
One of the most common mistakes is to impose the new system. The device appears at the location, while employees find out at the last minute why it is there and what is expected of them.
If automation is presented as a threat to jobs or as yet another additional obligation, staff will have difficulty accepting it. And when employees do not trust the system, customers sense it immediately. The change must be explained in advance and demonstrated step by step. People need to know how the system will make their work easier, what their role will be, and how to respond if something does not go according to plan.
Self-service rarely means a complete absence of people. More often, it frees staff from repetitive tasks so that their time can be directed toward work where human involvement truly adds value.
The Customer Should Gain Convenience, Not a New Obligation
Users are already accustomed to self-service systems thanks to large restaurant and retail chains. This lowers the initial barrier, but it does not mean they will accept every solution.
Working with the system should be clear, fast, and logical. If the customer hesitates, goes through unnecessarily many screens, or is constantly looking for help, the system is not saving them time. It is simply assigning them part of the employee’s work.
The device’s location also matters. It should be easy to notice and placed where the process naturally begins. Even a well-designed system may remain unused if it is hidden, inconvenient, or does not match customer behavior at the specific location.
The business itself must show that it trusts the solution. When employees guide customers calmly and confidently, the new way of providing service is accepted more easily. If staff avoid the system, customers will soon start doing the same.
Someone Must Take Responsibility for the Change
Especially in smaller businesses, successful implementation requires a specific person to lead it. This may be the owner, manager, or an employee who knows the day-to-day work and has clear responsibility for the project.
This person is the link between the solution provider, staff, and customers. They monitor how the system works, collect feedback, and participate in the necessary adjustments.
Without such an internal owner, even a technically well-executed solution may gradually be abandoned. The system does not change habits on its own. Someone needs to demonstrate the new process, monitor whether it is being followed, and give people time to learn it.
The First Day Does Not Show the Final Result
A system may become technically operational on the day of installation. That does not mean implementation is complete.
Staff need to get used to the new process, customers need to accept it, and real-world operations almost always reveal details that were not visible during preliminary testing.
The first few weeks are a period of observation and adaptation. Some problems can be solved by changing the interface, relocating the device, providing additional training, or adjusting the internal organization.
However, not every problem should be explained by saying that “people are still getting used to it.” Sometimes the cause lies in the solution itself. Good integration requires us to observe what is happening, make adjustments, and, when necessary, change part of the original idea.
A system is technically implemented when all its components have been installed, connected, and tested. It is truly implemented when customers and staff begin using it calmly and it becomes a natural part of everyday work.
That is the difference between a functioning device and a functioning solution.
What’s Next in “Self-service in Practice”?
In the following parts, we will examine specific systems and installations that we or our partners are working on. These include ordering kiosks in restaurants, parking systems, registration at dental centers, solutions for leaving and collecting car keys, and professional laundry management.
We will also present information kiosks for medical centers, web platforms for internal orders, automatic transfer of orders from platforms such as Glovo, Wolt, and Bolt Food to restaurant software, as well as solutions that use video surveillance and artificial intelligence to monitor inventory and organization.
At first glance, these systems are very different. What they have in common is that they reduce the need for a person to perform the same repetitive activity. Sometimes the customer enters the information themselves. Sometimes one system transfers it to another. In other cases, the software notifies an employee only when intervention is needed. For SelfService.bg, self-service is not a catalog of devices. The work may include selecting and configuring hardware, software development, integration with existing systems, and coordinating the entire process until the solution is actually put into use.
The Best Ideas Often Come from the Business Itself.
People working on the ground know where time is lost, which actions are repeated, and where the process most often becomes difficult. Our task is to assess the idea, organize it, and help turn it into a solution that works not only in theory.
If your business has a process that is repeated every day and takes up your team’s time, you do not need to know in advance exactly how to automate it. You can contact SelfService.bg for a free initial consultation. We will examine the process from the perspective of both the business and the future user, and determine whether there is a ready-made solution, whether adaptation is necessary, or whether another approach should be considered.
