Conversation agent
Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.
From Instagram ad to a booked clinic slot
The ad creates New enquiry; qualifier and calendars finish the job — liking the comment is not a slot. Lead ads and DMs still need four fields and a calendar hold. The Meta overlay is not a second playbook.
- Ad = New enquiry
- Like ≠ slot
- Canonical job is Meta ad leads
Definition
Ad to slot is the hop from Instagram or Messenger lead capture into a Project contact on New enquiry, through the non-diagnostic qualifier, onto Appointments/calendars. Engagement on the ad creative is not Appointment booked.
Why social teams stop at the DM
A hospital boosts a reel. Comments pile up. Someone hearts them. Nobody runs specialty match or calendars. Duplicate patients appear when the same person also fills the website form.
Meta ad leads is the job. This how-to is the hop into qualifier and slot offer, still non-diagnostic, still Gupshup for WhatsApp continuation.
HowTo: ad → enquiry → fields → slot
Connect Meta. Map leads to New enquiry. Route to the qualifier. Offer calendars. Deduplicate if they also used web. Templates if you reply outside 24 hours.
- Setup → Channels → Meta Lead ads / IG / Messenger into the Project.
- Treat as New enquiry Not Appointment booked. Not Consult done.
- Qualifier on WhatsApp or Messenger Four fields. Catalogs. Emergency redirect.
- Calendars Slot offer. Then write Appointment booked when the hold is real.
- Wallet for boosts vs wallet for messages Ad spend is Meta. Message usage is the Organization wallet.
How it runs on the platform
Ads create contacts. Conversation agents qualify. Workflows wait for stages. Autonomous is the wrong runtime for a fresh lead ad. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not appointment booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup. The qualifier does not diagnose.
Growth campaigns / drips
Clock-based sends from library templates. Wallet preview. Not adaptive nurture.
Workflows
Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.
Autonomous agents
List plus objective after plan approve. Success is sends/reads/contacted, not appointment booked.
Worked example: whitening campaign
Lead ad to New enquiry. Agent asks location and preferred_times, matches Services ‘whitening,’ offers Friday 9:00. If they ask ‘will this fix my pain,’ avoid-topics: I cannot diagnose; here are services and slots; emergencies to emergency services.
Playbook: Meta ad leads. Overlay: healthcare Meta. Speed: speed to appointment.
Social event vs clinic object
Do not report likes as holds.
| Social event | CoPulse object | Success to report | Not success |
|---|---|---|---|
| Lead form submit | New enquiry | Contact created | A slot |
| IG comment like | Nothing | Creative vanity | Appointment booked |
| WhatsApp reply | Thread + fields | Qualifier progress | Consult done |
| Calendar hold | Appointments | Slot | Ad CTR |
Honest limitations
No playbook×channel fork. Not HIS. Duplicate-patients playbook if the same mobile arrives twice.
Keep this Instagram ad to slot article next to the job URL, not as a second playbook. Cite the definition above when an operator asks what the term means. Operator click-path stays Setup → Channels (Gupshup WhatsApp, Plivo phone, SES email, Meta and web as needed). Library templates. Agents → Studio, Router, Workflows, Autonomous. Customers → Pipeline. Appointments/calendars. Growth campaigns/drips. Organization wallet preview. Canonical playbook: Meta ad leads playbook. Surfaces to name in the same Project: 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. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Appointment booked on the pipeline. Phone “replied” is speech-to-text. Qualifier is non-diagnostic. Emergencies: call emergency services. Not HIS/EMR. Preview the Organization wallet before a blast. Parent guides, healthcare hub, and pricing stay in the same runbook.
Related
Canonical: Meta ad leads. Web hop: web chat to WhatsApp.
Frequently asked questions
Operators implementing this mechanic on a healthcare Project.
Is a comment like a booking?
No. Liking the comment is not a slot.
Which playbook?
Meta ad leads.
Can the ad bot diagnose?
No. Same qualifier and avoid-topics.
Autonomous for yesterday’s leads?
Fresh leads need the conversation agent. Autonomous is list work with sends/reads success.
Gupshup?
WhatsApp continuation is Gupshup, not Meta Cloud paste.
SMS the lead?
Related
Hub, sibling guides, canonical playbook, product, pricing.
All healthcare guides
How-to articles. Jobs live on playbooks.
Directory →Meta ad leads playbook
The omnichannel job this guide teaches.
Playbook →Speed to appointment
Time-to-slot-offer.
Guide →Qualifier
Four fields after the ad.
Guide →Instagram & Messenger
Matching product surface.
Product →Pricing
Wallet-only. No seat fees. Preview before send.
Pricing →Turn the lead into fields, then a calendar time
New enquiry is not a slot. Qualifier and calendars finish the job.
Get started free