Package blasts preview the Organization wallet and use approved templates; they are not adaptive nurture and not an HIS billing module. Conversion is reply rate unless Appointment booked is tracked. PRODUCT/CATALOG WhatsApp types can show packages; knowledge catalogs are separate.
Package campaigns are Growth sends of health-check or procedure packages to a CRM segment using approved Gupshup/email templates, with wallet preview, then the usual qualify/book jobs on reply.
CoPulse does not adapt copy from prior outcomes. It does not replace billing. hc-reengage’s offer email is a campaign, not a price engine. Strip SMS.
Segment → blast → reply → qualification → calendars.
Growth campaigns are the runtime. Autonomous is the other recall tool. 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.
Patient Inquiry Qualifier (reason, service_need, location, preferred_times). Catalogs: Departments, Doctors, Beds, Services — not a chart. Emergency utterances: call emergency services. Inbox handoff. CATALOG templates ≠ Doctors knowledge files.
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.
Clock-based sequences and list blasts with wallet preview. Campaign conversion is reply rate unless you also track Appointment booked on the pipeline.
Keep a dental bot off a health-check reply. Route by stage, channel, or campaign.
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.
1,200 names, wallet preview, CATALOG of three packages. 90 replies. Campaign conversion = 90/1200. Twelve complete appointment-booking. Report 12 booked on the pipeline, not 90.
Click-path: Growth → audience → template → preview → send. Library template-approval guide when it ships.
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: Package campaigns are Growth sends of health-check or procedure packages to a CRM segment using approved Gupshup/email templates, with wallet preview, then the usual qualify/book jobs on reply. 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, Recurring patient, WhatsApp overlay, Health programs, 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 Package campaigns 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.
Campaign hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | CRM | Segment | Audience |
| 2 | WhatsApp / email | Approved send | Reached / replied |
| 3 | Qualifier on reply | Fields | |
| 4 | Calendars | Slot | Appointment booked if tracked |
Growth vs HIS vs adaptive.
Not shipped. You pick the template.
No. Packages are catalog names and campaign copy.
Reply rate unless Appointment booked is tracked on the pipeline.
Coming soon. Not live.
Campaigns are scheduled drips you design. Autonomous is list/objective outbound. Both need the qualifier on reply.
Preview before send. Organization wallet.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →Autonomous-friendly sibling.
Open →After replies.
Open →Package owners.
ICP →Typical audience.
Stage →PRODUCT/CATALOG vs knowledge.
Channel overlay →How-to companion. This playbook stays the job URL.
Guide →Agent Studio, skills, knowledge, router, workflows.
Explore agents →Library templates, audiences, wallet preview.
Explore campaigns →Sends and minutes debit the Organization wallet. Creating a CRM row does not.
See pricing →Approved templates only. Count replies and bookings as different meters.
Get started free