One WhatsApp Number, Several People

Several people can sell from one WhatsApp Business number. They cannot all be the owner of the same chat. The number is the shopfront the customer already saved. The owner is the person who owes the next step. When a team blurs those two ideas, the customer gets two replies, or none, and both feel like the business does not know itself.

This is the long version of the handoff. The sheet guide lists the columns. The sales day says when the row is written. Here, the subject is the people: who speaks, who stays quiet, and what the next person must see so the customer is not asked the same question twice.

One number. One owner per chat. If you cannot name the owner, you do not have a shared inbox. You have a shared risk.

Two replies, or none

Watch a small team share a phone for a week and the failures repeat. Two shapes, and almost no others.

Two replies. The customer asks if a Saturday viewing is free. One colleague says yes and offers 4:30. Another, who did not see that message, says Saturday is full and offers Monday. Both answers are polite. Together they are a contradiction with your name on it. The customer does not know which colleague to trust, so they trust neither.

None. Everyone saw the message. Everyone assumed someone else had it, because the chat is "the office number." The customer waits until morning and writes to the next business on their list. Your team discovers the thread at 10am, apologises, and calls it a one-off. It is not a one-off. It is the design.

Both failures come from the same gap. The thread has activity and no responsibility. Reading is not owning. A reply is not a handoff. Until one person is named, the chat is unassigned, and unassigned chats decay in exactly these two ways.

Reading a chat is not owning it. If you cannot name the owner, nobody will call.

A second phone number feels like a fix. It is usually a delay. Customers then have to guess which number is real, old conversations fork, and the sheet splits. Stay on one number until the owner rule is boringly reliable. Add a number when you truly have a second desk, a second city, or a second brand, not when the first desk is messy.

One number is the shopfront

Customers save a business once. They do not want a personal mobile for the receptionist, another for the advisor, and a third for "urgent." The business number is the address. People change. The address should not.

That is a reason to be on the WhatsApp Business API rather than on a personal app installed on one founder’s phone. A personal app walks out of the building in a pocket. An API number stays with the account. Templates, opt-in, and the thread history stay with the account too. The short explanation is in what the WhatsApp Business API is.

The shopfront can still sound human. Messages go out under the business name, and the sentence inside them names the person. "This is ConverseWith’s demo desk. Meera will call you at 6." The brand is the address. The name is the relationship. You do not have to choose.

Inside the team, decide who is allowed to send. On a tiny desk, both people may send, but never on a chat the other person currently owns, unless they are covering a leave day and the sheet says so. On a slightly larger desk, the night automation sends the first reply and the questions, and humans send only after a status exists. Either rule works. "Whoever sees it first" does not.

Owner, status, and next step

Three fields end the ambiguity. They are boring, and they are the whole system.

The owner is a name on your team, not a department. "Sales" is not an owner. "Rahul" is an owner. If Rahul is on leave, the owner changes to a name, in the sheet, before the leave starts. An owner who cannot act is the same as no owner, with extra delay.

The status is hot, warm, or not now. Hot means the constraint fits and there is a time, or a time could be set today. Warm means the chat started and did not finish. Not now means stop. The qualification guide is how the status gets chosen. The shared inbox only insists that the status is visible to the second person without a scavenger hunt.

The next step is a verb a person can do in one sitting. Call at 6. Offer Sunday after 4. Send the brochure they asked for. Stop. "Follow up" is not a verb. It is how chats linger for nine days and then get a guilty template. Write the step the night the status is set, while the constraint is still in your head.

Put these three on the sheet row, next to the ask and the constraint. WhatsApp can stay the place the words were said. The sheet is the place the team looks. If the truth lives only inside one person's memory of the thread, you are back to a personal phone with extra steps.

The handoff sentence

When a second person must join, the customer should hear a clean introduction, once. Not a new greeting that restarts the relationship, and not silence followed by a different tone.

A handoff sentence has the new name, the fact that they already know the answers, and the next action. "Priya will take this from here. She has the dates and the headcount you sent, and she will message you the two hotels that fit." Then Priya speaks. Priya does not open with "Can you tell me your dates again?"

Write the sentence in the thread, not in a side chat the customer cannot see. The thread is the record they trust. A side chat is where two colleagues agree a story that the customer never heard.

If the automation is doing the night shift, it can send this sentence itself once the questions are done and the owner is known. That is a better use of automation than a clever paragraph. The customer learns there is a person, and the person inherits a thread that already introduced them.

Do not hand off twice. If Priya needs a manager for a discount, Priya asks the manager off to the side and returns with an answer. A third voice in the thread, unannounced, feels like a crowd. The customer came to one business.

What the next person needs on screen

The next person needs the decisions, not the banter. Before they type, they should be able to read, in one place:

The name the customer used. The ask, in the customer's noun. The constraint. The status. The next step. The meeting time, or a clear mark that there is none. Anything they were promised, including a document that was supposed to be sent.

They do not need a transcript pasted into a notes cell. Transcripts are long, they go stale, and they tempt the next person to reply to a line from yesterday that the customer has already moved past. If a sentence in the transcript does not change the next step, it can stay in WhatsApp, where it already lives.

