How to Run a WhatsApp Inbox That Keeps Its Promises
How to run a WhatsApp inbox: use a business number, name the owner and hours, clear unread to zero, and tie every conversation to a contact and a deal.
To run a WhatsApp inbox, put the business on a business number in a shared place, name who answers and by when, and treat every unread conversation as a promise outstanding. Then tie each conversation to a contact so nothing depends on memory.
A message that invites a reply is a promise that someone will be there to read it. The inbox is where that promise is kept or broken. It is also where the commercial value of the channel is made, because the thread is the part no other channel does as well.
How to run a WhatsApp inbox: move it off personal phones
The instinct is to treat WhatsApp as a personal phone with a business on it. The moment business conversations live on someone's personal device, the business no longer owns them.
| What happens | The consequence |
|---|---|
| The person is on holiday | The thread goes silent |
| The person leaves | The history leaves with them |
| Someone else wants to help | Nobody else can see what was promised |
Use one business number and one shared inbox. Put the conversations somewhere the team can see them, and treat any customer thread that still sits on a personal phone as a record that needs to come home.
Name the owner, the hours and the time
Decide three things and write them down.
- Who owns the inbox. One named person or team.
- During which hours. Your real response hours, not the hours you wish you had.
- What a reasonable response time is for your business.
Then tell customers, in the profile or the first automated line, so the expectation is set by you rather than imagined by them. The failure is not slowness, because customers forgive a stated delay. The failure is ambiguity: three people who each assume someone else replied, or nobody who notices that a message arrived on a Friday evening.
Treat unread as a promise outstanding
Run the inbox like a queue with a standard. Every unread conversation is a customer waiting, and the inbox's job is to reach zero within your stated response time.
- Sort by what is waiting, with unread first.
- Make sure anyone picking up a thread can see the history, so the customer never has to repeat themselves.
- When a conversation reaches a resolution, say so in the thread: a question answered, an order placed, a next step agreed.
- Marking the ending tells the customer it is closed and the team that it is done.
Why speed matters here
Because the channel shortens the distance between a question and a decision, the speed of your reply is part of the product. Most buying stalls at one small uncertainty, such as whether it works with what the customer already has, whether it can arrive by Friday, or what happens if they cancel. A quick answer clears it.
Look at how long conversations wait for a first response, by time of day and by who owns them. Treat the slow hours as a commercial problem rather than an operational one. We carry that into the monthly review in how to measure WhatsApp marketing.
Every conversation belongs to a contact
A thread that exists only in WhatsApp is a conversation the business will forget. Tie it to a contact record. The phone number is the key, and the contact is where the knowledge lives.
| On the contact record | What it lets you do |
|---|---|
| Who the person is | Answer intelligently, without asking again |
| Where they first came from | Understand why they are here |
| What they have bought | Segment the next broadcast honestly |
| What they agreed to receive | Prove permission if anyone asks |
| What they have asked about | Continue the thread without repeating |
Record opt outs on the contact too, and not only in the messaging tool, so a stop request in one place cannot be ignored in another. The way permission is gathered is in how to get WhatsApp opt in.
Spot buying intent and make it a deal
Most of the commercial value of WhatsApp happens in a moment that is easy to miss. A customer asks a question that means they are deciding. "Can you do twenty of these?" "What would it cost for my team?" "Do you deliver here?" Those are not support questions. They are the start of a sale.
- Recognise the question as buying intent.
- Create a deal with a value, a stage and a next step.
- Give the next step a date.
- Keep the thread attached to the deal.
Without this, the most qualified conversations your business has are invisible to your pipeline, and the follow up depends on whoever happened to read the message remembering to do it. Turning a buying question into a deal is a step someone takes. It does not happen by itself.
Keep the list and the inbox clean
Housekeeping protects the inbox as much as the broadcasts do.
- Remove numbers whose messages repeatedly fail.
- Honour every stop request the same day.
- Stop sending to people who have not read anything in a long time.
A smaller list of people who read and reply is worth more than a larger one that quietly reports you. The reasons are laid out in why people mute WhatsApp business messages.
A weekly inbox routine
- Clear every unread conversation to zero within the stated response time.
- Check that each active thread is tied to a contact.
- Turn each buying question into a deal with a dated next step.
- Mark finished conversations as finished.
- Remove numbers that keep failing.
- Note the slow hours, and who owned the threads that waited longest.
It is a small routine, and it is the difference between a channel that advertises availability and one that delivers it.
Handing a thread from one person to another
Teams change hands during a day, and so do threads. The handover is a risk point, because a customer who has to repeat themselves feels they are dealing with a company, not a person.
| At handover | The standard |
|---|---|
| History | The new person can see the full thread without asking the customer |
| Promises | Anything agreed is visible, with a date for the next step |
| Context | The contact record shows source, purchases and what the person agreed to receive |
| Voice | The tone stays recognisably the same |
The customer should never need to know that the person changed. That is continuity with a named person in practice, and it is the quiet form of trust that a ticket system or a no reply address never gives.
What to say in the first line
The first automated line, or the business profile, is the place to set the expectation. It should tell customers who is answering, during which hours, and roughly how long a reply takes. You decide the content from what your team can really deliver, and you write it plainly.
- Say what hours you are available, in the time zone you work in.
- Say the reasonable response time you decided on.
- Do not promise a faster answer than your team can give.
The reason this matters is simple. Customers forgive a stated delay. What they cannot forgive is silence they were never warned about.
Watch the quiet hours
The messages most likely to be missed are the ones that arrive when nobody is looking, such as a Friday evening. Make a deliberate decision about those hours rather than leaving it to chance.
- Decide whether anyone is available outside the stated hours.
- If not, make sure the stated hours and delay are visible to customers.
- Check the queue first thing when the team returns, starting with the oldest unread.
- Note which hours produce the longest first response times, and review them monthly.
A conversational channel without an owner is worse than no channel, because it advertises availability and then withholds it. How the review fits the wider picture is in WhatsApp broadcast versus conversation.
Closing a conversation properly
A thread that simply stops leaves both sides unsure. Closing is a small act with two audiences, and it is worth doing deliberately.
| Moment | What to say in the thread | Who it tells |
|---|---|---|
| A question has been answered | That the question is answered, and that they can write again | The customer, who knows it is closed |
| An order has been placed | That the order is in, and what happens next | The customer and the team |
| A next step has been agreed | What the step is and when it will happen | The customer, who can hold you to it |
Marking the ending in the thread tells the team the work is done, and it keeps the inbox honest: unread and unresolved stay visible, and finished threads stop competing for attention. At the end of each week, anything still open should have an owner and a date.
Frequently asked questions
Can the founder just answer from their own phone?
You can start there, but a customer thread on a personal phone is a record that needs to come home to a shared place. Otherwise the history leaves with the person and nobody else can see what was promised.
What response time should I promise?
One that your business can keep. The guidance is to decide a realistic time and tell customers, because a stated delay is forgiven and an unstated one is not.
Should every message get a reply?
Every conversation should reach a resolution that is marked in the thread. Not every message needs its own long answer, but nothing should be left unread and unowned.
Who should create deals?
Whoever reads the conversation. The key is that buying questions are noticed and given a value, a stage and a dated next step, rather than left to memory.
The full method, with the checklists, is in The WhatsApp Playbook, a free 31-page playbook.