Internal notes and team alerts from a flow
The most useful automations often send the customer nothing at all. They tell your team something at the moment it matters.
Not every step in a flow is aimed at the customer. Four blocks exist purely to move information sideways — onto the conversation, onto a person's queue, or onto a colleague's phone — and they are the ones that turn an automation from a message sender into part of how your business runs.
They also cannot annoy anybody, which makes them the safest thing to add to a flow you are still nervous about.
The four blocks
| Block | Who sees it | Typical use |
|---|---|---|
| Add Internal Note | Anyone who opens the chat | Context: what the customer chose, what the flow worked out |
| Assign Chat | The agent or team it lands on | Routing: send this to the right person |
| Update Conversation Status | Whoever filters the inbox | Housekeeping: open, pending, resolved |
| Forward Template to Number | Phones you list | Alerts: reach someone who is not watching the inbox |
The first three act inside the shared inbox. The fourth leaves it, which is why it works differently and deserves most of the explanation.
Internal notes: write what the next person needs
An internal note attaches to the conversation and is invisible to the customer. The customer never sees it, never gets a notification, and cannot reply to it.
What makes a note useful is writing it for the colleague who opens this chat tomorrow knowing nothing. Not "customer replied" but "chose express delivery to Lahore, quoted 1,200, asked about a bulk discount".
Notes can include values the flow already collected, which is what makes them worth automating rather than typing. A note assembled from the customer's answers is a summary nobody had to write.
Assigning the chat
Assignment puts the conversation on a specific person's or team's queue. The two moments it is most valuable are both moments of failure or opportunity:
- When the bot cannot answer. The unanswered path of a knowledge base step, or the fallback of a menu, should assign rather than apologise.
- When the answer needs authority. A refund request, a complaint, a wholesale enquiry — things where a person should decide.
Assignment is also what makes measurement possible later: a conversation with an owner can be counted, and one without cannot. If you are trying to work out how much work the bot is actually absorbing, this block is where that data starts.
Conversation status, which sounds trivial and is not
Open, pending and resolved are how a busy inbox stays navigable. A flow that sets status deliberately keeps two things straight: your team's view of what still needs attention, and your reporting on how many conversations were genuinely handled.
The common pattern is to mark a conversation resolved when a flow has fully answered it and set it back to open the moment a customer replies afterwards. That way "resolved" means resolved rather than "the bot said something".
Alerting a phone: why it must be a template
Now the block that trips people up. Forward Template to Number sends to numbers you list — your operations manager, a warehouse phone, a partner — rather than to the customer in the chat.
It always sends an approved template, and that is not a limitation but the whole reason it works. Your colleague has not messaged your business number in the last 24 hours, so there is no open session with them; per Meta's sending messages documentation, free-form messages are only possible inside that window. A template is the sanctioned way to reach a chat outside it, per Meta's template documentation.
Practically that means one small piece of preparation: an internal alert template with variables for whatever you want carried across. The customer's message, an order number, a total. One template covers every alert you will ever build, because the variables change and the shape does not.
An escalation flow, end to end
Nothing sent to the customer except reassurance
Five internal steps and one line to the customer. That ratio is normal for the flows that matter most.
What these blocks cost
Notes, tags, assignment and status changes cost nothing — they send no message. The alert is the exception: a template to your colleague's phone is a template, and templates are billed under Meta's pricing documentation.
It is a small cost and usually an obvious trade, but it is worth knowing before you put an alert on a flow that runs two hundred times a day. If the alert is informational rather than urgent, an internal note plus a properly filtered inbox view does the same job for nothing.
Where teams get this wrong
- Alerting on everything. An alert that fires constantly is an alert nobody reads. Reserve it for things that need action within the hour.
- Notes written for the author. "Sorted" tells the next person nothing.
- Assignment with nobody on duty. Assigning to a team outside working hours means the chat sits unowned, which is worse than unassigned. See what to do with chats overnight.
- No alert template ready. The moment you need one urgently is the moment approval takes a day.
Frequently asked
Can the customer ever see an internal note?
No. Notes live on the conversation record in your inbox.
Can I alert several people at once?
Yes — the block takes a list of numbers, and each can be a literal or a value the flow already holds, such as an assignee's number saved on the contact.
Why not just send my colleague a normal WhatsApp message?
Because it will not arrive unless they happen to have messaged your business number in the previous 24 hours. The template is what makes the alert reliable.
Should the bot resolve conversations by itself?
Only when it genuinely finished the job. If in doubt, leave it open — an over-eager resolve hides work from your team, and the handover rules in bot to human handover apply.
Choosing between the four
A decision list that settles most cases in one pass:
- Does someone need to act within the hour? Alert a phone.
- Does someone need to own this conversation? Assign it.
- Does the next person need context? Write a note.
- Does the inbox need to stay tidy? Set the status.
Most escalation flows answer yes to three of the four, and the order above is the order to put them in — record first, route second, alert last, so the person who picks up the phone alert finds the context already waiting.
What a good note contains
| Weak note | Useful note |
|---|---|
| "Customer asked about delivery" | "Asked about delivery to Karachi, order 10482, wants it before Friday" |
| "Complaint" | "Item arrived damaged, sent a photo, asked for replacement not refund" |
| "Handled" | "Quoted 4,500 including delivery, they are checking with their partner" |
Three details is usually the right size: what they want, which order or product, and any constraint. Assemble it from values the flow already collected and nobody has to type it.
Alerts and the 24-hour rule, once more
It is worth being precise, because this is the part that surprises people. The customer service window is 24 hours long, opens when someone messages or calls your business number, and resets each time. Your colleagues are subject to exactly the same rule as your customers.
So an alert built as a plain message works during a test — because you had just messaged yourself — and then silently stops working in production, which is the worst possible failure pattern. Build it as a template from the start.
One internal alert template with 3 or 4 variables covers every alert flow you will build. Submit it early, alongside the order templates in order confirmation messages.
Alerts that earn their place
A short list of the moments genuinely worth waking somebody's phone up for, drawn from what stores actually build:
- A high-value order placed out of hours, where someone may want to check it before it ships.
- A cash-on-delivery order the customer declined to confirm, which is a parcel worth stopping.
- A complaint or a refund request, where a slow first response is the thing that escalates it.
- A wholesale or bulk enquiry, which is usually the largest opportunity in the inbox that day.
- An integration failure — a lookup that failed, a payment gateway that did not answer.
Five is about the right number. Beyond that you are training the recipient to swipe the notification away, and the one that mattered goes with it.
Notes as a record you will need later
There is a second reason to write notes from a flow, and it only becomes obvious months in: the conversation is the record. When a customer disputes what they were told, or a colleague asks why a refund was approved, the note is the evidence.
Automated notes are better evidence than typed ones because they are consistent. Every conversation that took a particular branch carries the same note in the same shape, which makes them searchable and makes patterns visible.