The meeting was a no-show. The agent is already rebooking it.
An hour after a booked meeting ends, Underfive asks on Slack whether the lead joined. One click on No-show hands the thread back to the inbox agent, which apologises briefly, offers new times from the live calendar, and keeps the conversation going until another meeting is booked.
50 free credits · no credit card · template included
Half the meetings that get booked from cold outreach do not happen. Someone has to notice, write the awkward follow-up, and find new times. Usually nobody does, and a lead who already said yes goes cold.
How the No-show recovery workflow runs
One trigger, then each step in order. Every step has its own delay, and every outcome has somewhere to go.
Meeting booked
Any meeting booked by the agent, through Cal.com, Calendly, HubSpot, GoHighLevel, Google Calendar, a form, or by hand.
- 1
Ask on Slack
60 minutes after the meeting ends (you can set 15 minutes to 24 hours), a message asks “Did {lead} join the call?” with They joined and No-show buttons. Cancelled meetings are skipped and moved ones re-timed.
- 2
Hand back to the agent
On No-show, the inbox agent writes a short apology, offers a few new times, and runs the thread until the next meeting is booked.
- 3
Set a label
On They joined, mark the conversation Attended so your reports and CRM stay honest.
- 4
Sequence end
Each path ends with a reason you can read in the run list.
There is a template for this
Start from one that already works, then make the messages yours. The template lists what it needs connected and lets you read every message the agent will follow before you publish.
- A short, human apology on the channel the conversation was already on
- Two or three new times that are really free
- A rebooked meeting with a calendar invite
- One Slack question per meeting, answered with a click
- The run’s path on the canvas: who answered, when, and what the agent sent
- Attended and no-show counts per client
- An inbox agent with a connected calendar
- Slack connected to the workspace
- A review of the re-engage instructions the agent follows
No-show recovery questions
How does Underfive know the meeting was a no-show?
It asks. After the meeting ends, a Slack message asks whether the lead joined, with They joined and No-show buttons. The answer can also be given in the Unified Inbox. There is no calendar guesswork.
How soon after the meeting does it ask?
An hour after the scheduled end by default. You can set anything from 15 minutes to 24 hours. If the meeting is moved, the question moves with it, and a cancelled meeting is never asked about.
What does the agent say to a no-show?
It follows re-engage instructions you can read and edit in the template: a brief apology, a few new times from the live calendar, and it keeps the thread going until another meeting is booked.
Can I review the message before it goes out?
Yes. The inbox agent keeps its own approval setting, so the apology can wait for a click in Slack or the app before it is sent.
Does this work for every client in my agency?
Yes. Pick which inbox agents the workflow watches. Each lead is handled with its own agent’s calendar, sending account and voice, so one workflow can cover many clients.
Put No-show recovery on autopilot.
Connect your tools, publish the workflow, watch the first run on the canvas. Your first 50 credits are free.