Skip to main content

Customer service

Team alerts from a WhatsApp flow: tell the right person the moment it matters

Most important messages do not need an answer from a bot. They need a person to notice them in time. Here is how the Notify Agents node sends a push notification or an email to the right agents from any flow, with six recipes and the texts to use.

MonoChat Team Updated: 6 min read

On this page
  1. Why speed of noticing matters
  2. How Notify Agents works
  3. Recipe 1: a VIP writes
  4. Recipe 2: a customer asks to cancel
  5. Recipe 3: the AI agent cannot finish
  6. Recipe 4: a payment link could not be created
  7. Recipe 5: a conversation is left without an owner
  8. Recipe 6: an important order arrives from your store
  9. Writing alerts people act on
  10. What to check before you switch it on
  11. What it costs

Some customer messages are urgent for your business but not for a bot. A long-standing customer writes for the first time in months. Someone asks how to cancel their subscription. The AI agent runs out of budget halfway through a refund question. A payment link could not be created for an order. In each case the right answer is a person, and the problem is that the person does not know yet.

Shared inboxes solve part of it: the message is there for whoever looks. But “whoever looks” is not a process. The Notify Agents node, released in MonoChat 3.8.48 on 10 November 2026, lets any flow send a push notification, an email or both to exactly the agents who should act, with the customer’s name and message in the alert. This guide explains how it works and gives six recipes you can rebuild in minutes.

Why speed of noticing matters

Customers on messaging channels do not wait long. In Emplifi’s 2025 survey of nearly 1,000 US consumers, about a third expected a reply on social media within one hour, most within 24 hours, and only 4% were willing to wait 72 hours or more. 37% named slow responses as a factor in a negative experience (Customer Experience Dive, 4 April 2025).

On WhatsApp there is a second clock. When a customer messages you, a 24-hour customer service window opens, and after it closes you can only reach them with an approved template. A cancellation request noticed the next afternoon is a request you can no longer answer in free text. Getting the right person to look within minutes keeps both clocks on your side.

How Notify Agents works

Add Notify Agents from the action nodes in the flow designer. It has five settings:

SettingWhat it does
RecipientsAgent assigned to the session: whoever holds the conversation when the node runs. Agents of a workgroup: the agents of the chosen Workgroup; turn on Only active agents to skip those who are away. Chosen agents: up to 50 agents you pick. Only agents of your workspace can be chosen; for more than 50, use a workgroup.
NotificationA push notification in the browser and in the MonoChat mobile app. When the flow belongs to a conversation, tapping it opens that conversation.
EmailAn email to the agent’s verified address.
TitleThe notification title and the email subject, up to 100 characters.
TextThe notification text and the email body, up to 1,000 characters.

Turn on Notification, Email or both. Title and text accept {{key}} variables, for example {{customer.profile.firstname}}, {{message.text}} or {{flow.order.id}}.

Three rules keep it safe:

  • Nothing reaches the customer. The node writes nothing in the conversation.
  • One alert per agent per run. If a flow loops back through the node, the same agent is not notified twice in that run.
  • No dead ends. If there is nobody to notify, for example because the conversation is not assigned yet, the flow continues on Output.

Each agent stays in control of what they receive. Flow Notifications in their notification settings has a Notification and an Email switch, both on by default, covering every flow of every workspace they belong to.

Recipe 1: a VIP writes

Goal: the account manager knows within seconds when a key customer opens a conversation.

  1. New Session Created.
  2. If with the Customer Tag condition: includes vip.
  3. On true, Notify Agents to Chosen agents (the account managers), Notification on.
Title: VIP message from {{customer.profile.firstname}}
Text:  {{message.text}}

If you tag VIPs during a conversation rather than before it, start a second flow with Customer Tag Added listening for vip, as in our guide to tag-triggered automation.

Recipe 2: a customer asks to cancel

Goal: your retention team sees every cancellation request before it turns into a lost customer.

  1. New Message Received.
  2. If with a Message condition: the text includes cancel (add the words your customers actually use, in each language you serve).
  3. Set Customer Tag cancel-request, then Assign Session to the retention workgroup.
  4. Notify Agents to Agents of a workgroup (retention), Only active agents on, Notification and Email on.
Title: Cancellation request: {{customer.profile.firstname}}
Text:  The customer wrote: "{{message.text}}". The chat is assigned to Retention.

The email is the safety net: if nobody in the team is in front of a screen, the request still lands in an inbox they check.

Recipe 3: the AI agent cannot finish

Goal: when the AI agent stops, a person picks up the conversation before the customer notices.

