Booking appointments

A booking, as a record#

There is no appointment object in Connect. What exists after a successful booking conversation is a Person with the identity the caller used, a conversation or calls row holding what was said, and a Follow-up on a date with a reason attached. That is deliberately thin, and it is the part that matters: the commitment is written down where it will be chased, and the record of who agreed to what sits on the relationship rather than in somebody's memory of the call.

Reading the time back#

The most useful habit on a booking call is that the agreed time is repeated aloud before the call ends, in full, and written into the follow-up in the same turn. A misheard date is the failure that survives the call: most things in a booking are recoverable from the transcript, but a confident wrong Tuesday is not, because nobody has any reason to go back and check it.

1. Let the caller state a time in their own words.

   Result The transcript holds exactly what they said, which is what an audit later reads.

2. Have Connect repeat it back as a full date and time, never as a relative day.

   Result The caller corrects it on the call, when correcting is cheap.

3. Confirm in writing on the channel that fits — an email reply, or a WhatsApp message where the provider's session window allows one.

   Result There is something the customer can re-read, and a send record with the provider's own acknowledgement behind it.

4. Let the follow-up carry the reason and the date.

   Result It appears on the follow-ups screen with a reason attached, and a reminder or a call-back can be drained from it later.

What will not work#

Live availability

Connect cannot see whether a slot is free. It has no calendar integration, so two callers can agree the same time and neither conversation will notice. Whoever owns the diary is still the one preventing that.

Taking a deposit or quoting a fee

safe_sales refuses commercial terms Knowledge does not support, and the Assistant has no pricing right at all. The refusal is the designed behaviour, not a gap to work around.

A recording of the booking call

Recording is foundation — the capability is asked of the provider rather than assumed, and it is not enabled on the live carrier. You have the transcript and the summary, not the audio.

Handing the caller to a person mid-call

An escalation phrase queues a transfer and a supervisor can act on a live call, but a completed warm transfer depends on a provider capability that is not enabled. Plan the escape as a call-back, not a transfer.

A booking SMS on the live carrier

Outbound SMS is provider-dependent and the carrier on the live account carries none. readiness.messaging says so on the Phone screen rather than presenting a thread that cannot send.

Where the money goes#

Almost all of it is the call. A live voice session is billed on audio tokens — four times the same model's text rate on input and roughly 2.7× on output — and the session is re-billed for its whole context on every turn, which is why production calls run about 92% carried context by input token. A five-minute booking conversation costs meaningfully more than the twenty emails around it.

• Shorten the call, not the courtesy. Most of the spend is turns, and a booking that collects four facts should take four exchanges.
• Keep the instructions tight. Prompt size moves first-token time: around 7,500 characters measures 1.2–1.8 s, around 9,600 measures 2.3–3.4 s.
• Let email confirm. The written confirmation costs a fraction of the minute it would take to say the same thing twice.

A call is charged from its own duration at the published per-minute rate even when it reports no tokens, so an abandoned ring is not free and a call that dies mid-sentence is still billed for what it used.

Questions#

Related#

• Chasing appointments and commitments
• Creating a follow-up
• Due dates and times
• Promises made on a call
• Set business hours
• Price, SLA and warranty: what Connect may say