Web widget
Snippet, visitor tracking, conversation agent. Product setup: /channels/web.
Widget for capture — WhatsApp for the rest of the job
The site widget captures the enquiry and optional web voice; WhatsApp continues the same contact after they share a number. Web Push is a separate channel. Reminders, consult, and plan do not live as browser notifications on this overlay.
- Chat widget + optional web voice
- Same contact after number share
- Push is a different Setup type
A contact form that never becomes a slot
Hospital sites bury a form in footer, then email a shared inbox nobody owns. CoPulse’s web channel is the chat widget (and optional click-to-talk web voice on that same snippet). Visitor tracking can attach a person before they message. After they share a number, Gupshup WhatsApp is the session for lists, Flows, and slot confirms. Web Push is not this overlay: it is its own Setup channel (VAPID, Library templates, campaign steps). Link it when you need browser notifications — /channels/web-push. Do not treat Push as the reminder hop unless you explicitly connect that channel.
Where this hop sits in the job
Web is hop one for organic site traffic. Slot offer can start on the widget; reminder usually moves to WhatsApp. Voice on the widget is web voice, not the Plivo confirmation dialer.
- Enquiry on the widget Chat (and optional web voice) creates New enquiry. Same qualifier fields as WhatsApp.
- Slot on widget or after number share Appointment skill can offer calendars in chat. Continuing on WhatsApp unlocks lists/Flows and the 24-hour session rules.
- Reminder Prefer WhatsApp templates. Do not assume Web Push unless that channel is connected. Phone confirms quiet numbers.
- Consult and plan Off the website. Pipeline columns after the visit. Widget is not an HIS portal.
How it runs in CoPulse
Web chat and web voice share the widget and Voice AI profiles with phone, but desk outbound confirms still use Phone. Push opt-in on the widget only appears when the Web Push channel is connected — sends still go through that channel.
Web voice
Optional click-to-talk on the same widget. Not a separate Setup channel. Not the confirmation power dialer.
Continue on WhatsApp
After they share a number, the contact is the same. Qualifier history is not a second lead.
Web Push (not this overlay)
Separate Setup type. If you need it: Web Push. Taxonomy for this page does not include Push as the job.
Operator setup
Enable the widget on the hospital or clinic site for this Project. Connect WhatsApp so the number-share hop works.
Setup → Channels (Web) → paste snippet → Agents → Studio (same qualifier) → optionally enable web voice on the widget → Channels (WhatsApp / Gupshup) for continuation. Web Push only if you open that channel separately.
Pricing-page visitor to Thursday slot
A parent on the pediatrics landing page opens chat, states evening preferred_times, and hears two slots. They tap click-to-talk once to ask a parking question (web voice), then share WhatsApp for the reminder. T-24h is a Gupshup template, not a browser push, because Push was never the job. That is web chat to WhatsApp as the how-to, and this overlay as the channel story.
Do not put the full Doctors catalog behind a form that emails PDF. Knowledge on the widget agent is enough to match a pediatrician, then calendars. If you later connect Web Push, treat it as campaign/drip notifications — still not this URL.
This overlay is how web sits on a healthcare Project, not a second product manual. The Patient Inquiry Qualifier still collects reason, service_need, location, and preferred_times. Knowledge bases hold Departments, Doctors, Beds, and Services — not a clinical chart. Appointments and calendars are slot truth. Inbox plus human handoff carries clinical questions. Pricing is wallet-only. Autonomous success is sends, reads, or contacted — not appointment booked. If a visitor describes an emergency, tell them to call emergency services immediately. Web voice lives on the widget. Softphone and AMD live on Phone. Web Push is a different channel page. Keep those three sentences in the operator runbook so nobody files Push bugs against this overlay. Keep one Organization and a Project per facility or program. Preview the Organization wallet before a blast. Library templates are required outside the 24-hour WhatsApp window. Workflows fire on pipeline stage change only when you attach them. Do not invent extra board columns. Do not claim HIS or EMR replacement. Playbooks remain omnichannel URLs; this channel is one hop.
Web across the care job
Capture and optional on-site voice. Reminders usually leave the browser.
| Job | This channel | Other hops | Exit |
|---|---|---|---|
| Enquiry | Widget chat / web voice | Meta, QR | New enquiry |
| Slot | Calendar offer in chat | WhatsApp after number | Appointment booked |
| Reminder | Not Push on this overlay | WhatsApp template, phone | Confirmed or recovered |
| Consult | Off-site | Calendar | Consult done |
| Plan | Not a patient portal | Inbox / WhatsApp | Treatment plan |
Playbooks that use this hop
Each playbook is the full omnichannel job. This channel is one step, not a second URL tree.
Frequently asked questions
Widget, web voice, and why Push is not this page.
Is web voice a separate Setup channel?
No. Click-to-talk on the site widget. Desk dials use Phone (Inbox → Live voice).
Should Web Push be configured here?
No. Own Setup type: Web Push. This overlay is chat + optional web voice, then WhatsApp.
Can the widget send WhatsApp by itself?
It continues the same contact after they share a number, using the WhatsApp channel — not a hidden widget send.
SMS from the site form?
Coming soon. Not live.
Does the widget replace HIS login?
No. Engagement capture only.
Product page?
Related
Hub, sibling hops, product channel page, and the surface operators actually open.
Healthcare hub
Qualifier, catalogs, calendars, ICPs, and jobs.
Back to hub →Where the session continues after number share.
Open →Phone
Plivo confirms — not web voice.
Open →AI agents
Same Studio qualifier on the widget as on WhatsApp.
Explore →Web on CoPulse
Widget, visitor tracking, optional web voice.
Product channel →Wallet-only pricing
Agent turns meter from the Organization wallet; voice minutes follow phone pricing.
See pricing →Put the qualifier on the clinic site
Embed the widget, offer a slot, and continue on WhatsApp — leave Push on its own channel.
Get started free