Learn · Healthcare

Healthcare guides: how and when, not extra job URLs

Guides teach how and when; playbooks are the job. Start with the non-diagnostic qualifier, 24-hour window, and calendars versus pipeline. Each article is a how-to with a definition, numbered steps, one table, and a single canonical playbook — no bylines, no second job URL, no diagnosis.

  • Linked from the healthcare hub and the site footer
  • Jobs stay at /industries/healthcare/playbooks/{slug}
  • Honest gaps: 24h templates, autonomous sends/reads, three nurture systems

Definition

CoPulse healthcare guides are operator how-tos under /guides/healthcare: definitions, numbered steps or decision tables, FAQPage JSON-LD on each leaf, and a single link to the omnichannel playbook that is the job. They are not a documentation theme (no docs.css), not a dated article feed, and not a second sitemap of WhatsApp-only jobs.

What you will not find here

SMS as live. Meta Cloud WhatsApp as the catalog path (Gupshup is live). Adaptive nurture. Autonomous success equal to appointment booked. A shared stop-when-booked contract across conversation agents, Growth drips, and autonomous tasks. Seat-priced logins. Diagnosis, HIS/EMR replacement, or a HIPAA product claim. If a capability is partial, the guide says what the operator does today: pick an existing library template, mark Consult done only after attendance, exclude STOP from every runtime, preview the Organization wallet, send emergencies to emergency services.

Surfaces named throughout: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Terminology: Organization and Project. Default columns: New enquiry, Appointment booked, Consult done, Treatment plan, Recurring patient.

How to use this directory

If you are implementing, open the playbook in the In CoPulse box, not only the guide. If you are learning a mechanic (non-diagnostic qualifier, 24-hour window, calendars versus the Appointment booked column), stay on the guide, then jump. Compare URLs remain canonical for vendor-class bake-offs; we did not clone those keywords here. Product URLs stay under /product/*.

  1. Pick the mechanic Qualifier, window, calendars vs stage, no-show, voice, catalogs, workflows, autonomous honesty, consent, show-rate, emergencies.
  2. Read the definition First H2 is citable. Then steps and the table.
  3. Follow In CoPulse Setup → Channels, Library, Agents → Studio / Router / Workflows / Autonomous, pipeline, appointments/calendars, Growth, wallet.
  4. Run one playbook Each guide maps to exactly one canonical job URL. Qualification stays on /playbooks/patient-qualification even if you arrived from emergencies.

Grouped index

Sixteen how-to leaves. The industry hub and the site footer link here so primary nav stays Product, Channels, and Industries.

Map: guide to canonical playbook

One job URL per row. Guides never fork a WhatsApp-only twin. First-segment /guides does not collide with the client SPA.

Guide H1 Canonical playbook
Non-diagnostic qualifier Patient inquiry qualifier: four fields, no diagnosis Patient qualification playbook
24-hour window WhatsApp 24-hour window for clinic follow-ups Pre-consult prep playbook
Speed to appointment Speed to appointment: first message, then a slot offer Enquiry capture playbook
Calendars vs stage Calendars vs the Appointment booked column Appointment booking playbook
No-show how-to How to recover a clinic no-show (without fake consults) No-show recovery playbook
Voice confirmation Voice AI to confirm clinic appointments Appointment reminder playbook
Doctors & services KB Doctors and services knowledge bases (not a chart) Specialty match playbook
Workflow on stage change Workflows when Appointment booked or Consult done fires Treatment-plan follow-up playbook
Autonomous reactivation Autonomous reactivation: sends and reads, not booked slots Annual checkup reactivation playbook
Opt-in and opt-out Clinic opt-in and opt-out (not a HIPAA claim) Opt-out compliance playbook
Measuring show-rate Measure clinic show-rate without mixing reply rate NPS & review playbook
Web chat to WhatsApp Web chat into clinic WhatsApp on one contact Website enquiry playbook
Instagram ad to slot From Instagram ad to a booked clinic slot Meta ad leads playbook
Hospital vs clinic scripts Hospital vs clinic scripts (both non-diagnostic) Referral intake playbook
Emergency & avoid-topics Emergencies and avoid-topics (product, not a slogan) Patient qualification playbook
Template approval Approve WhatsApp templates for clinics (Gupshup) Package campaigns playbook

Worked path for a new Project

Create the Organization wallet mindset first: usage, not seats — see pricing. Setup → Channels: Gupshup WhatsApp, Plivo phone, SES email, Meta if you run ads, web chat if the site matters. Library: submit reminder utility and one marketing template before you need them. Agents → Studio: non-diagnostic qualifier, catalogs, emergency avoid-topics, appointment skill, router. Agents → Workflows: fire on Appointment booked (prep) and Consult done (plan ping). Customers pipeline with the five healthcare columns. Appointments/calendars for slot truth. Growth for packages with wallet preview. Autonomous only for a clean overdue-checkup query, success = sends/reads/contacted — not appointment booked. Inbox staffed for handoff. That is the platform. The guides below explain the sharp edges; the playbooks are the jobs.

Campaign conversion remains reply rate unless you track Appointment booked. Phone replied is STT, not intent to attend. Show-rate is calendars plus Consult done versus no-shows. Library estimates are illustrations, not SLAs. The qualifier does not diagnose. Emergencies: call emergency services. Not HIS/EMR. Not a HIPAA claim on the opt-in page.

All guides

Same site.css chrome as the industry hub: hero, mock, steps, cards, one table, FAQ, CTA. More H2s than a playbook, still not a blog theme.

Frequently asked questions

Directory questions before a leaf.

Are guides the same as playbooks?

No. Playbooks are omnichannel jobs with one URL each. Guides teach mechanics and point at exactly one playbook. Example: the qualifier how-to points at playbooks/patient-qualification.

Where are the guides in the nav?

Footer, and from the healthcare industry hub. This hub is the directory so primary nav does not list sixteen articles.

Is /guides a logged-in app route?

No. First segment /guides is marketing content. It must not conflict with the client SPA; marketing-routes checks first segments.

Do you have playbook×WhatsApp pages?

No. Channel overlays live under /industries/healthcare/channels/. Jobs stay omnichannel.

Will autonomous stop when a visit is booked?

Not as success criteria today. Sends, reads, or contacted. See autonomous reactivation and workflows on Appointment booked.

SMS and Meta Cloud WhatsApp?

Live WhatsApp catalog is Gupshup. SMS is MSG91 when connected. Guides that mention channels repeat that.

Where is pricing?

Wallet-only, no seats. Pricing. Leaves that mention money link there.

Learn the mechanic, then run the playbook on a Project

Connect Gupshup and Plivo, staff the inbox, preview the wallet — guides stay beside jobs, not instead of them. Qualifier stays non-diagnostic.

Get started free