Internal notes and @mentions in a chat
The conversation is the record. A note is how the next person knows what happened without reading all of it.
An internal note is a message attached to a conversation that only your team can see. The customer receives nothing, is not notified, and cannot reply to it.
It is the simplest feature in a shared inbox and the one that most changes how a team of more than two people works, because it is what lets a conversation be handed over without being re-read.
What a note is for
| Situation | The note |
|---|---|
| Handing over at the end of a shift | Where you got to, and what you promised |
| A decision that needed judgement | What you decided and why |
| A customer with history | Context the transcript does not show |
| Something you did outside the chat | "Called the courier, they will redeliver Thursday" |
| A promise with a date on it | So somebody can check it happened |
The fourth row is the one teams under-use. Work that happens outside WhatsApp — a phone call, a supplier email, a warehouse check — is invisible unless somebody writes it down, and the conversation is the natural place.
Writing one somebody else can use
The test is whether a colleague who knows nothing could pick this conversation up cold. That usually means three things: what the customer wants, what has been done, and what happens next.
- Weak: "Sorted."
- Weak: "Spoke to customer."
- Useful: "Wants to swap the blue for the green, same size. Told her we'd cover return postage. Waiting on the parcel, order 10482."
Twenty extra words, and it removes a five-minute reconstruction for whoever opens it next.
Mentions
Typing @ in a note lets you pull in a specific colleague or a whole
team. Use it when the conversation needs somebody who is not watching it:
- A question only one person can answer — a price, a stock level, a decision about a refund.
- Escalation, where a manager needs to see it rather than take it over.
- Handing to a specialist team without transferring ownership yet.
Mentioning a team rather than a person is the better move when anybody in that group could answer — it avoids the conversation waiting on somebody who happens to be off today.
Mention or assign?
A distinction worth being deliberate about, because using the wrong one is how conversations end up with two owners or none.
| Mention | Assign | |
|---|---|---|
| Means | "I need something from you" | "This is yours now" |
| Ownership | Stays with you | Moves |
| Use when | You need an answer to continue | Somebody else should handle it |
If you are still the person talking to the customer, mention. If you are not, assign — the mechanics are in assigning chats to the right agent.
Notes an automation writes
Your flows can add notes too, which is where this stops being a manual habit and becomes reliable. A flow that has just asked four qualifying questions can write the answers into a single note, so whoever picks the chat up starts informed.
Automated notes are more consistent than typed ones — every conversation that took a given path carries the same note in the same shape, which makes them worth reading. That side is in internal notes and team alerts from a flow.
Two things to be careful about
Notes are a record. Written in irritation, they are still there months later when somebody disputes what happened. Write them as though they will be read out, because occasionally they are.
Notes are not private. They are hidden from the customer, not from your colleagues, and access follows whatever roles you have set — which is a reason to keep them factual. Who can see what is covered in roles in a shared inbox.
Notes and the clock
One small relief: a note is not a message to the customer, so it is not subject to the 24-hour customer service window in Meta's sending messages documentation, and it costs nothing. You can annotate a conversation that closed last week.
That makes notes the right tool for recording an outcome you cannot yet tell the customer about, which happens more than you would think.
Frequently asked
Can the customer ever see a note?
No. They are internal to your inbox.
What if I type a note into the wrong box?
Check which mode the composer is in before you press send — the note mode is labelled. This is the mistake worth being slightly paranoid about.
Do mentions notify people?
That is their purpose — to get a specific colleague or team to look at this conversation.
Should every conversation have a note?
No. Most are self-explanatory. Note the ones where something happened that the transcript does not show.
A note-writing convention
Teams that get value from notes almost always converge on the same shape. 3 parts, one line each:
- Want: what the customer is trying to achieve.
- Done: what has happened so far, including outside the chat.
- Next: what should happen, and by when.
Thirty seconds to write, and it makes a conversation legible to somebody who has never seen it. Agreeing the convention matters more than which convention you pick — 1 shared habit beats 6 personal styles.
When a note is better than a reply
| Situation | Why a note |
|---|---|
| You have found out something the customer should not hear yet | Record it now, tell them when it is confirmed |
| The window has closed | A note costs nothing and needs no template |
| You are handing over mid-problem | The next person needs your reasoning, not your wording |
| A promise has a deadline | So somebody can check it happened |
That second row is worth remembering. Once a conversation is past 24 hours you cannot message the customer freely under Meta's sending messages documentation, but you can still annotate it — so a chat you cannot reply to is still a chat you can leave in a usable state, and inside the window everything remains free under Meta's pricing documentation.
Notes as the handover mechanism
The single highest-value moment for a note is the end of a shift. A conversation handed over with no note is a conversation the next person has to reconstruct, and reconstruction is where promises get dropped.
A shift-end habit that works: before you log off, open anything still assigned to you that is not finished, and leave one note each. For most agents that is a handful of conversations and about three minutes.
What good looks like across a team
- Every unfinished conversation carries a note by the end of a shift.
- Notes say what was promised, not just what was discussed.
- Mentions go to a team when anybody could answer, and to a person when only they can.
- Nobody writes anything in a note they would not say out loud.
- Flows write the routine ones so people only write the judgement calls.
None of that needs a policy document. It needs one conversation with the team and a fortnight of doing it — and the rota context sits in agent shifts and out-of-hours cover.
Common questions
Should I note every phone call?
Any call that changed something, yes. A call nobody records is work your business cannot see.
Can I mention someone who is off shift?
You can, and it will wait for them. If it needs answering today, mention the team instead.
What if the note turns out to be wrong?
Add a correcting note rather than pretending the first one did not happen. The sequence is the record.
Do notes count towards anything?
No. They send nothing, cost nothing, and are not subject to any Meta rule.
The short version
Notes are team-only, cost nothing, and are not subject to the 24-hour window. Write what the customer wants, what has been done, and what happens next. Mention a person when only they can answer and a team when anybody could, and assign instead of mentioning when the conversation should change hands.
The single habit worth adopting: a note on every unfinished conversation before you log off.
What changes when a team adopts them
The observable difference is that customers stop being asked to repeat themselves. A conversation picked up by a second person continues rather than restarting, which customers notice immediately even though they cannot see the note that made it possible.
The second difference is quieter: work done outside the chat becomes visible, so the business can see that somebody called the courier, chased a supplier or authorised a refund. Without notes, all of that effort simply never happened as far as any record is concerned.
Starting from nothing
If your team writes no notes today, do not introduce a convention and a training session. Pick the one moment that hurts most — usually the end of a shift — and ask for a note on unfinished conversations only.
That is a small enough ask to survive a busy week, and it produces the visible benefit fastest, because the person picking those conversations up the next morning notices immediately. Everything else follows from people wanting more of that.