The AI Agent and AI Conversation nodes leave on Budget Exceeded, Timed Out or On Fail when a run does not complete. Connect those outputs to:

  1. Assign Session to your support workgroup.
  2. Notify Agents to Agent assigned to the session, Notification on.
Title: The AI agent handed over a chat
Text:  {{customer.profile.firstname}} is waiting. Last message: "{{message.text}}"

The order matters: assign first, then notify the assigned agent. If the chat is still unassigned when the node runs, nobody is notified and the flow continues on Output, where a second Notify Agents node can alert a supervisor instead. More on designing the hand-over itself in AI to human handoff.

Goal: an order never stalls silently because of a payment problem.

The Send Payment Request node takes its failed output when the amount is not a positive number or no payment system is set up. Connect that output to Notify Agents, Chosen agents (your finance or operations lead), Email on.

Title: Payment link failed for {{customer.profile.firstname}}
Text:  The flow could not create a payment link for this conversation. Please check the order and send the link by hand.

Once the customer pays, the New Payment Received event can start a separate flow, for example to thank them and tag the order.

Recipe 5: a conversation is left without an owner

Goal: no chat falls between two shifts.

  1. Session Unassigned.
  2. If with Session Status: open.
  3. Notify Agents to Agents of a workgroup (team leads), Only active agents on.
Title: Unassigned chat: {{customer.profile.firstname}}
Text:  A conversation was unassigned and is still open. Please assign it.

Combine it with your routing rules from routing conversations to workgroups so the alert only fires for chats your routing does not catch.

Recipe 6: an important order arrives from your store

Goal: sales hears about high-value or unusual orders while the customer is still in the chat.

  1. Webhook Received, with your store’s order webhook sending to the node’s URL. Turn on Require Secret so only your store can start the flow.
  2. In the node, turn on Save Flow Variable to keep the order’s ID and total from request.body for later nodes, then add an If with a Flow condition on the total.
  3. Notify Agents to Chosen agents (sales), Notification on.
Title: New order {{flow.order.id}} over your threshold
Text:  Check the customer's chat for questions about delivery or payment.

Writing alerts people act on

  • Lead with the who and the why. The title shows on a phone lock screen: “Cancellation request: Sara” beats “New notification”.
  • One action per alert. Say what to do: assign, call back, send the link by hand.
  • Write in your team’s language. Every recipient gets the same text, whatever language the customer wrote in.
  • Prefer a workgroup over a list of names. People join and leave; a workgroup with Only active agents follows your roster.
  • Use email for things that can wait an hour, push for things that cannot. Turning both on for everything teaches people to ignore both.

What to check before you switch it on

  1. Every recipient has the MonoChat mobile app installed if you rely on push notifications away from the desk. See the team inbox on mobile.
  2. Agents who receive email alerts have a verified address.
  3. Test each recipe from your own phone and confirm who receives what.
  4. Look at your support metrics a week later: first response time on the chats you alert about should drop.

What it costs

Notify Agents is part of MonoChat’s flows. MonoChat’s Basic plan is free and Growth is $120 a month. Messages you send to customers on WhatsApp are billed by Meta directly, and MonoChat, an official Meta Business Partner, adds no markup.

FAQ

Frequently asked questions

What does the Notify Agents node do?

It sends a push notification, an email or both to agents when a flow reaches it. You choose the recipients: the agent assigned to the session, the agents of a workgroup, or agents you pick by name. Nothing is written in the conversation, so the customer sees nothing.

Where do agents receive the notification?

In the browser and in the MonoChat mobile app. When the flow runs for a conversation, tapping the notification opens that conversation. The email goes to the agent's verified address.

Can I put customer data in the alert?

Yes. The title (up to 100 characters) and the text (up to 1,000 characters) can use {{key}} variables such as {{customer.profile.firstname}}, {{message.text}} or a flow variable. Every agent receives the same text, so write it in your team's language.

Can a looping flow flood my team with alerts?

No. A Notify Agents node notifies each agent at most once per flow run, even if the flow passes through it again.

Can an agent turn these alerts off?

Yes. Flow Notifications in each agent's notification settings has a Notification and an Email switch, both on by default. The setting covers every flow of every workspace the agent belongs to.

What happens if there is nobody to notify?

The flow continues on Output. That happens, for example, when the node is set to the assigned agent and the conversation is not assigned to anyone yet.

First month of Growth on us

Run WhatsApp, Instagram and Messenger from one inbox

Start free with MonoChat: shared team inbox, AI assistants, templates and campaigns on official Meta APIs.

One code per business • 30 days to redeem • No card needed

$150 to get started.

Claim