Academy › Build › WhatsApp and customers
Whose customer is it
You walk away with the handoff rule written down where the whole team can see it: which conversation belongs to whom, and who takes whatever doesn't fit any category.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
When several people are answering the same business WhatsApp, it's easy for two people to answer the same message, or for nobody to answer at all, even though the bot already handles the usual questions. The missing piece is in the middle: when the bot hands off a conversation to a person, who on the team picks it up?
It's eleven in the morning. A customer writes asking to reschedule their Thursday appointment. The bot has already done its part: the customer asked to speak with a person, so the bot hands off the conversation to be handled by a human. Marta is at her computer. Carlos is too.
Whose turn is it? If the answer is "whoever sees it first," you already know how that goes: both of them answer, or neither does, each one assuming the other has it. What's missing is a written rule for who picks up what, not a habit that shifts depending on who's more on the ball that day.
By rotation or by topic
There are two ways to divide up what the bot passes along. The first is by rotation: each new message goes to the next person on a list, no matter what it's about. The second is by topic: each person owns a type of conversation, and the message always goes to whoever handles that topic, regardless of who happens to be free at the moment.
An auto repair shop makes this clear. Whoever's at the front desk handles routine service appointments. The shop manager handles body-work estimates, because they're the only one who can put a price on a dent. There, splitting by topic isn't optional: rotating it would hand a body-work estimate to someone who can't price it, and the customer would be left waiting on a number that person can't give them.
- Each message goes to the next available person on the list, in turn
- Splits the workload evenly so no one gets overloaded
- Anyone can pick up any conversation: no one needs to know it all
- Each person owns a type of conversation: bookings, issues, estimates
- The message always goes to whoever handles that topic, not whoever's free at the moment
- It requires that whoever opens the message can see what it's about and leave it for whoever owns that topic
Which one should I pick: Pick by topic if everyone on your team already handles a different part of the job, like the shop manager handling body-work estimates. Pick by rotation if everyone answers everything equally well, and the only thing missing is making sure no one carries more than their share.
A small business doesn't have to settle for just one of the two. Split by topic whatever requires specific knowledge, like a body-work estimate or a customer's file. Split by rotation whatever anyone on staff can handle equally well, like confirming a time.
This happens at an accounting firm with two partners: general questions of the day, like deadlines or paperwork, rotate between the two because they both answer them the same way. But questions from a specific client always go to the partner who handles that account, because they're the only one who knows the numbers. Both rules live side by side in the same business, each one where it makes sense.
What matters isn't which system looks more professional. What matters is that every conversation has a clear rule before it arrives, not a decision made on the fly while the customer is already waiting for a reply.
The topic with no owner
The costly mistake isn't splitting things up wrong. It's leaving a gap. A topic that's assigned to no one, or assigned to "everyone," ends up with no one at all: each person assumes someone else will pick it up, and the customer waits for a reply that never comes because no one felt responsible for sending it.
Picture a message asking about the status of a delivery. It's not a booking, it's not a classified issue, it doesn't fit any topic on the list. If that kind of message lands in a drawer labeled "other," and that drawer doesn't have a name behind it in your written rule, the message just floats there until someone stumbles across it while checking the inbox.
Before you roll out the rule, go through the list of topics you get and make sure each one has exactly one person behind it. Not zero, not two.
The rule, written where everyone can see it
The rule doesn't live in anyone's head, or in a WhatsApp group where someone once said "I've got this one." It lives somewhere the whole team checks before replying: a shared spreadsheet or a printed sheet by the counter, right next to the list of what gets left to the bot. It's written topic by topic, using the same names you use to tell them apart, and it's in place before the first real message that depends on it comes in.
- 1List the topics
Go through the last conversations the bot handed off to a person and jot down what each one was about: bookings, issues, estimates, and so on for all of them. - 2Put a name on each one
Next to each topic, write down the person who takes that conversation when the bot hands it off. If it rotates, list the names in the order they take turns. - 3Add the "everything else" bucket
Create one last row for anything that doesn't fit a topic on the list, and give it a fixed name. Never "team," never "everyone." - 4Share it and test it
Send it to the whole team, then text yourself from another phone with a topic you haven't tested yet, to confirm the right person picks it up, and no one else, before a real customer writes in.
With this table in plain view, you already know whose conversation it is the exact second the bot hands it off. Marta and Carlos stop looking at each other to decide who answers: the answer was already written down before the customer even asked.
What's still missing is deciding what happens in that same second, when two people might be reading the same message at once, and what happens if the person whose turn it is isn't working at that hour. That's next.
- The routing rule you've chosen: by rotation, by topic, or a mix of both depending on what each type of conversation requires
- Every topic with exactly one person behind it, no gaps and no overlaps
- A fixed owner for whatever doesn't fit any topic, written down just like all the others
Put it to the test
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. A hair salon has two people at the front desk doing exactly the same job: booking appointments, taking payment, answering scheduling questions. Should this be split by rotation or by topic?
By rotation. If both people respond equally well to any conversation, there's no topic that calls for a specific owner. The only thing that needs dividing is the workload, and alternating handles that.
2. At a dental clinic, emergencies always have to go to the same dentist because they're the one who knows each patient's history, but calls to book an appointment can be taken by anyone at the front desk. Does the whole clinic need to pick one single system for splitting things up?
No. Emergencies get split by topic, always to the same dentist, and appointments get split by rotation, to whoever's free at the front desk. Each type of conversation gets divided based on what it actually requires, not on which system looks tidier on paper.
3. A business sends bookings to one person and complaints to another, but nobody has decided what happens with a message asking about the status of an order, something that's neither a booking nor a complaint. What's missing, and what happens to that message if it's left as is?
What's missing is an owner for the "everything else" bucket. If it's left unassigned, that message falls into no-man's-land: each person assumes the other one has it, and the customer never gets an answer, even though the split for the other two topics works fine.
What's still unresolved is the moment when two of you could be looking at the same message at the same time, before you both reply without knowing about the other.
In Yodai the WhatsApp bot answers with your prices and your hours, and hands the chat over when someone asks for a person. See how the WhatsApp bot for your business works.
NextWhoever picks it up, keeps it