Calendly No-Show Recovery Agent with OpenCode
This is the one template in this set whose output is prose a customer will read: two or three sentences, one booking link, one specific alternative time, and a line reusing something they typed when they booked. Model choice shows up directly in whether that reads like a colleague or a mail merge, and OpenCode is the harness built around letting you choose.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Discovery call (30 min)
ConfirmedSofia Kowalczyk · s.kowalczyk@vantopharma.pl
Marked as a no-show for Tuesday 5 August at 09:00 CEST, hosted by Nadia. She typed at booking: what are you hoping to fix, we run trial logistics across 40 sites and scheduling is still spreadsheets; where did you find us, a LinkedIn post; anything we should know, I am usually in the lab before 10. Two earlier meetings with this team were attended.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Calendly
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Rebooking policy
How you follow up when somebody misses a call: how long you wait, the tone and length you want, the booking link to send, what you will and will not offer to win the meeting back, and how many misses before a rep takes over instead of another email.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
Prose is where models differ
Every other output here is a list or a number. A short warm note is the one place where the engine you connect is visible to somebody outside your company.
Two models, one policy
The rebooking policy, the link and the wiring stay fixed while the engine changes, so a comparison comes down to reading two sets of drafts written against identical rules.
Before you fork
The policy says never offer a discount. Does an open model hold that?
The instruction explicitly rules out floating a discount, holding a slot, or promising a call back that is not written into the policy, and how firmly that holds does vary by model. Because nothing sends on its own, checking is cheap: read a fortnight of drafts in Gmail before anyone presses send, and change the engine if they start improvising.
Run it with a different agent
Put Calendly No-Show Recovery Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.