Meta · healthcare

Ad lead to the same Project — the job is a booked slot

Meta ad leads enter the same Project as web and walk-ins; the job is a booked slot, not a comment thread that never reaches the inbox. WhatsApp or the widget continues qualification. Phone confirms. Email is prep. Comments that stay on the post are wasted spend.

  • Lead ads + DMs + comments
  • Same contact as walk-ins
  • Slot is the exit, not a like

A comment is not an appointment

Hospitals boost Instagram, collect comments (“price?”), and never create a CRM row. CoPulse connects Instagram Business and Facebook Pages so DMs, comments, and lead ads land in the omnichannel inbox on the same Project as website chat and QR walk-ins. The conversation agent still runs a non-diagnostic qualifier. Moving them to WhatsApp after they share a number is a hop, not a second lead. Meta here is capture — Gupshup remains the WhatsApp catalog.

Where this hop sits in the job

Meta is typically hop one (enquiry). Slot, reminder, consult, and plan use WhatsApp, calendars, voice, and email on the same contact.

  1. Enquiry from ads or social Lead form, DM, or comment becomes New enquiry. Duplicate with a website chat if your merge rules allow.
  2. Qualify toward a slot Same four qualifier fields. Offer calendars or hand off to WhatsApp for the session window and lists/Flows.
  3. Reminder and consult Do not remind on a public comment. Use WhatsApp templates and voice. Consult done is after the visit.
  4. Plan Treatment plan is staff-owned. Do not continue clinical negotiation in Instagram comments.

How it runs in CoPulse

Meta onboarding is the product channel. Healthcare overlay: route into the qualifier agent, then the rest of the omnichannel job. Campaigns on Instagram are ads; CoPulse Growth campaigns are WhatsApp/email/voice you send after the lead exists.

Inbox capture

DMs and comments beside WhatsApp. Human handoff when they ask for a diagnosis or a human.

Conversation agent

Same Studio agent as web. Router can tag source=meta without a second bot.

Handoff to WhatsApp

After they share a number, lists, Flows, and 24-hour session rules apply on Gupshup — not on the ad comment.

Workflows

On New enquiry from Meta, assign the qualifier. On Appointment booked, reminder templates — not another ad boost.

Operator setup

Connect Meta under Setup → Channels on the same Project as WhatsApp and web.

Setup → Channels (Meta) → Agents → Studio (same qualifier) → Router by source if needed → Pipeline → continue WhatsApp (Gupshup) for slot and reminder. Product onboarding: /channels/meta.

Health-check ad that actually books Saturday

An Instagram lead form drops into New enquiry with a package interest. The agent asks preferred_times and location, offers Saturday 9:00, and invites WhatsApp for the reminder window. A public “how much?” comment gets a short inbox reply plus a DM to qualify — not a 40-comment thread. Voice confirms Friday. That is meta ad leads, not a clone of the Meta product page.

Do not train the comment agent on clinical protocols. Catalogs of packages are Services names and prices you already publish, not findings. Wallet-only still applies when you later blast the matched list on WhatsApp.

This overlay is how Meta 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. Instagram and Messenger onboarding, comment reply, and DM inbox behaviour belong on /channels/meta. This page only insists the healthcare exit is Appointment booked on the same Project as walk-ins. 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.

Meta across the care job

Social is capture. Slot truth is never a comment count.

Job This channel Other hops Exit
Enquiry Lead ad / DM / comment → inbox Web, QR New enquiry
Slot Qualify then calendars or WhatsApp WhatsApp lists/Flows Appointment booked
Reminder Not on the public post WhatsApp template, voice Confirmed or recovered
Consult Off-platform Calendar Consult done
Plan Do not negotiate in comments 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

Ads, comments, and the booked-slot exit.

Is a comment reply a booked appointment?

No. Create the contact, qualify, offer a calendar slot. Comments that never reach the inbox are wasted.

Same Project as walk-ins?

Yes. That is the point of this overlay. Duplicate rules belong on New enquiry.

WhatsApp vs Meta Cloud for the reminder?

Reminders use Gupshup WhatsApp templates (or voice/email). Meta here is Instagram/Facebook capture.

SMS to ad leads?

Coming soon. Not live.

Can the comment bot diagnose a rash from a photo?

No. Hand off. Book a dermatology slot from catalog.

Product onboarding?

Instagram and Messenger on CoPulse.

Put ad leads on the clinic Project

Connect Meta, run the same qualifier, and measure booked slots — not comment volume.

Get started free