They do need to know what the automation already said. The most common way to look careless is to repeat the menu the bot just offered. If the first reply asked for a budget, and the budget is in the row, the human's first line is about the budget, not a second request for it.

On a practical screen, that means the sheet is open next to the inbox, or the inbox itself shows the fields. Scrolling up twenty messages to "get context" is a sign the fields are empty. Fill the fields. Then the scroll is optional.

For a travel desk, the fields are dates, headcount, and the kind of trip. For a coaching institute, they are the course, the batch timing, and who the class is for. For a property desk, they are locality, budget, and whether they will visit. The playbooks for travel, coaching, and real estate name them. The handoff does not change. Only the nouns do.

After hours and the next shift

Decide, in writing, what the night is allowed to do. A clear policy is short.

The night reply can greet, ask the three questions, set a provisional status, and book a time if the calendar has real openings. It can name the morning owner. It cannot offer a discount, change a price, or promise a slot that is not on the calendar.

The morning shift starts from the sheet, not from the unread count. Unread is a queue. The sheet is a priority. A hot row from 8:50pm outranks a new "hi" from 9:05am. If the morning person answers the new hi first because it is on top, the night process was theatre.

When shifts overlap, name a single sender for that hour. Overlap is when double replies are born. "We are both online so we will both help" is the Saturday viewing contradiction waiting to happen. One person sends. The other updates rows, prepares the visit, or takes the calls that were already booked.

Leave and sickness use the same mechanism as the night. Change the owner on the open rows. Send one line to any customer with a meeting that day, from the business number, naming the person who will actually be there. Do not forward the chat to a personal WhatsApp and hope. Forwarding splits the record and the opt-in.

The unowned row

Once a day, before new work, filter the sheet for rows with no owner, no next step, or a next step older than the rule you set. Those rows are the leak. They will not announce themselves in the inbox, because the inbox sorts by latest message, and a person who is waiting quietly has the oldest timestamp.

Give each of those rows an owner in the meeting, or in the ten minutes you pretend is not a meeting. If the status is not now, the next step is stop, and the owner can be the person who confirms it stays stopped. A stopped row with an owner is healthy. A warm row with no owner is where this week’s apology is hiding.

Do not delete quiet rows to make the filter look clean. Deleting is how the same person messages again next month and gets treated as a stranger. Mark not now, and leave the history. Next month’s template, if you send one at all, can refer to the original ask. That only works if the row survived.

The follow-up guide says how many times you may nudge a warm row. The shared inbox adds a prior question: whose job is the nudge? If the answer is "whoever is free," it will be nobody on a busy day and everybody on a slow one.

What the team chat should not contain

The internal chat is not a second copy of the customer's life. Colleagues need the next step. They do not need a screenshot of an identity document, a card number, a one-time password, or a medical description.

Clinics and dental desks should be especially plain about this. The internal handoff can say "new visit, Tuesday 4:30, owner is Dr Shah’s coordinator." It should not summarise symptoms for a group chat that includes people who do not treat patients. Booking is an operations fact. Clinical detail belongs in the clinical record, if you keep one, under whatever rules already govern it. The WhatsApp playbook does not replace that record, and it should not become an unofficial one.

Insurance desks have the same shape. The handoff can say which product the person asked about and when they can talk. It should not become a place where colleagues debate which policy the person ought to buy. That recommendation, if it happens at all, is a licensed conversation with the customer, not a thread aside.

If a customer sends a document you did not ask for, do not relay it around the team "just in case." Tell them, in the business thread, what you actually need, and let the extra file stay unshared.

A worked handoff

This is an example, not a customer and not a result.

A parent messages at 7:40pm about a weekend batch for a class 10 course. The night reply asks which subject, which area they can travel to, and whether Sunday morning is possible. They answer: mathematics, Andheri, Sunday morning works. The row is written. Status hot. Owner is the counsellor who covers Andheri batches, named on the sheet before morning. Next step: offer the 9am batch and a 10:30 alternative.

At 9:15am the counsellor sends one message. It uses the parent's name, mentions mathematics and Sunday, and offers the two times. It does not ask which subject they need. The parent picks 9am. The calendar event is created with the same counsellor as the guest, and the sheet meeting field matches. If the counsellor had been on leave, the owner field would have been changed first, and the message would have used the other name. The parent would still have seen one business.

Nothing in that handoff required a second WhatsApp number. It required the row to exist before the counsellor sat down.

A small team does not need a second number yet

Add people before you add numbers. A second number is justified when the audiences must not share a thread: two brands, two cities with different calendars, or a volume that has already outgrown one owner plus one backup. ConverseWith’s Growth plan is one WhatsApp number at ₹2,999 a month, with a one-time basic AI training. Professional is three numbers at ₹7,999 a month, with lead scoring, auto follow-ups, knowledge feeding, and dynamic AI training. The first 14 days are free. The upgrade is there when the first number is orderly, not when it is confusing.

Until then, the work is the owner, the status, and the next step, written where the next person will look. Do that for a month. The inbox will feel quieter, which is the signal that it is finally being shared on purpose.