Playbook · referral

Referred patient, tagged source, private thread

A referred number becomes its own contact with source tagged; the referring doctor does not sit inside the patient’s private thread. Qualify and book as usual. Do not CC clinical notes into WhatsApp.

  • Own contact
  • Source tag
  • Privacy vs the referrer

Definition

Referral intake is creating a patient contact from a referring clinician or partner list, tagging source, and running qualification without putting the referrer in the patient’s inbox thread.

Forwarded WhatsApp from the referring clinic

A PDF of names plus a group chat with the referrer leaks privacy and duplicates. Import or type the number, crm.set_custom_properties referring_doctor=Mehta, qualifier on the patient hop. HIS referral module stays HIS.

Omnichannel sequence

Capture via CSV/email/WhatsApp from the partner, then the same qualify → slot path.

  1. Create the patient Do not reuse the referrer’s contact.
  2. Tag source Workflow stamps properties.
  3. Qualify privately Four fields with the patient.
  4. Optional thank-you Separate template to the referrer if you have consent — not in the patient thread.

How it runs in CoPulse

Import plus qualifier. Do not autonomous-message a referrer list as if they were patients. 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.

Conversation agent

Patient Inquiry Qualifier (reason, service_need, location, preferred_times). Catalogs: Departments, Doctors, Beds, Services — not a chart. Emergency utterances: call emergency services. Inbox handoff. Router by referring_department if campuses split.

Workflows

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.

Growth campaigns / drips

Clock-based sequences and list blasts with wallet preview. Campaign conversion is reply rate unless you also track Appointment booked on the pipeline.

Agent router

Keep a dental bot off a health-check reply. Route by stage, channel, or campaign.

Operator setup

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.

Ortho list without a group chat

Twenty numbers imported. Each gets New enquiry. Qualifier runs on WhatsApp templates if no session exists. Referrer gets a weekly count email if you built that campaign — not the patient’s fasting notes.

Duplicate-patients still merges if they already walked in.

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: Referral intake is creating a patient contact from a referring clinician or partner list, tagging source, and running qualification without putting the referrer in the patient’s inbox 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, New enquiry, WhatsApp overlay, Hospitals, 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 Referral intake 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.

Channel sequence (one job, not extra URLs)

Referral hops. There is no nested playbook-by-channel path.

Hop Channel What happens Exit to next hop
1 CSV / email Create patient contact New enquiry
2 WhatsApp Qualify privately Fields
3 Calendars Slot Appointment booked
4 Email to referrer Optional aggregate thank-you Not the patient thread

Frequently asked questions

Referrer vs patient timeline.

Can the referrer see the patient WhatsApp?

Not via this job. Separate contacts.

HIS referral?

Stays in HIS. CoPulse is engagement.

SMS the list?

Connect MSG91 under Setup → Channels, or use WhatsApp templates.

Diagnosis in the referral note?

Do not paste into knowledge for the bot to elaborate.

Duplicates?

Merge before two slots.

Hospital vs clinic scripts?

Guide hospital-vs-clinic-scripts when it ships.

Tag the source, protect the thread

One contact per referred patient, then the same qualifier.

Get started free