One WhatsApp number for several salespeople: the assignment rule in 4 lines

A chat arriving at a shared number needs an owner before anything else, and the rule that assigns one fits in four lines: whoever answers first signs the message with their name and that chat is theirs; if 15 minutes go by during business hours and nobody has signed, the salesperson on duty that day takes it; a chat only changes owner through a message written in that same chat; and after three days with no reply from the customer, the owner releases it. You paste it in the team group today and it is written the same way with the WhatsApp Business app, with a shared inbox or with whatever comes next: the tool gives you the owner field, never the criterion. The technical part —linking the same number on several devices so everyone sees the same chats— is solved in five minutes and is not where the problem is.

The mess of a shared number takes exactly two forms and you pay for both. The first is the collision: two salespeople work the same opportunity without knowing it and end up negotiating against each other. Each of them believes they are beating a competitor and improves their offer —brings the delivery date forward, stretches the payment terms, drops what they are authorised to drop— when in reality they are raising the stakes against a colleague sitting three metres away. It is not the problem of having two price lists coexisting, which is fixed with a single list: here both can be looking at exactly the same list and the customer still walks away with the better of the two hands, because what differs is not the published price but how much each one is willing to give up to close today. The second form is the gap: an enquiry comes in, all three see it, all three assume somebody else is taking it, and the customer is left without an answer until they write to a competitor. Both come from the same place: the chat has no owner.

Sharing the number takes five minutes; who answers does not

Linking the same number on several devices is the easy part and needs nothing beyond the WhatsApp Business app. In five minutes you have three people looking at the same chats.

What that app does not give you is the only thing that matters once there are three of you: somewhere that says who this conversation belongs to. There is no inbox per salesperson, no assignment field, and nothing warns you that your colleague is typing in that same chat from another computer. Assignment ends up living in the one place where it cannot be audited: inside each person's head.

And the tool you pick does not fix this either. A shared inbox gives you an "assigned to" field, but you have to have decided the criterion that fills that field anyway: if today you do not know who a new chat belongs to, buying software leaves you the same mess spread across more screens and with a subscription on top. What is missing are two things written down nowhere: who each chat belongs to and when it stops belonging to them.

The assignment rule, in 4 lines to paste in the team group

1. OWNER. Whoever answers first signs their first message
   ("Hi, this is Vale from Aceros del Sur"). That chat is theirs.
   If the chat already has a signature, you do not write: you tell that person.

2. ON DUTY. If 15 minutes go by during business hours and nobody has signed,
   the salesperson on duty that day takes it. The duty roster is written
   in the group every Monday, it is not assumed.

3. HANDOVER. A chat only changes owner through a message in the chat:
   "From here on Martín takes over, he handles the southern zone". It is written
   by the one coming in, not by the one leaving.

4. RELEASE. Three days with no reply from the customer, the owner sends
   the closing message and tells the group they are letting it go.
   From then on it is free for anyone.

The first line defines ownership by speed and not by allocation. You could assign by zone, by product or by rotating shift, and all of those criteria are better on paper. On WhatsApp they are worse, because any rule that forces an intermediate step to decide the owner adds minutes, and minutes are exactly what you are selling when somebody writes to you. First you answer and sign; the fine-grained allocation is sorted out afterwards with line 3.

The second exists because line 1 on its own produces gaps. If the owner is whoever answers first, a chat nobody answers has no owner and just sits there. Fifteen minutes and not five, because whoever is finishing another chat still gets there in time to take their own and you are not pulling a good one out of their hands; and not an hour, because by then the customer has already written somewhere else. The person on duty is one individual with a first and last name per day. "The team" is nobody.

The third prevents the duplicate message. The typical scenario: on Tuesday Vale sends a quote, on Thursday Martín opens the chat, does not scroll up and sends a different price. The handover is written by the one coming in because that way the customer knows who they are continuing with without having to explain everything again, and because it puts on record the exact date the hand changed.

The fourth is the one almost nobody writes down, and without it the rule breaks the other way. The signature that protects also blocks: three weeks in you have twenty chats with an owner who stopped following up and that nobody else touches because they carry a signature. That is why ownership expires. Three days with no reply from the customer and the chat goes back into the common pool.

The signature goes as a message in the chat, not as a label in an app

The temptation is to mark the owner with WhatsApp Business labels or with an internal note. As long as assignment is manual, they are no use.

First, a label lives inside a tool: the day somebody answers from somewhere else, or you migrate to a shared inbox, those marks do not travel. A message written in the chat is never lost, because it is the chat.

Second, the signature does a job the label does not: the customer stops talking to a faceless company and starts talking to Vale. When they come back two months later, they write asking for Vale, and there the assignment sorts itself out.

Third, when you review three weeks later why a sale fell through, you know who to ask without reconstructing anything.

One execution detail: the signature goes in the first message and is repeated in the first message of each day after a long silence. Nobody scrolls up to find out who they were talking to.

The duty roster is written on Monday or it does not exist

A pinned message in the team group, every Monday:

Duty roster for the week (first replies to chats with no owner):
Mon Vale · Tue Martín · Wed Vale · Thu Sofía · Fri Martín
Saturday 9am to 1pm: Sofía

The job of the person on duty is not to sell everything that comes in that day. It is that no chat goes past 15 minutes without a signature. If the enquiry is about a zone or a product they do not handle, they answer anyway, qualify it and do the line 3 handover. Answering first and allocating afterwards is what prevents the gap; allocating first and answering afterwards is what creates it.

