01 · How it works, in 5 steps
How does internal notes work?
- 1
Switch the composer to Note
Most inboxes have a Reply / Note toggle on the message box. Check the mode before pressing Enter; good inboxes colour the box differently in note mode so mistakes are obvious.
- 2
Write what the next person needs
State what was checked, what was decided, and what is still open: order number, steps tried, promised callback time. Skip opinions about the customer.
- 3
@mention the right teammate
Mentioning a colleague or team in a note sends them an in-app notification without reassigning the chat, which is how agents ask finance or a supervisor a question mid-conversation.
- 4
Leave a handover note before transfer
Before a chat transfer or escalation, add a summary note so the receiving agent can read one line instead of scrolling the whole history.
- 5
Review notes in QA
Include notes in conversation reviews: they show whether agents documented decisions and whether anything sensitive was written where it should not be.
02Try it
Hands-on: use the controls to work through it yourself.
Follow a note down the stack — and see where it stops
PayloadInternal note
Enters at the top, travels down through 5 layers
Hop 5 of 5: the payload is in layer 5, Customer's WhatsApp. Sees nothing. Only replies sent through the API ever arrive here.
03What is internal notes?
Internal notes are private comments that agents attach to a WhatsApp conversation in a shared team inbox. They appear in the conversation timeline next to the customer's messages, usually on a different background colour, but they are visible only to people with access to the inbox. The customer never sees them, because a note is never sent through the WhatsApp Business API.
Technically, a note is a record in the inbox's own database, linked to the conversation and stamped with its author and time. A reply goes the other way: the inbox posts it to the Cloud API /{PHONE_NUMBER_ID}/messages endpoint and it is delivered to the customer's phone. Because notes never touch that endpoint, they create no message ID, no delivery status and no charge.
Internal notes are easy to confuse with canned responses, but they do opposite jobs. A canned response is saved text that agents insert and send to the customer; an internal note is written for colleagues and stays inside the team. Notes are also different from conversation tags: a tag is a short label for reporting, while a note carries the context a person needs to act.
Key takeaways
- Internal notes are private comments on a WhatsApp conversation that teammates can read and the customer never receives.
- Notes live only in the inbox database; they are never sent to the WhatsApp Cloud API, so they cost nothing and cannot be delivered.
- Use notes for handover context, @mentions and decisions, so the next agent does not ask the customer to repeat themselves.
- Never put full card numbers, OTPs or passwords in a note; notes are stored, searchable and often exported.
04 · Mistakes to avoid
Common mistakes with internal notes
Typing a note in reply mode
The classic mistake: a candid note goes to the customer as a WhatsApp message, and it cannot be unsent from their phone. Use an inbox that colours note mode clearly, and train agents to check the toggle.
Writing sensitive data in notes
Notes are stored, searchable and exported with the conversation. Never record OTPs, full card or account numbers, or passwords; reference a masked value or a secure system record instead.
Treating a note as an assignment
An @mention notifies a colleague but does not make them the owner. If someone else must act, reassign the chat as well, or it will sit in the original agent's queue.
Notes that only make sense to the writer
"Done, see above" helps nobody on the next shift. Write notes as if the reader joined today: what happened, what is next, and by when.
05Example: A Kochi insurer hands over a claim between shifts
A motor-insurance team in Kochi handles claims on WhatsApp across two shifts. At 17:55 the day agent adds a note: "Claim 88213 — photos received, surveyor visit booked Tue 11:00, customer wants SMS confirmation too. @claims-team please confirm garage." The evening agent picks up the chat when the customer asks about the garage, reads one note instead of forty messages, and answers in under a minute. The customer saw none of this; they only saw a fast, informed reply.
06 · Key facts
Internal notes: key facts and limits
- Visible to
- Inbox users with access to the conversation
- Sent to the customer
- Never — not posted to the Cloud API
- WhatsApp charge
- None, because nothing is delivered
- Effect on the 24-hour window
- None; only customer messages open it
- Typical metadata
- Author, timestamp, @mentions
07 · Why it matters
Why does internal notes matter?
WhatsApp support is rarely handled start to finish by one person. Chats move between shifts, from first-line agents to billing or technical teams, and from bots to humans. Without notes, each handover means the customer explains the problem again — the most common complaint in chat support. A two-line note ("Refund approved by finance, waiting for bank reference") lets the next agent continue the conversation instead of restarting it, and leaves an audit trail of who decided what.
08 · Pro tips
Best practices for internal notes
- Use a fixed handover format: issue, checked, decided, next step.
- Mention a team rather than a person when the right individual may be off shift.
- Keep notes factual and polite; customers can request their data, and notes may be part of it.
- Pin the most important note so it stays at the top of a long thread.