A missed call is a customer who chose the hardest channel
A person who called has already concluded that writing would not work. They wanted a person, and the unanswered call shows that their effort achieved nothing.
An immediate callback looks like the right move, yet it is often wrong. By then the customer has already gone into a meeting, and a second unanswered call adds cost rather than recovering it.
The channel is a judgment about that customer. Some customers reply to a text right away and never answer calls from an unknown number. Others read email within an hour. Some have only ever contacted the company by phone.
The content also matters. If a callback lacks context, the customer has to start over, which is exactly what they were trying to avoid by calling.
How the agent is built in Agent Studio
The system prompt includes callback windows based on your actual staffing, so the agent never suggests a time when no one is available, or a time outside the customer's working hours.
Prompt skills set the channel options and what each channel is appropriate for. A customer who has only ever used one channel probably prefers that channel.
The context comes from a flow. Twilio sends the missed-call event through a Webhook trigger. An HTTP Request node retrieves any open ticket together with the previous contact history. The Agent Chat node then requests a recovery plan.
The agent returns a channel, a time, and a draft message that refers to the open issue, rather than asking why the call was made.
A Wait node holds the flow until the suggested time. A Human in the Loop node releases the message. Twilio then sends an SMS or email, and Resend handles the written channels.
Google Sheets records which channel brought back which customer. After a few months, that table replaces guesswork about channel preference with actual data.
What this agent is built from
- System prompt: callback windows matched to real staffing and to the customer's plausible hours.
- Prompt skills: channel options and what each is appropriate for.
- Twilio (Integration): delivers the missed-call event and sends the SMS recovery.
- HTTP Request (Util): pulls the open ticket and contact history to provide context for the message.
- Agent Chat (Util): returns a channel, a time, and a draft referencing the open issue.
- Wait (Control): holds the flow until the proposed time rather than sending immediately.
- When an ActionFlow is enough: If an automatic callback ticket is enough, build the workflow. Choosing the channel and the moment is the agent's job.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.