The expensive mistake is not sharing the number: it is each salesperson using their own

Many SMBs solve the mess the other way round: each salesperson with their own WhatsApp Business and their own SIM. The collisions disappear and three more expensive problems appear.

The customer starts belonging to the phone, not to the company. In sales roles turnover exists, and the day that person leaves they take the history, the open quotes and the contact with them. For months your customers keep writing to a number you do not control, sometimes when that person is already working for a competitor.

You also lose the ability to answer basic questions —how many open conversations there are, which quotes are pending— without asking each salesperson and taking their word for it. And the two-year customer who was served by two different people has their history split across two phones, one of which no longer exists.

A messy shared number is still a better deal than three tidy numbers that are not yours.

The unowned chat has two bills and both are calculated in one line

The collision is the one you see, the one argued about in the Monday meeting and —this is the surprise— the cheaper of the two. When two salespeople end up working the same opportunity, the customer keeps the softer of the two hands and the difference comes entirely out of your margin:

(highest offer − lowest offer) × collisions per month.

With example figures: an average quote of USD 900, two salespeople who differ by 12% in what each is willing to give up to close, three collisions a month. Around USD 320 a month that shows up in no report, because each case looked at on its own looks like a normal, well-argued discount. On top of that there is a second round that never gets calculated: the customer who discovered that inside your company you can shop around does it again, and on the next purchase writes asking for the other salesperson on purpose.

The gap is not visible and costs considerably more, because it does not shave your margin: it wipes out the whole sale.

new enquiries with no first reply the same day × your close rate × average ticket.

With the same company: 40 new enquiries a week, 3 that no salesperson touched the day they came in, a close rate of 1 in 5 and the same USD 900 ticket. That comes to around USD 2,100 a month, seven times the collision. And it is the bill nobody argues about, because a chat nobody answered leaves no trace: there is no odd quote, no discount to justify, no angry customer on the other side. It is simply not there, and the month closes a little weaker without anyone knowing why.

That is why both are measured together and with the same effort: one week, two numbers. How many chats had two salespeople writing within 24 hours with no handover, and how many new customers were left without a first reply that same day. As a rule of thumb, if the sum goes above one in every ten new chats, the written agreement has stopped working for you.

An agreement between people needs one of them to be free, and it falls apart in this order

The four lines are not a system: they are a pact that holds as long as somebody has the head space to watch the clock and the list. The three points where that stops being true always arrive in the same order.

Line 2 has nobody to measure it. Nobody times 15 minutes. It works while enquiries are few and everyone hears the phone. Above around 20 new conversations a day, the person on duty is inside one chat when the next three come in, and the clock becomes decorative.

Outside business hours no rule holds. What comes in at 9pm on a Saturday waits until Monday, with no signature on it. If a meaningful share of your enquiries arrives at night or at the weekend, no written line solves it.

There is no reporting. You cannot answer, without opening chat by chat, how many open conversations each salesperson has, which ones have not been touched in five days, how long the first reply takes on average or how many leads each person got. Nor can you reassign forty chats when somebody goes on holiday.

All three fail for the same reason: the rule needs somebody to be free to watch the clock and the list, precisely at the moments when nobody is. What is needed there is for the owner to be assigned automatically when the enquiry comes in —by rotation, by zone or because that customer already belonged to someone—, for the 15 minutes to escalate without anyone timing them, and for the chat that arrives at 9pm on a Saturday to end up answered and already assigned for Monday. The rule organises your people; it does not replace them when none of them is free.

The rule comes first, whatever tool you have

The criterion, rounded: with two or three salespeople and fewer than 15 new enquiries a day, assignment holds with the four lines and one person on duty per day. From four salespeople up, above 20 new enquiries a day, with real volume outside business hours or with an allocation criterion other than "whoever answers first" (zone, product, book of business), the agreement between people stops being enough and the owner has to be assigned automatically at the moment the enquiry comes in.

That is a different decision from when the WhatsApp Business app gets too small for your volume and it is worth moving to the API, which is settled with other numbers and is covered in the WhatsApp automation guide. The two are independent and it is best not to mix them: you can need the API for volume with a single salesperson, and need the assignment rule with three people and low volume. The rule, moreover, is not thrown away when the tool arrives: it is loaded into it. Anyone who has picked the best shared inbox on the market without first defining when a chat stops having an owner will discover in three weeks that they have forty conversations assigned to somebody who no longer looks at them.

Two weeks of counting before looking at any tool

None of the above needs you to buy anything to find out whether it applies to you, and the counting is done by the same person who allocates the chats today.

For two weeks, on a sheet off to the side, note down two things and nothing else. One tally mark every time two salespeople show up in the same chat or quote the same customer. And one tally mark every time a new enquiry ends the day without a single reply. At the end of the second week multiply each column by the two formulas above and you will have your two bills in money, not in gut feeling.

Almost always the same thing happens and it is worth anticipating: the collisions column comes out short and the gaps column comes out uncomfortable. It is the reverse of the Monday meeting order, where the collision is argued about —it has someone to blame, a name and a screenshot— and the chat nobody opened is never mentioned, because it has none of those three things.

With those two columns the decision makes itself. If the two bills together do not reach the cost of a shared inbox, write the four lines, paste them in the group and count again in six months. If the gaps column on its own already exceeds it, stop arguing about tools and look at what time of day concentrates those gaps: almost always there are two slots, and one of the two is fixed with Monday's duty roster, for free.

The two columns and the timing of the gaps: info@striqtech.com.