Ad DMs join the same visit job as portal WhatsApp

Definition

Meta ad leads is the job of taking Instagram, Messenger, and post-comment interest from ads or organic, writing a Booking, qualifying with the same RE Qualifier, and offering a site visit — continuing on WhatsApp or voice when the DM window is the wrong place for slots.

Social inboxes are not buyer pipelines

Performance teams live in Ads Manager. Sales never sees the DM. CoPulse Meta channel puts the thread in the omnichannel inbox on the Project. Lead ads that only dump CSV still need capture/import. Do not invent Instant Forms APIs we did not connect. WhatsApp hop uses Gupshup, not Meta Cloud WhatsApp.

Omnichannel sequence

Meta is capture. WhatsApp often continues qualification. Voice confirms the visit. Email unused unless launch digest.

How it runs in CoPulse

Conversation agent on Meta. Workflows tag source. Optional WhatsApp for templates and slots. Autonomous not for inbound DMs. 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, not an invented Meta Cloud hop. Phone is Plivo; email is SES. Wallet-only pricing: preview the Organization wallet before a blast. Organization and Project — never a shared inbox that vanishes when a broker leaves.

Operator setup

Meta connected. Qualifier knowledge matches the ad creative (same project).

Lead ad at 11 p.m., visit Sunday

Messenger lead: qualifier asks BHK. They prefer WhatsApp; inbox stays one contact. Sunday 10 booked. Visit Caller Friday. Performance still looks at Ads Manager; sales looks at Bookings. Click-path: Meta inbox, Booking, appointment, phone.

Comments under the reel use the same agent if you enabled them as on the home FAQ. Illustrative blitz funnel after they qualify. Pricing: Meta messaging and WhatsApp/voice on the wallet. No seat fee for the ads manager.

Operators assemble this job on the Project. Click-path remains Setup → Channels Meta + WhatsApp → Studio → Router by channel → pipeline → Library for WhatsApp continuation → wallet. Keep the quotable definition in the brief for the team: Meta ad leads is the job of taking Instagram, Messenger, and post-comment interest from ads or organic, writing a Booking, qualifying with the same RE Qualifier, and offering a site visit — continuing on WhatsApp or voice when the DM window is the wrong place for slots. 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, Developers, 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 visit 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 PDFs you uploaded. Preview the Organization wallet before a blast. Property managers should not paste sales token stages onto leasing jobs. The Meta ad leads playbook never forks into a WhatsApp-only or voice-only child URL. Funnel percentages on some leaves are library template estimates from Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back — not an SLA and not Insights. If this job mentions money, the Organization wallet is the meter. If it mentions a Saturday slot, Visit Caller and T-24h templates are in-product; cab dispatch is not. That is the honest operating manual for this URL.

Channel sequence (one job, not extra URLs)

Meta job hops. There is no nested playbook-by-channel path.

Illustrative funnel (library template estimates)

After the hop to the blitz path, use those estimates. These percentages come from CoPulse library playbook templates (Site-visit booking blitz, New project launch teaser, or Cold-buyer win-back). They are not your project's Insights chart.