Guide · Autonomous reactivation

Autonomous reactivation: sends and reads, not booked slots

Approve a plan, send to a list, count sends and reads; do not tell the board the autonomous agent booked the annual slot. Recurring-patient lists are real work. Pretending the task monitor is a calendar is how health-program dashboards lie.

  • Plan approve, then send
  • Success = sends/reads/contacted
  • Canonical job is annual checkup reactivation

Definition

Autonomous reactivation is a list-plus-objective task you clarify and approve. It sends WhatsApp, email, or voice using an existing library template. Success today is sends, reads, or contacted — not appointment booked, and not a shared stop-when-booked contract with inbox agents or Growth drips.

Why program teams equate ‘contacted’ with ‘booked’

A health-program manager sees 410 reads and reports 410 appointments. Calendars disagree. Appointment booked never moved. The qualifier still has to collect times when someone replies.

Annual checkup reactivation is the job. This guide is the honesty layer: three systems, no shared brain, wallet preview, Gupshup templates,

HowTo: run a checkup list without lying

Build a clean CRM query. Pick an existing template. Preview wallet. Approve the plan. Staff inbox for replies. Move Appointment booked only when a slot is real.

  1. Query recurring or overdue rows Customers pipeline / lists. Recurring patient stage is a filter, not a send.
  2. Pick an existing library template Autonomous does not draft the template the plan needs.
  3. Wallet preview Organization wallet. No seat-priced ‘AI licenses.’
  4. Approve and monitor sends/reads Contacted includes voice STT. Still not a slot.
  5. Replies go to the qualifier Conversation agent books from calendars. Workflows may fire after the column moves.

How it runs on the platform

Autonomous is list work. Growth drips are clock-based with reply-rate conversion. Neither is adaptive nurture. 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: 800 overdue executive checks

A program Project approves a Gupshup template to 800 rows. Monitor: sends and reads. Forty families reply; qualifier offers calendar times; ops write Appointment booked. The task is not marked successful because 40 booked — it succeeded because it sent. The board slide must say that.

Product: autonomous. ICP: health programs. Sibling workflows.

What to report upstairs

Pick the metric that matches the runtime.

Runtime Honest metric Not honest Next human step
Autonomous list Sends, reads, contacted Slots booked by the agent Qualifier + calendars
Growth drip Reply rate Show-rate Inbox
Workflow Template sent on stage event It ‘nurtured’ Ops
Calendars Holds Campaign conversion Remind / no-show

Honest limitations

No stop-when-booked. No adaptive nurture. Templates must already exist. Not HIS. Not a HIPAA claim.

Keep this Autonomous reactivation 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: Annual checkup reactivation 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.

Related

Playbook: annual checkup reactivation. Stage: Recurring patient. Opt-out: opt-in and opt-out.

Frequently asked questions

Operators implementing this mechanic on a healthcare Project.

Will autonomous stop when they book?

Not as success criteria today. Sends, reads, or contacted.

Can it draft the checkup template?

No. Pick an existing library template.

Which playbook?

Annual checkup reactivation.

Is this the same as a drip?

No. Drips are clock-based campaigns. Autonomous is plan-approve list work.

SMS list?

Pricing?

Wallet-only usage. Preview before send.

Count sends and reads, then book like a desk

Approve the list task, staff the inbox, write Appointment booked only when calendars agree.

Get started free