Guide · Voice confirmation

Voice AI to confirm clinic appointments

Outbound confirmations can use sequential, power, or parallel dialer plus AMD; phone replied is STT, not intent to attend. Use voice when WhatsApp is silent before a slot — not as a diagnostic line and not as a promise they will show.

Dialer + AMD on confirm calls
STT ≠ they will attend
Canonical job is appointment reminder

Start free Appointment reminder playbook

Definition

Voice confirmation is an outbound call hop that asks the patient to confirm or reschedule a calendar hold. Answering-machine detection (AMD) and dialer mode (sequential, power, or parallel) are phone-channel mechanics. Speech-to-text ‘replied’ is not a show-rate event.

Why voice gets treated as a second doctor

A clinic lets the bot discuss symptoms on the confirm call. Families hear advice. The real job — confirm or reschedule — never finishes. AMD voicemails become rambling clinical messages.

Appointment reminder is the job. Voice is a hop beside WhatsApp templates. Keep avoid-topics on the call: no diagnosis, emergencies to emergency services.

HowTo: confirm without playing doctor

Pick dialer mode for the day’s volume. Enable AMD so voicemail does not burn an agent minute on silence. Script confirm/reschedule only. Write outcomes on the contact. Do not mark Consult done from STT.

Connect phone Setup → Channels → Plivo. Healthcare overlay explains confirm use, not a call-centre HIS.
Choose dialer mode Sequential, power, or parallel — match staff capacity. AMD on.
Script confirm only Slot, doctor name from catalog, reschedule offer. Avoid-topics: diagnosis, treatment advice.
Emergency line If they describe an emergency on the call, tell them to call emergency services.
Log STT, move pipeline by policy Reminder playbook + ops. Show-rate uses Consult done, not ‘replied.’

How it runs on the platform

Voice is a conversation or outbound agent on the phone channel. It is not an autonomous checkup list. 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: hospital OPD confirm list

Tomorrow’s cardiology roster: WhatsApp template at 18:00, then parallel dialer for silent rows. AMD drops voicemail with the slot time. STT ‘yes’ stays on the contact. Ops still mark who arrived. No diagnosis on the recording.

Channel: healthcare phone. Sibling no-show how-to.

Voice outcomes vs pipeline

Do not equate telephony events with consults.

Telephony event	What it means	Pipeline	Do not
AMD voicemail	Machine, not a person	Still Appointment booked	Diagnose on voicemail
STT replied	Speech-to-text on the call	Contact field	Treat as show
Human handoff	Desk continues on inbox/softphone	Same contact	Start a personal mobile
No answer	Retry policy you set	Unchanged	Mark Consult done

Honest limitations

Voice is not HIS. Not an emergency line. Wallet meters minutes. Softphone and dialer are phone-channel features, not a second CRM.

Keep this Voice confirmation 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: Appointment reminder 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.

Playbook: appointment reminder. Product: phone & voice AI. No-show recovery remains a separate job.

Frequently asked questions

Operators implementing this mechanic on a healthcare Project.

Does ‘replied’ on phone mean they will attend?

No. Phone replied is speech-to-text, not intent to attend.

Which dialer modes exist?

Sequential, power, and parallel, plus AMD — as the phone channel documents.

Can the confirm bot diagnose?

No. Avoid-topics and emergency redirect still apply on voice.

Which playbook?

Appointment reminder.

SMS confirm?

Pricing?

Wallet-only. Minutes meter from the Organization wallet.

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

Confirm the slot, do not practise medicine on the call

Dialer plus AMD, STT logged honestly, Consult done only when they attend.

Get started free