Guide · Speed to appointment

Speed to appointment: first message, then a slot offer

Speed is time-to-first-message and time-to-slot-offer on a connected channel; there is no marketed minute-SLA product name. A web form that sits until morning is not speed. A WhatsApp ‘hi’ without a calendar offer is not a booked consult.

First message on the same contact
Slot offer from calendars, not a vibe
Canonical job is enquiry capture

Start free Enquiry capture playbook

Definition

Speed to appointment is how fast a New enquiry gets a first reply on a connected channel and a concrete slot offer from Appointments/calendars. It is an operating metric you measure, not a CoPulse product SKU with a minute SLA.

Why ‘we reply fast’ still loses the slot

The desk answers ‘yes we have dentists’ in twelve minutes and never opens calendars. The family books a competitor who offered 9:00. Walk-in QR and Meta leads die the same way: a greeting without a slot is courtesy, not capture.

Enquiry capture is the job. Speed is the mechanic. If the qualifier waits for four fields, still offer a provisional window once location and times exist — do not wait for a diagnosis that will never come.

HowTo: shrink time-to-slot-offer

Connect the capture channel to the Project inbox. Route to the qualifier. Keep calendars current. Staff handoff for overflow. Do not invent a minute-SLA name on the pricing page.

Connect capture Web widget, walk-in QR, Meta leads, and WhatsApp all create New enquiry on one Project.
First message from the Project number Conversation agent greets on WhatsApp. Personal doctor phones are not speed — they are a vanished inbox.
Offer a slot from calendars Appointments/calendars hold truth. The Appointment booked column moves when booking succeeds or a human says so.
After hours Inside 24h, free-text. Outside, approved template.
Measure two clocks First message time and slot-offer time. Campaign conversion remains reply rate unless you track Appointment booked.

How it runs on the platform

Capture is a conversation agent plus calendars. Autonomous lists are not how a new web lead gets a same-day slot. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not appointment booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup. The qualifier does not diagnose.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not appointment booked.

Worked example: independent practitioner, one Project number

A solo dentist’s website widget identifies the visitor, continues on WhatsApp, asks location and preferred_times, offers Friday 9:00 from calendars. Inbox shows the thread if they ask about fees. Stage New enquiry until booked. No minute-SLA widget on the site.

Also see walk-in QR and web chat to WhatsApp.

What speed is and is not

Operators confuse greeting speed with booking speed.

Clock	Good enough	Not speed	Where it lives
Time-to-first-message	Agent or human on the Project inbox	A personal doctor WhatsApp	Inbox + channels
Time-to-slot-offer	Calendar times on the thread	‘We will call you’	Appointments/calendars
Time-to-Appointment booked	Workflow or human after a hold	Autonomous send count	Pipeline column
Campaign conversion	Reply rate unless you track stage	A marketed minute SLA	Growth analytics

Honest limitations

There is no marketed minute-SLA product name. Autonomous success is not the slot. Web Push is a different Setup channel than this overlay.

Keep this Speed to appointment article next to the job URL, not as a second playbook. Cite the definition above when an operator asks what the term means. Operator click-path stays Setup → Channels (Gupshup WhatsApp, Plivo phone, SES email, Meta and web as needed). Library templates. Agents → Studio, Router, Workflows, Autonomous. Customers → Pipeline. Appointments/calendars. Growth campaigns/drips. Organization wallet preview. Canonical playbook: Enquiry capture playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Appointment booked on the pipeline. Phone “replied” is speech-to-text. Qualifier is non-diagnostic. Emergencies: call emergency services. Not HIS/EMR. Preview the Organization wallet before a blast. Parent guides, healthcare hub, and pricing stay in the same runbook.

Capture siblings

Website: web chat to WhatsApp. Ads: Instagram ad to slot. Playbook: enquiry capture.

Frequently asked questions

Operators implementing this mechanic on a healthcare Project.

Do you sell a 60-second SLA?

No. Speed is an operating metric: first message and slot offer. There is no marketed minute-SLA product name.

Does a ‘hi’ count as speed?

Only as time-to-first-message. Time-to-slot-offer still needs calendars.

Walk-in QR?

Same mechanic, same enquiry-capture family. One speed guide.

After hours?

Templates outside 24 hours.

Which playbook?

Enquiry capture.

Wallet?

Usage meters from the Organization wallet. No seat fees.

Hub, sibling guides, canonical playbook, product, pricing.

Reply, then offer a calendar time

Connect web and WhatsApp on one Project so New enquiry does not wait until morning.

Get started free