After Consult done, NPS and a review ask sit on the same timeline; they do not move Recurring patient by themselves. Detractors go to inbox. Promoters may get a review link. Not a diagnosis of satisfaction from tone.
NPS and review ask is a post-consult campaign or workflow that collects a score and optionally a public review request, without treating the send as Recurring patient or a new clinical finding.
If you fire NPS from Appointment booked, no-shows review you. Bind to Consult done. SMS review links are not live. Do not let the bot argue clinical quality.
Consult done → wait a few hours → WhatsApp/email → inbox if detractor.
Growth drip or workflow on stage enter. Conversation agent for replies. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. 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 autonomous-NPS a list that includes no-shows.
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.
Workflow six hours after Consult done. Two 3s become tasks. Twenty promoters get a Maps link. Nobody auto-jumps Recurring patient. Show-rate guide is related, not this URL.
Wallet: one template per attended card, not per reminder.
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: NPS and review ask is a post-consult campaign or workflow that collects a score and optionally a public review request, without treating the send as Recurring patient or a new clinical finding. Do not use autonomous tasks as the inbound qualifier. Conversation agents, Growth drips, and autonomous list sends are three systems with no shared stop-when-booked contract. While you implement, keep the parent playbooks directory, Consult done, WhatsApp overlay, Clinics, 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 NPS & review 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.
Feedback hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | Pipeline | Consult done | Eligible |
| 2 | WhatsApp / email | NPS ask | Score |
| 3 | Inbox | Detractor | Task |
| 4 | Optional review link | Promoter |
NPS vs recall column.
No. Ops or a workflow you explicitly build — not this job by default.
No. They are not Consult done.
Coming soon. Not live.
No. Handoff.
Reply rate (score received), not bookings.
Asks debit the Organization wallet.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →They should not get NPS.
Open →Recall is a different job.
Open →Post-OPD asks.
ICP →Attendance gate for NPS.
Stage →Template after the visit.
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 →Bind NPS to Consult done. Keep Recurring patient for recall.
Get started free