After Consult done, workflows can nudge the plan you already issued; agents still refuse diagnosis and new clinical advice. Logistics drips, coordinator tasks, return-visit booking. Not a Construction-style extra stage.
Treatment plan follow-up is stage-enter automation on Treatment plan: templates, properties, coordinator tasks, and a logistics agent — never new clinical advice in the thread.
If copy could be a prescription, delete it. Waiting-on-lab is a property, not a stage. SMS daily dosing is not live and would still not make CoPulse a HIS.
Consult done → human shares plan → this column → drips → optional new Appointment booked.
Workflows as on /product/workflows. Conversation agent with a hard clinical refuse. 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. Coordinator queue in the router.
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.
Plan printed Friday. Week-2 template Monday. Tray-change ask → handoff. Return Friday on calendars. Dental-specialty ICP.
Click-path: Pipeline column, Workflows, Library, Inbox queues.
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: Treatment plan follow-up is stage-enter automation on Treatment plan: templates, properties, coordinator tasks, and a logistics agent — never new clinical advice in the thread. 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, Treatment plan, WhatsApp overlay, Dental & specialty, 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 Treatment plan follow-up 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.
Follow-up hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | Pipeline | Enter Treatment plan | Workflow |
| 2 | WhatsApp / email | Approved nudge | Delivered |
| 3 | Inbox | Clinical change | Human |
| 4 | Calendars | Return visit | Appointment booked |
Non-diagnostic follow-up.
No. Handoff.
No. Custom property or task.
Do not SMS clinical dosing. That is not a HIS.
send.*, crm.set_custom_properties, crm.create_task, agent.run logistics.
Call emergency services immediately.
Nudges debit the Organization wallet.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Return visit.
Open →If labs are involved.
Open →Plans after consult.
ICP →Where this drip binds.
Stage →Closed-window templates.
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 →Stage-enter workflows on the plan you already shared.
Get started free