Internal Notes & @Mentions on WhatsApp
A customer asks a question your teammate already knows the answer to. So you do the only thing WhatsApp lets you do: screenshot the chat, paste it into a separate group, type "anyone know what we quoted this guy?", wait, copy the reply back, and hope you didn't accidentally send the side conversation to the customer instead. Every team running support or sales on WhatsApp has lived this — the moment two people need to talk about a chat without talking in it.
The fix is WhatsApp internal notes: a private layer on top of the conversation where your team comments, @mentions each other and leaves context, all invisible to the customer. This guide explains what internal notes and @mentions actually do, why plain WhatsApp can't offer them, and how a shared workspace puts the side conversation right where it belongs — inside the chat, not beside it.
What internal notes and @mentions are
An internal note is a message you leave on a conversation that only your team can see. It looks like a reply, it lives in the same thread, but it never sends to the contact. Think of it as a sticky note pinned to a customer chat: "this is the angry one from Tuesday," "already refunded, don't re-process," "wants the enterprise quote, not the starter."
An @mention is how you pull a specific teammate into that note. Type @Priya inside a note and Priya gets pinged — she opens the chat, reads the full history and the note, and picks it up. No screenshot, no forwarding, no "which customer was this again?"
Together they solve one narrow but constant problem: collaborating on a single conversation without the customer in the room. That's it. But for a team sharing one number, that one capability is the difference between a coordinated inbox and a chaotic one.
Why plain WhatsApp can't do this
The free WhatsApp Business app — and even the WhatsApp Business API tools — have no concept of a note. WhatsApp only knows two kinds of message: one you send to the contact, or one in a group everyone in the group can read. There is no third, private, team-only layer. So teams improvise, and every workaround leaks:
- The "ops" side-group. You screenshot the customer chat into a staff group to ask a question. Now the context is split across two apps-within-an-app, the customer's history isn't attached, and the answer lives somewhere nobody will find it next week.
- DMing a colleague. "Hey, what did we promise the Sharma account?" Fast, but invisible to everyone else and gone the moment the chat scrolls.
- The near-miss. The genuinely scary one: you mean to send the snarky aside to your teammate and send it to the customer. On a shared number, one wrong tap is a reputation problem.
None of these put the note where it belongs — attached to the conversation, visible to whoever picks it up next, and structurally impossible to send to the customer. That's a job for a shared inbox, which is the foundation everything in this guide sits on; our WhatsApp shared inbox for teams guide covers the full picture.
How internal notes work in a shared workspace
In a workspace, every conversation has two tracks running in the same thread: messages to the customer, and notes between your team. The notes are visually distinct (a different colour, marked "internal," never a green bubble) so nobody confuses the two — and the system simply won't deliver a note to the contact.
Here's what that unlocks day to day.
Leave context that survives the handoff
The most valuable note is the one your future teammate reads. When a chat gets passed from sales to onboarding, or from the morning agent to the evening shift, a note carries the why: "promised free setup," "do NOT upsell, they churned once already," "spouse handles billing — loop them in." The next person opens the chat already briefed, instead of asking the customer to repeat themselves. This is the connective tissue of WhatsApp team collaboration — context that lives with the conversation, not in someone's head.
Pull the right person in with an @mention
When you hit a question outside your lane — a refund you can't authorise, a technical spec you don't know — you @mention the person who can. They're notified, they have the entire thread in front of them, and they either reply inside the note or take over the customer reply themselves. No forwarding, no re-explaining. It pairs naturally with assigning WhatsApp chats to agents: mention to consult, assign to hand over ownership.
Keep the customer-facing reply clean
Because the back-and-forth happens in notes, the customer only ever sees the finished, agreed answer. Three people can debate the right discount in the notes; the customer receives one clear message. The messy thinking stays backstage.
Build a searchable memory of the account
Notes don't vanish. They sit on the contact's timeline, so months later — when that customer comes back — the history of why you did things is right there. Tied into a real CRM with custom fields and a contact profile, internal notes become part of the account record, not a disposable aside.
A quick example
A buyer messages your shared sales number: "Still thinking about the annual plan — can you do anything on price?"
- The agent on duty opens the chat and leaves a note:
@Dev this is the 12-seat lead from the webinar, deal's in Negotiation. What's the most we can flex? - Dev gets the @mention, opens the chat, reads the full history, and replies in the note: "Up to 15% if they commit annual. Don't go past that."
- The agent sends the customer one clean message: "Happy to do 15% off if you go annual — shall I set that up?"
- The note stays on the contact's timeline. When the customer mentions price again in three months, the whole reasoning is right there.
The customer saw two messages. Your team had a full internal conversation. Nothing leaked, nothing got screenshotted, nothing got lost.
Notes vs assignments vs replies — keep them straight
These three tools overlap, so a simple rule of thumb:
| Action | Who sees it | Use it when |
|---|---|---|
| Reply | The customer | You're answering the contact |
| Internal note | Your team only | You're commenting about the chat, or adding context |
| @mention | A specific teammate (in a note) | You need one person's input or eyes |
| Assign | Your team (changes ownership) | One person should now own the conversation |
Most teams use notes constantly, @mentions a few times a day, and assignment whenever a chat changes hands. For more on the ownership side, see how to share one WhatsApp number with a team.
Where Tenashi fits
Tenashi is the WhatsApp workspace for teams, and internal notes and @mentions are built into every conversation in the shared inbox. You link your existing WhatsApp number with a QR scan — no new SIM, no porting — and your whole team works one inbox where each chat has a private notes track alongside the customer-facing messages. Type @teammate, drop the context, and the note is pinned to that contact's timeline forever. The customer never sees a word of it.
Crucially, this works on DMs and groups — the official WhatsApp Business API can't touch groups at all, so it can't offer team notes on the group chats where a lot of deals actually happen. With Tenashi, you can leave a note on a broker-group lead or a busy customer group the same way you would on a DM. Underneath sits a real CRM — contacts, custom fields, a drag-drop pipeline, follow-ups — so a note isn't a throwaway message; it's part of the account record. On Growth and Scale plans, AI can also summarise a long, noisy chat into the key points and suggest a reply, so a teammate you @mention is caught up in seconds. Sends stay ban-protected — human-paced, warmed up, with burst patterns paused before they ship — which reduces risk to the number that runs your business (risk reduction, not a guarantee).
Pricing is flat — from $18/mo, no per-message fees and no template approvals — with a 3-day Growth trial, no card.
Start your free trial → · See every feature
FAQ
What are internal notes on WhatsApp?
Internal notes are private messages your team leaves on a customer conversation that the customer never sees. They sit in the same thread as the real chat but are visible only to your team, so you can add context, flag accounts and discuss a reply without ever sending it to the contact.
Can you @mention a teammate on WhatsApp?
Not in the standard WhatsApp app — it has no team-mention feature for one-to-one chats. In a shared workspace like Tenashi you can type @teammate inside an internal note to notify a specific colleague, who then opens the chat with full history and either advises in the note or takes over the reply.
Will the customer see an internal note?
No. Internal notes are structurally separate from customer-facing messages — they're visually marked as internal, never appear as a sent message, and the system won't deliver them to the contact. That's the whole point: it removes the risk of accidentally sending a side comment to the customer.
Do internal notes work on WhatsApp groups?
Yes, in Tenashi. Because Tenashi works on your own number, group chats appear in the same shared inbox as DMs, so you can leave notes and @mention teammates on a group lead too. The official WhatsApp Business API can't access groups at all, so API-based tools can't offer this.
Do internal notes get saved with the contact?
Yes. In a real workspace, notes live on the contact's timeline alongside the message history, deals and custom fields — so months later you can see not just what was said to the customer, but the internal reasoning behind it. They're part of the account record, not a disposable message.
Do I need a new number to use internal notes?
No. Tenashi links your existing WhatsApp number with a QR scan — no new SIM, no porting, no migration. Your team starts leaving notes and @mentioning each other on the conversations you already have, on the number your customers already message.
Stop screenshotting customer chats into a side group. Start a free trial and put the whole team conversation where it belongs — inside the chat, invisible to the customer.