Messaging Actions
Messaging actions let your agent send on a channel (email, SMS, WhatsApp or a messaging app such as Telegram) or place an outbound phone call. They also decide something more basic: whether your agent can reply on those channels at all.
You attach them to your AI Agent's Action port. The agent then uses them like tools: when the moment is right, whether that's a reply, an order confirmation, or a follow-up, it calls the action and the message goes out through your connected provider.

There are five messaging actions, under Actions → Messaging in the node picker:
| Node | What it does |
|---|---|
| Email Sender | Sends an email (subject, body, optional attachment). |
| SMS Sender | Sends an SMS. |
| WhatsApp Sender | Sends a WhatsApp message. |
| Chat Sender | Replies on a messaging app — Telegram, Slack, Messenger, Instagram, Microsoft Teams, Discord, Google Chat or RCS — in the chat the customer wrote from. |
| Phone Caller | Starts an outbound AI phone call. |
Your agent needs a sender to reply on email, SMS, WhatsApp and messaging apps
This is the most important rule on this page. An agent only sends on email, SMS, WhatsApp or a messaging app when the matching sender is wired to it:
| Inbound on… | Agent replies only if this is on its Action port |
|---|---|
| Email Sender | |
| SMS | SMS Sender |
| WhatsApp Sender | |
| Telegram, Slack, Messenger, Instagram, Microsoft Teams, Discord, Google Chat, RCS | a Chat Sender whose Messaging app is that app (one Chat Sender covers one app) |
| Web chat, web voice, phone | Nothing needed. Replies are delivered directly in the chat or on the call. |
Without the sender, an inbound message on that channel still starts the agent. The workflow runs, but nothing is sent back. That's deliberate: it lets you build agents that only take messages in, such as "log every WhatsApp enquiry to a sheet, never reply", without them unexpectedly messaging customers.
Because it's easy to forget, the canvas warns you. If an agent has, say, a WhatsApp trigger but no WhatsApp Sender, it shows a warning on the AI Agent explaining that replies will not be delivered on WhatsApp and telling you to add the sender. It's a warning, not a block, so a trigger-only agent can still be published.
Shared configuration
The Email, SMS and WhatsApp Senders and the Phone Caller share the same settings. The Chat Sender is simpler — see Chat Sender below.

