Overdue screening lists get campaigns or autonomous sends; success is contacted, not a booked slot, until calendars or a workflow say so. hc-reengage is inspiration (WhatsApp + email, strip any SMS if a variant adds it). Campaign conversion is reply rate unless Appointment booked is tracked on the pipeline.
Annual checkup reactivation is segmenting Recurring patient (or a list), sending approved templates via campaigns or autonomous agents, and only then running qualification and appointment-booking for people who reply.
hc-reengage copy says “book in 2 taps.” Taps that do not write Appointments are not bookings. Autonomous does not stop when booked. Do not add Overdue as a stage. HIS is not this list’s source of clinical truth — it may be an import.
Pool in Recurring patient → blast → reply → qualify → calendars → Appointment booked.
Autonomous or Growth for the list. Conversation agent on reply. Three systems, no shared stop-when-booked. Autonomous agents may send a list-based recall after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not appointment booked. Move the pipeline with a workflow or by hand. WhatsApp live catalog is Gupshup. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a personal doctor phone that vanishes when the receptionist leaves.
Patient Inquiry Qualifier (reason, service_need, location, preferred_times). Catalogs: Departments, Doctors, Beds, Services — not a chart. Emergency utterances: call emergency services. Inbox handoff. Do not agent.run a diagnostic screening on the blast.
Agents → Workflows on stage change: agent.run, route.agent, crm.set_custom_properties, crm.update_stage, crm.create_task, templated send.whatsapp/email. Not adaptive nurture.
Clock-based sequences and list blasts with wallet preview. Campaign conversion is reply rate unless you also track Appointment booked on the pipeline.
Keep a dental bot off a health-check reply. Route by stage, channel, or campaign.
One Organization, one Project. Healthcare pipeline labels. Wallet-only. Library kits are sketches — rewrite hops without SMS and without a diagnostic triage agent.
Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop.
Filter Recurring patient. Autonomous sends. 400 reads = success for that task. Forty replies complete appointment-booking with Saturday packages. Those forty show Appointment booked. The other 360 remain Recurring patient. Health-programs ICP.
Kit email “20% off packages” is a Growth campaign with wallet preview — not adaptive nurture, not HIS billing.
Operators assemble this job on the Project. Click-path remains Setup → Channels (WhatsApp/Gupshup, Web, Meta, Email/SES, Phone/Plivo as needed) → Library templates → Agents → Studio (Patient Inquiry Qualifier, catalogs, appointment skill, emergency guardrail, handoff) → Router → Setup → Customers → Pipeline (five default columns) → Appointments/calendars → Agents → Workflows (stage changed: agent.run, route.agent, crm.set_custom_properties) → Growth with Organization wallet preview. Connect SMS (MSG91) under Setup → Channels when you want that hop. Keep the quotable definition in the brief for the team: Annual checkup reactivation is segmenting Recurring patient (or a list), sending approved templates via campaigns or autonomous agents, and only then running qualification and appointment-booking for people who reply. Autonomous agents may send a list-based recall after you approve the plan and pick an existing library template. Success today is sends, reads, or contacted — not appointment booked. Move the pipeline with a workflow or by hand. While you implement, keep the parent playbooks directory, Recurring patient, WhatsApp overlay, Health programs, Agent Studio, Growth campaigns, and wallet-only pricing in the same runbook. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Human handoff stays in the omnichannel inbox. Appointments and calendars are the slot truth when this job books time. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them under Agents → Workflows. The agent router keeps the wrong bot off this thread. Knowledge bases hold Departments, Doctors, Beds, and Services catalogs — not a clinical chart. Preview the Organization wallet before a blast. Do not claim HIS or EMR replacement. The Annual checkup reactivation playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on library kits are estimates, not an SLA. Autonomous success is sends, reads, or contacted — not appointment booked. If this job mentions money, the Organization wallet is the meter. That is the honest operating manual for this URL.
Recall hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | CRM segment | Overdue pool | List |
| 2 | WhatsApp / email | Template send | Contacted / replied |
| 3 | WhatsApp reply | Qualifier | Fields |
| 4 | Calendars | New slot | Appointment booked |
Inspired by hc-reengage. Booked is not autonomous success. Percentages, if shown, are illustrative estimates inspired by library kits (hc-appointment-reminder, hc-lead-followup, hc-reengage). They are not your Project Insights chart, not an SLA, and not a reason to treat SMS as live.
Reactivation meters.
No. Sends, reads, or contacted.
Reply rate unless you also track Appointment booked on the pipeline.
Coming soon. WhatsApp + email in the kit we keep.
No. Recurring patient plus properties.
No. Engagement list. Chart stays in HIS.
No. Package names only.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Growth blasts with wallet preview.
Open →After they reply.
Open →Who runs overdue lists.
ICP →The recall pool.
Stage →Templates outside 24h.
Channel overlay →How-to companion. This playbook stays the job URL.
Guide →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →Sends and minutes debit the Organization wallet. Creating a CRM row does not.
See pricing →Preview wallet, measure contacted, write calendars when they actually pick a time.
Get started free