Playbook · capture

One contact before anyone opens a personal WhatsApp

Every web, ad, phone, and walk-in enquiry lands on one contact in the Project before anyone opens a personal WhatsApp. Then qualification and slot offers run on that timeline. This is not a WhatsApp-only child URL.

  • All sources, one contact
  • Tag source
  • Then qualify

Definition

Enquiry capture is creating one contact and one New enquiry row from every source, then starting the qualifier on that timeline instead of a personal chat or Excel.

Every source invents its own inbox

The website emails a shared mailbox. Instagram sits on a marketer’s phone. Walk-ins shout at the receptionist. By evening two desks offer two Thursday slots. CoPulse is the Project inbox after the ping arrives. CSV import still exists for partner lists. Duplicate-patients is the sibling merge job. Library hc-lead-followup sketches “inquiry → appointment” with SMS and a Patient Triage that “detects symptoms” — this playbook strips both: no live SMS, no diagnosis.

Omnichannel sequence

Capture is hop one. Qualification, booking, and reminders are sibling URLs.

  1. Land the source Web widget, WhatsApp, Meta, email, QR, or CSV. Tag source.
  2. Write New enquiry Workflow on enter can agent.run the qualifier.
  3. Stay on their hop If they wrote WhatsApp, do not bounce them to email for the first four fields.
  4. Hand to qualification patient-qualification writes reason, service_need, location, preferred_times.

How it runs in CoPulse

Conversation agent plus capture channels. A Growth blast is the wrong first move if they just messaged you. 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. Appointment skill stays quiet until qualifier fields exist.

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.

Three pings, one card

Ops imports a doctor-referral CSV. A twenty-first person is already on the widget. Instagram comments become inbox rows, not likes. Workflow starts the qualifier. Click-path is Setup → Channels, Studio, Workflows, Customers kanban. hc-lead-followup funnel estimates (inquired → triaged → slot offered → booked) are not an SLA and not a symptom detector.

Phone as a first hop is rare; missed-call lists still become New enquiry, then WhatsApp. Voice confirmation is appointment-reminder, not this job.

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: Enquiry capture is creating one contact and one New enquiry row from every source, then starting the qualifier on that timeline instead of a personal chat or Excel. 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, Web 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 Enquiry capture 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)

Capture hops. Qualification and slots are other playbooks. There is no nested playbook-by-channel path.

Hop Channel What happens Exit to next hop
1 Web / Meta / QR / CSV Enquiry exists Contact + New enquiry
2 WhatsApp Continue if they share a number Session
3 Inbox Human if insurance / named doctor Thread continues
4 Voice / email Not first-line capture Later jobs

Frequently asked questions

Where the row is created and what the library kit got wrong.

Does CoPulse replace HIS registration?

No. Engagement CRM. Charts stay in your clinical system.

CSV?

Import is v1. Then this job runs on the contact.

Autonomous capture overnight?

No. Inbound is the conversation agent. Autonomous is list sends you approve.

SMS the dump?

Use WhatsApp templates, SMS (MSG91), or web chat.

Patient Triage that detects symptoms?

Do not ship that. Qualifier is non-diagnostic. See patient-qualification.

Duplicates?

Sibling duplicate patients.

Put every ping on one contact

Connect hops, start the qualifier, and keep personal WhatsApp off the critical path.

Get started free