FOLLOW-UP
A morning WhatsApp brief for each rep, from their own chats
- By Charindu Edirisuriya
- Published 2026-10-28
- 6 min read
Build it from the company numbers, not from the rep. Link each company-owned WhatsApp number once, and every morning each rep can be emailed their own chats: the customers waiting for their reply, what was escalated to them, deadlines due today, missed calls nobody returned, and yesterday's figures beside their own week. Never a message, never another rep's numbers.
Most sales teams on WhatsApp have a morning report for the manager and nothing for the rep. The daily sales report says which customers were left waiting and by whom. The rep it names finds out when the manager forwards it, mentions it in the stand-up, or does not. By then the customer has waited another morning.
This post is about the other email: a list for each rep, of their own chats, every morning. What should be on it, 3 ways to produce it, and the 1 rule that keeps it from becoming a scorecard.
How do I give each sales rep a daily list of the WhatsApp customers waiting on them?
Build it from the company numbers, not from the rep. Once each company-owned number is linked, the record already holds everything a rep needs at 08:00: who wrote and heard nothing back, who rang and was not called back, what a manager escalated, what a rule says is due today. The rep’s list is a view of that record, narrowed to their numbers and sent to them. Nobody fills in a form.
What a rep needs at 08:00
Four things, in the order they should act on them.
- Who is waiting on me right now. Every customer on the rep’s numbers who wrote and has had no reply, longest wait first, with the number so the chat is one tap away. Not yesterday’s count: the list as it stands this morning, because a wait that started at 17:50 last night is still a wait.
- What was escalated to me. A manager who escalated a chat said “this one, now.” If it is still open, it belongs at the top, with how long ago and how many reminders have gone.
- What runs out today. A promise made on Monday that falls due today. A deadline rule that says a quote goes out within 24 hours. A missed call from a customer that nobody has returned.
- How yesterday went, by my own numbers. Messages sent, customers spoken to, how fast they were answered, calls and talk time. Beside the rep’s own recent average, so a quiet day and a busy day are visible to the one person who can do something about it.
Everything else a manager wants in a report, the rep does not need in theirs. Rankings, other reps’ figures, team totals: those are the manager’s questions.
3 ways to give it to them
| Method | What the rep gets | What it costs |
|---|---|---|
| The stand-up | Whatever the manager remembers from the digest, said aloud to the whole team | 15 min of everyone’s morning, and the names are said in front of everyone |
| A shared sheet | A row per customer the rep adds and updates themselves | The rep’s time, every day, and it only lists what the rep remembered to add |
| Built from the company numbers | Their own waits, escalations, deadlines, missed calls and figures, emailed each morning | Linking each company number once. The rep does nothing |
The first 2 share a flaw: they report what someone remembered. The customer who wrote at 17:50 on Friday is in neither, because nobody saw the message before Monday. The third reads the record, so the 17:50 message is at the top of Monday’s list with a wait of 63 hours beside it.
What arrives each morning
Here is the brief one rep in our sample workspace, Marcus Webb, received on a Thursday at 08:00. The figures are demonstration figures, not a customer’s results.
Your morning brief: 1 customer waiting, 1 escalation
15 October 2026
Where your chats stand this morning.
Good morning, Marcus. 1 customer is waiting for your reply, and it is past your 4-hour reply target.
1 escalation is still open on your chats
A manager escalated these and they are still open. They come first.
Waiting for your reply (1)
| Customer | Number | Waiting |
|---|---|---|
| Jordan M. | +1 512 555 0171 | 46h (past target) |
Escalated to you
| What | Customer | Escalated |
|---|---|---|
| a customer waiting for a reply | Jordan M. | 19h ago, reminded 1× |
Open on your chats (1)
| Finding | Customer | Due |
|---|---|---|
| Promise overdue | Jordan M. | 12 Oct 2026, 18:00 |
Missed calls nobody returned (1)
| Caller | Number | Rang |
|---|---|---|
| Kevin T. | +1 512 555 0108 | 40h ago |
Yesterday, by your numbers — and in brackets, your own average over the last 7 days.
- Messages sent
- 118 (104 a day)
- Threads
- 15
- Customers spoken to
- 6
- Mean reply
- 22m (19m)
- Replies within target
- 71% (68%)
- Calls in
- 3
- Calls out
- 1
- Talk time
- 9.0m
Mean reply is measured on your workspace's business-hours clock; a wait that fell outside business hours is not counted. Your reply target is 4 hours. No message from your chats is in this email: a customer waiting is named, and the conversation is on your phone.
Read it top to bottom. The first sentence says the one thing that matters: 1 customer waiting, and past the 4-hour reply target the workspace set. The escalation comes next, because a manager asked for it; the brief says it was escalated 19 hours ago and reminded once. Then an overdue promise, then a customer who rang on Tuesday and never heard back, and only then Wednesday’s figures.
Every figure in the lower half is the same one the manager’s digest prints for Marcus. The number in brackets is his own average over the last 7 days: 118 messages against his usual 104, a 22 minute mean reply against his usual 19. Nothing about Nina or Chris is in it.
The rep’s own numbers, never the team’s
A list of waiting customers helps a rep. A ranking does not. The moment a morning email shows a rep where they sit against the team, it stops being a to-do list and becomes a scorecard, and a scorecard read alone at 08:00 teaches a rep to argue with the numbers rather than open the chats.
So the only comparison in the brief is the rep against their own last 7 days. A rep who sent 118 messages on a day their average is 104 knows it was a heavy day. Whether 104 is good is a conversation for the manager to have with them, with the team view in front of both of them, which is what coaching from real conversations sets out.
The rule that keeps it fair
No message from any chat. Not a quote, not the words a rule matched, not what the AI made of it. The brief names a customer, their number and how long they have waited; the conversation is on the rep’s phone, where it already is.
The rule is the same one the manager’s digest keeps, and for the same reason. An email is a copy outside the archive. Reading a conversation in WAOversight is written to the access log before anything appears on screen; an email that quoted messages would be a way round that log, for the rep as much as for the manager. What the rep is told about all of this is on what your employer can and cannot see.
Setting it up
- Link each company number once, with a QR scan. Nothing is installed on any phone.
- Give each rep an email address on the Registry. A rep with no address and no login cannot be reached, and the settings page says which reps those are.
- Switch the rep daily brief on. Choose the time, on the quarter hour in your workspace’s timezone, and the days of the week. Your holidays are skipped unless you say otherwise.
- Switch off any rep who should not get it, without switching it off for everyone.
From the next scheduled morning, every rep with something waiting or any traffic the day before is emailed. A rep with nothing waiting and a quiet yesterday gets no email that day, so the brief never becomes a daily message that says nothing. The mechanism, section by section, is on the rep daily brief page.
What this does not do
It does not send anything on WhatsApp. The brief is email. A message to every rep every morning from one number is the pattern WhatsApp bans numbers for, and the one number a workspace can send from is reserved for escalation notices.
It cannot see a reply made outside WhatsApp. A customer the rep rang back on an ordinary phone line still reads as waiting. A WhatsApp call that connected counts; so does a message from any linked number on the thread.
It does not know what was promised off WhatsApp. A deadline agreed in a showroom is not in any chat, so it is not in the brief.
It is not a reply. The rep still answers the customer, from their phone. The brief only says who is waiting.
Where the manager’s report still fits
Keep the daily sales report. The manager still needs the team: every rep’s figures side by side, the top findings across the team, the rules with items open. The rep’s brief does not replace it; it takes the part of it that was always meant for the rep and sends it to them directly, before the stand-up, with the number to tap.
What changes is the stand-up. When every rep has already seen their own list, the manager does not read names out. The 15 minutes go on the 2 customers the team is about to lose, which is what the meeting was for.
Find out what happened last week.
Fifteen minutes, your own numbers, no slides. If you don't see something that surprises you, we'll say so.
WAOversight is an independent product and is not affiliated with or endorsed by WhatsApp or Meta.