Five lines, under 200 words, readable one handed on the walk between two meetings. That is a strange instruction to hand a harness known for being thorough, and it is the one deciding whether the brief gets read at all. Claude Code follows written constraints closely, so the research it does behind the scenes stops at the edge of the message instead of spilling into it.
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.
Technical demo (45 min)
ConfirmedCamila Fuentes · c.fuentes@andesretail.cl
Booked for Tuesday 26 August at 09:30 America/Santiago, second time this person has booked with us. What should we cover: stock counts are done by hand twice a week across 30 stores and finance no longer trusts the numbers. Who else is coming: our head of IT and one store manager. Anything in the way: we need the interface in Spanish and invoicing in Chilean pesos.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Cal.com
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect HubSpot
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.
Positioning notes
What you actually want said on these calls: your one line pitch, the proof you lead with for each type of meeting, the objections you expect and the answers you stand behind. Say here too whether a rescheduled booking should get a fresh brief.
Runs on Claude Code
Preselected for this page — connect your Claude Code 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.
The booking, the event type, the invitee's earlier bookings, the HubSpot contact and its deals are all read. Almost none of that survives into the message, which is the point.
An empty company field tells the rep what to ask on the call. A company inferred from an email domain sends them in believing something nobody checked.
In practice it holds, because the limit is written into the instructions rather than implied. Where it drifts, the cause is usually the positioning notes: a long list of proof points invites a long brief. Read a few briefs on real bookings in the first week and trim what you asked for.
Free to start. Guided setup, a test run against staged conversations, and it's live.