Instagram and Messenger leads join the same New enquiry column as the website; the job ends when a slot is offered, not when the comment is liked. Reminders then use Gupshup WhatsApp, not another boost.
Meta ad leads is moving Instagram/Facebook lead ads, DMs, and comments onto the Project, qualifying them, and offering a slot on the same timeline as organic traffic.
Hospitals count likes. This job uses the Meta overlay: DMs, comments, lead forms in the omnichannel inbox. Diagnosis from a photo in comments is forbidden. SMS to ad leads is not live.
Meta is capture. WhatsApp/calendars are slot. Voice confirms.
Meta onboarding is the product channel. This playbook is the healthcare exit. 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. Tag source=meta. Router so ad replies do not hit the dental bot.
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.
Lead form drops in. Qualifier asks times. Saturday 9:00 on calendars. Public “how much?” gets a DM, not a 40-comment thread. Campaign conversion on a later package blast is reply rate unless those replies also become Appointment booked.
Click-path: Setup → Channels → Meta, same Studio qualifier as web.
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: Meta ad leads is moving Instagram/Facebook lead ads, DMs, and comments onto the Project, qualifying them, and offering a slot on the same timeline as organic traffic. 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, Meta 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 Meta ad leads 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.
Social capture hops. There is no nested playbook-by-channel path.
| Hop | Channel | What happens | Exit to next hop |
|---|---|---|---|
| 1 | Meta | Lead / DM / comment | New enquiry |
| 2 | Qualify + lists | Fields | |
| 3 | Calendars | Slot | Appointment booked |
| 4 | Phone | Quiet confirm | STT ≠ attend |
Ads vs booked slots.
No. Qualify and offer a calendar slot.
Yes.
Coming soon. Not live.
No. Hand off.
Reply rate unless you track Appointment booked on the pipeline.
/channels/meta.
Parent directory, sibling jobs, ICP, stage, channel overlay, and product surfaces.
One URL per omnichannel job.
Directory →All sources.
Open →After they leave the ad.
Open →Campus ads into one desk.
ICP →Where ad leads land.
Stage →Same Project as web and walk-ins.
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 →