The booking agent, designed before it is promised.
A conversation agent that qualifies, answers, and holds context across messages and restarts, with bookings as a later phase behind human approval. This page describes the design specification; nothing here ships today.
- Internal design spec exists; no public artifact yet
- v1 scope: persistent conversation memory plus an idempotency guard so it never double-acts
- Bookings arrive only after a human-approval gate exists
Lock the conversation first
The v1 win is continuity: the agent never loses context across messages or restarts. Answers, qualification, and handoff come before any transactional action.
Idempotency is non-negotiable
Webhooks redeliver and clients double-tap. One confirm produces one appointment, ever. The design treats duplicate execution as the primary failure mode.
Humans gate the money path
Live booking execution lands in v2, behind explicit approval. Availability truth comes from the booking tool, never from the model.
// v1 goal: lock the conversation
// - persistent conversation memory across messages and restarts
// - idempotency guard: one action, never two
// v2: live booking executor behind a human approval gateCan I install this today?
No. Chat is in design. Join the waitlist and you will hear when a public artifact exists.
What does it run on?
Uncommitted design work points to WhatsApp and site chat channels. The channel decision is not final, which is exactly why nothing is promised here.
Why publish a page for something unbuilt?
So the design is public and falsifiable. When it ships, this page documents reality instead of inventing it retroactively.