Tool Name and Instruction
- Tool Name (optional): how the AI refers to this action, for example
send_booking_confirmation. Leave it blank to use the node's label. Give each one a distinct name when an agent has two senders for the same channel, such as a bill email and a reminder email. - Instruction (required): tells the AI when to use this action, what to pass, and what it returns. For example: "Send the booking confirmation once the customer has confirmed a date and time." The ✨ Ask AI link drafts one for you.
Send from / Call from (required)
The business email address or number the message is sent from, or on Phone Caller, the caller ID the call shows. Pick one from the list, which is filled from the numbers and addresses on your Connections. Each entry shows which connection it belongs to. Use Reload after you add a new one.
This is required. A sender without it can't be published, and the canvas outlines it in red with "Missing 'Send from' — pick a business number/email". If the list is empty, add the provider on Connections first.
There is no default sender: a message only leaves from a Send from that one of your connected accounts owns. If none does, every send from it is refused (and you're notified) — the builder warns you about this before you activate. See Sender Nodes.
Send to / Call
Who receives it:
- Let the AI decide: the agent chooses the recipient at send time from the conversation.
- The person in this conversation (default): the contact you're already talking to. A new sender starts here, and a sender saved without a choice sends here too.
- A fixed address / A fixed number: always the same recipient, such as a shared inbox or an on-call line.
If the Instruction names an address or number ("email the team at sales@acme.com") but Send to isn't fixed to it, the builder warns you before you activate and tells you where the message will really go — set Send to → A fixed address to send it there.
On Phone Caller the choices read Let the AI decide who to call, The person in this conversation, and A fixed number.
What to send
Message content has two modes:
- Let the AI write it (default): the agent writes the message from the conversation and your guidelines.
- Use a template or fixed text: you provide the wording. Extra fields appear:
- Load saved template: fills the fields below from a saved message template. You can still edit them afterwards.
- Subject (email only) and Body / Message: fixed or templated text.
{{ placeholders }}are filled at send time. Leave a field empty and the agent writes that part.
Guidelines for the AI (optional) is soft guidance (tone, length, what to mention) that the agent follows whenever it writes any part of the message.
If the recipient is a {{ variable }} that has no value in the run, nothing is sent: the action fails with a message naming the variable, so you can fix the step that should have set it.
If a send is refused or fails — the sender isn't owned by a connected account, the contact is on your suppression list, a daily limit is reached, or the provider rejects it — the agent is told why and that it shouldn't retry, so it can let the customer know the message couldn't be sent right now.
Placeholders vs. fixed text
Text with no placeholders is sent exactly as written, which is useful for approved or regulatory wording. Text with {{ placeholders }} is a template the agent fills from the conversation.
Per-node extras
Email Sender
- Subject: supports placeholders. Leave it empty and the agent writes the subject.
- Attach a file the AI generated earlier: when ticked, the most recent file the agent generated earlier in the turn, such as a PDF, is attached. (File creation is a built-in capability you turn on per channel on the AI Agent.)
SMS Sender and WhatsApp Sender
A single message body, no subject. Keep SMS short. On WhatsApp, a message sent outside the 24-hour customer-service window needs an approved template.
Chat Sender
The Chat Sender has Tool Name, Instruction, Messaging app (Telegram, Slack, Messenger, Instagram, Microsoft Teams, Discord, Google Chat or RCS — default Telegram) and Guidelines for the AI. There's no Send from or Send to: the reply goes to the chat the customer wrote from, through the connected bot they wrote to. It works on the Action port only — Activate refuses it as a flow step.

Phone Caller
Phone Caller places an outbound call and hands it to the agent. Instead of message content, it has a What to do on the call section:
- Call objective: Let the AI decide the objective (default), or I'll specify the objective to script it.
- With I'll specify, two fields appear: Call objective, which is what the call should accomplish, and Opening line (optional), the first thing the agent says when the call connects.
Using a sender as a flow step
Senders can also sit in the flow, after an AI Agent or any other step, to send a message when the workflow reaches that point. An example is sending a summary email after a call ends. Configuration is identical, and Send from is required there too. In Use a template or fixed text mode, a flow step fills the {{ placeholders }} in the body, subject and opening line itself from the run's data — for example Summary: {{call_summary}} after a call — and a placeholder with no value is left empty. As a flow step, a sender reports whether it sent and on which channel, so later steps can use the result.
A sender in the flow does not authorize the agent's own conversational replies, because a conversational agent answers each message without advancing the flow. To let the agent reply on a channel, wire that channel's sender to its Action port as described above.
Handing off to a person
Handing a conversation to your team is not a messaging action. It is set on the agent's Operator node, under Routing → When the AI hands off. Without that switch on, the agent has no hand-off at all.

With the hand-off on, you set:
- Hand off when — your instructions for when the AI should get a person (up to 500 characters).
- Try in this order — Web operators (with a ring style) and Phone operators (dialled one at a time, in the order listed), dragged into the order you want. AI operators on the Operator node's Team tab are offered to the AI as their own targets on calls.
- Ring each person for, seconds (5–120, default 30), Only web operators with this skill, If everyone is busy, wait in queue up to (s) (0–900, default 120; 0 = no queue) and Tell the caller their place every (s) (0 = never, otherwise 20–300).
- If nobody answers — Take a voicemail, or The AI keeps helping; the team calls back (default).
- When the person leaves the call — Back to the AI (default) or End the call.
- Flag the conversation and notify the team on every hand-off — with no group ticked and no AI operator, that is all the hand-off does.
On chats, a hand-off to web operators offers the conversation to the team; AI operators are not offered there. What the caller hears while being connected or on hold is set in the same tab, under Waiting sounds.
This is different from the Human Handoff node in the Core group, which pauses the workflow until a person acts. See Human Handoff.
Related
- Email, SMS, WhatsApp, Messaging Apps (for Chat Sender), and Voice (for Phone Caller): provider setup and channel behaviour.
- Connections: connect the providers these actions send through.
- Operator: your team on this agent — who answers, the hand-off, supervision and the copilot.