Workflows
On enter: stamp properties, queue week-2 template, create a coordinator task.
The plan you shared — not a plan the bot invented
Treatment plan is the post-consult column for the plan you already shared — agents do not invent clinical advice in the thread. Logistics (when to return, fasting for a follow-up draw, package inclusions) may drip from workflows. The clinical content stays with the clinician and, if you use one, the HIS.
- Human-authored plan
- Drips for logistics
- Not a chat diagnosis
A chatbot that “writes the plan” is the failure mode
Specialty OPDs want the agent to escalate trays or guess antibiotics. That is diagnosis. This column exists so ops can filter who needs follow-up after a real consult. On enter, a workflow may send a Library template you wrote (“bring last x-rays”), crm.set_custom_properties plan_status=shared, agent.run a logistics agent, or route.agent to a coordinator queue. It must not author clinical steps. No extra Construction-style stages for “waiting on lab” — use custom properties or tasks. Report-ready remains a playbook.
How the card gets here and what happens next
Consult done first. Then a human shares a plan. Drips and inbox run. Recurring patient is for cycles and packages, not a substitute for this column if a plan is active.
- Consult happened Consult done is already true.
- Plan shared In person, HIS, or a document you sent. Then move this column.
- Workflow drips Return visit, payment logistics, coordinator tasks — not new clinical advice.
- Exit Accept and continue, pause, or later Recurring patient for recall.
How it runs in CoPulse
Mirror product workflows: stage-changed trigger, send.whatsapp/email, crm.set_custom_properties, crm.create_task, agent.run for FAQ logistics, route.agent to a coordinator. Knowledge may hold published package names, not indications the model should apply.
Conversation agent
Handoff when they ask to change the plan. Emergency line reminder still applies.
Campaigns
Only if you designed a follow-up sequence. Wallet preview. Not autonomous “booked” trophies.
HIS boundary
Orders and prescriptions stay there. CoPulse carries the conversation.
Operator setup
Bind a coordinator queue in the router before you turn the drip on.
Setup → Customers → Pipeline (keep the five default labels unless you truly rename) → Appointments/calendars → Setup → Channels → Library templates → Agents → Studio / Router → Agents → Workflows (trigger: stage changed; actions: agent.run, route.agent, crm.set_custom_properties, crm.update_stage, crm.create_task, send.whatsapp / send.email) → Growth campaigns with wallet preview.
Aligner week-2 without a chat diagnosis
Friday consult, plan printed. Card → Treatment plan. Workflow sends “wear time and next visit window” from a template the clinic approved. Patient asks to skip trays; agent.run logistics bot refuses and hands off. Coordinator uses crm.create_task. No new pipeline stage named “waiting on scan.” Custom property scan_status=pending is enough. That is treatment plan follow-up.
Dental and specialty ICPs should keep Doctors calendars for the return visit. When they rebook, you may also have an Appointment booked card or the same contact with a new meeting — do not invent a parallel board.
This page is the Treatment plan story on the default healthcare board — not a playbook clone and not a loan-style extra stage. The Patient Inquiry Qualifier still collects reason, service_need, location, and preferred_times. Knowledge bases hold Departments, Doctors, Beds, and Services. Appointments and calendars are slot truth; the Appointment booked column is a CRM stage that should match a calendar fact, not a campaign send. Inbox plus human handoff carries clinical questions. Pricing is wallet-only. Autonomous success is sends, reads, or contacted — not appointment booked. Emergencies: tell them to call emergency services immediately. The unique_angle is the guardrail: agents do not invent clinical advice. If copy on a drip sounds like a protocol, delete it. Workflows live under Agents → Workflows with a stage-changed trigger. Typical actions: send.whatsapp or send.email with a Library template, agent.run (hand the contact to a Studio agent), route.agent (agent router by stage/channel/rules), crm.set_custom_properties, crm.update_stage, crm.create_task. Skills and knowledge stay on the agent, not on the workflow node. Preview the Organization wallet before a template blast. Do not add No-show or Report ready as board columns — those are playbooks. Do not invent HIS/EMR replacement.
Treatment plan vs adjacent objects
Plan column, return slot, and documents.
| Stage | Automation | Human | Channel hops | Exit criteria |
|---|---|---|---|---|
| Treatment plan | Logistics drip | Plan content | WhatsApp + email + inbox | Continue, pause, or recall |
| Return Appointment booked | Reminder again | New calendar event | Calendars | Next consult |
| Report-ready playbook | Ping | LIS | Email + WhatsApp | Not a plan |
| Recurring patient | Recall lists | Segment | Campaigns | New enquiry/slot cycle |
| Bot-authored protocol | Forbidden | Delete that prompt | — | Handoff |
Jobs for this column
Follow-up is the playbook. Stage change is the trigger.
Frequently asked questions
Non-diagnostic follow-up and workflow stamps.
Can the agent adjust the plan in WhatsApp?
No. Logistics only. Clinical change is human handoff.
Waiting-on-lab as a stage?
No. crm.set_custom_properties or a task. Keep five columns.
What should the enter workflow do?
Template you wrote, properties, coordinator task, optional logistics agent.run. Not a new protocol.
SMS for daily medicine nudges?
Coming soon. Not live. Do not imply CoPulse is a dosing HIS.
Emergency during follow-up?
Call emergency services immediately.
Wallet?
Follow-up templates debit the Organization wallet.
Related
Parent hub, sibling stages, CRM product, and jobs that move this column.
Healthcare hub
Qualifier, catalogs, calendars, ICPs, and jobs.
Back to hub →Consult done
Attendance before any plan column.
Open →Recurring patient
Recall cycles and packages.
Open →Pipeline & CRM
Custom properties and tasks live on the CRM; the plan text does not have to.
Product CRM →Wallet-only pricing
Follow-up sends debit the Organization wallet.
See pricing →Drip logistics, not clinical advice
Move this column after a human shared the plan, then workflow the reminders you actually approved.
Get started free