Playbook · web

Widget first, WhatsApp next, Push not this job

The widget starts the thread; WhatsApp continues the same contact after they share a number — web voice is optional, Web Push is a different channel. Qualification and slot offers can begin on-site; reminders usually leave the browser.

  • Same contact after number share
  • Optional web voice
  • Push is another Setup type

Definition

Website enquiry is capturing the OPD job on the site widget (chat and optional click-to-talk), then continuing the same contact on WhatsApp after a number share.

Footer forms that email nobody

Hospital sites bury a form; the mailbox is a graveyard. This job uses the Web channel overlay: widget, visitor tracking, optional web voice. Web Push is /channels/web-push — not a reminder hop here. Do not treat the widget as HIS login.

Omnichannel sequence

Web is capture. WhatsApp is qualify/slot/reminder. Phone confirms quiet numbers.

  1. Widget Chat or web voice creates New enquiry.
  2. Qualify Same four fields as WhatsApp.
  3. Number share Continue on Gupshup WhatsApp for lists/Flows and 24h session.
  4. Remind elsewhere Templates and voice — not Push unless you connected that channel on purpose.

How it runs in CoPulse

Web widget agent is the same Studio qualifier. Desk outbound confirms stay on Phone. 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. Web voice is not the confirmation power dialer.

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.

Pediatrics landing page to Thursday 6:30

Parent opens chat, states evenings, hears two slots, shares WhatsApp. T-24h is a Gupshup template. Push was never connected. Sibling enquiry-capture is the generic source job; this URL is the website-shaped one.

Click-path: Setup → Channels → Web snippet, then WhatsApp coexistence or new number.

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: Website enquiry is capturing the OPD job on the site widget (chat and optional click-to-talk), then continuing the same contact on WhatsApp after a number share. 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, 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 Website enquiry 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)

Website-shaped capture. One job URL. There is no nested playbook-by-channel path.

Hop Channel What happens Exit to next hop
1 Web widget Chat / web voice New enquiry
2 WhatsApp Continue after number Session
3 Calendars Slot if they accept Appointment booked
4 Web Push Not this playbook Other channel page

Frequently asked questions

Widget vs Push vs phone.

Is web voice a Setup channel?

No. Click-to-talk on the widget.

Web Push?

Separate channel. Not this job unless you explicitly connect it.

SMS from the form?

Connect MSG91, or continue on WhatsApp or web chat.

Same qualifier?

Yes. Four fields, non-diagnostic.

HIS portal?

No. Engagement capture only.

Product web page?

/channels/web.

Put the qualifier on the site

Embed the widget and continue on WhatsApp — leave Push on its own channel.

Get started free