Small businesses do not hire someone to answer WhatsApp because they have extra room in the budget. They do it when the chat stops being one task among many and becomes a bottleneck: messages go unanswered, orders slip through, and customers do not come back.
I have seen that point up close. The question is not whether WhatsApp matters. It clearly does. The question is whether a full salary is the best answer for your business, or whether one person is covering for a process that needs to be organized differently.
The shop that assigned someone almost entirely to chat
I met a fast-food shop selling burgers, hot dogs, pepitos, and salchipapas. They work with about four people. The owner used to answer WhatsApp orders herself, on top of everything else involved in running the shop.
The volume got so overwhelming that they hired someone whose job is, roughly 90% of the time, answering messages. In practical terms, they are paying a full salary so the chat does not sit unattended.
They do not use Sotoban. At one point, the owner told me that they “do not work with order tickets.” I still do not fully understand what she meant, but the outcome is clear: orders still depend on one person chatting, taking notes, and passing information along in whatever way they manage internally.
I am not saying hiring is wrong. It can make sense when that person also handles complaints, sells, confirms complicated details, or covers other necessary work. But there is an important distinction: hiring someone to serve customers and help run the business is one thing; paying a full salary because repetitive orders have no clear workflow is another.
Before making that decision, look at one real week of conversations. Separate the messages that require judgment from the ones that repeat: catalog questions, prices, common modifications, addresses, payment method, and order status. That will show you whether you need another person or a different way for orders to come in and get organized.
The owner who could not grow through WhatsApp
Sotoban started with a pilot for another food business. Its owner came to me with a straightforward problem: lots of WhatsApp orders were coming in, they often got missed, and he could not give them enough attention. He did not feel he was losing only orders; he felt he was losing customers.
I offered him two paths. One was a custom solution, billed as a full development project. The other was software with a monthly fee. We ended up building the second option.
Today, that business handles an average of about 30 orders a week through the platform. Sotoban answers WhatsApp on the business’s behalf, takes the order and confirms it with the customer. The owner no longer has to watch the chat in order to put together every order. His role is to validate payment and dispatch it.
What stayed with me was something else he said: he had not been able to grow WhatsApp orders the way he wanted because he had no time left to attend them. Now, he felt he would have that room.
That does not mean software replaces the whole operation. Someone still needs to prepare the order, charge correctly, and deliver it. When a customer sends a Yappy or bank-transfer receipt, it arrives as an image and, by default, a person checks it against the bank. If the branch chooses that setup, the order is held before preparation until someone validates or rejects the payment, and either way the customer is told on WhatsApp.
But removing the owner’s obligation to live inside the chat changes what they can do during the day. They can focus on the register, dispatch, inventory, or the problems that actually need their judgment.
A delay does not feel small to the customer
I have seen this from the customer side too. One time I messaged several places to order food. One replied half an hour later. The others had not even answered by then. I ended up looking around and ordered McDonald’s through its app; I placed the order and it was at my home about 15 minutes later.
It was not that the other places had bad food. I never got to try it. They lost the chance because it took half an hour just to answer.
When you are buried in daily operations, it is easy to think, “I’ll reply in a minute.” But customers do not see the line, the register, the kitchen, or the delivery issue. They only see silence. When they have another option that lets them order immediately, they usually do not wait around for an open-ended reply.
Run the numbers from your operation, not from a promise
Do not start by asking whether a system costs less than a salary. Start by understanding what that salary, or the owner’s time, is buying today.
For one week, use a notebook or review your chats and ask:
- Who answers orders when the shop gets busy?
- How many messages are left for later because that person is charging, preparing, or dispatching?
- How many conversations become real orders, and how many are repeated questions?
- At what point is information most often lost: taking the order, sending it to preparation, charging, or arranging delivery?
- What other work does the person handling chat have to leave undone?
Then compare three options using your own information: keep the owner on chat, hire someone, or set up a workflow that brings orders in already organized. There is no universal answer. If the chat involves a lot of unusual back-and-forth, a person may be essential. If what overwhelms you is familiar, repeatable orders, the issue may be how they enter the business and reach the operation.
You do not have to hand everything over to a platform
The owner from that pilot told me that PedidosYa and Uber are a necessary evil. In his view, they remove a headache, but they keep the customer and the commission. Going by what each one publishes, PedidosYa advertises around 10% and Uber Eats between 25% and 30%. For him, that pushes prices up and can make fewer people order.
I am not telling you to leave delivery platforms. They may bring discovery, traffic, and help with part of the operation. The useful decision is to review which customers arrive through them and which ones already know you but still do not have an easy way to order directly.
With Sotoban, orders can come in through WhatsApp or through the counter point of sale, and both create the same order with the same pricing path. Sotoban does not provide drivers: it organizes and quotes delivery, while your business or the delivery team you already use handles the drop-off. Customers order through the WhatsApp they already have, and you do not install anything from an app store: the preparation screen and the register open in the browser.
Setup is not self-service yet. We build it with you: your WhatsApp number, catalog, branch, and hours. If you want to see whether your chat now calls for another employee or a different process, bring us a week of conversations or your order notebook. You can message us on WhatsApp, and we will look at the operation you have today rather than sell you a generic promise.
Frequently asked questions
How much does Sotoban cost?
The founder price is USD 49 a month per branch, with 500 orders a month included and USD 0.10 for each additional order. At that price, setup costs nothing. It is for the first 10 businesses or until the end of the year, whichever comes first. See pricing for the details.
What happens when a customer asks for something unclear?
Sotoban asks the customer instead of guessing: if what they want could be more than one option with a different price, the chat asks which one. The final price is calculated by the system from your branch’s menu, and the order is confirmed with the customer before it is created.