Inbox agent
Studio persona on Meta surfaces. Knowledge for public-safe FAQs. Escalate price arguments.
Ads in Messenger, qualification on the same Buyer
Meta ads should land in the same omnichannel inbox as WhatsApp so qualification and site-visit booking are not stuck in Messenger. Instagram and Facebook DMs — and public post comments when those channels are connected — belong on the Booking, then the job continues on WhatsApp, voice, and email. /channels/instagram and /channels/messenger redirect here on the product site; this overlay is the real-estate job.
- DMs + post comments
- Same inbox as WhatsApp
- Then book the visit
Messenger-only follow-up dies at the slot
Instagram lead ads create conversations that never reach the shared inbox. Brokers then paste screenshots into personal WhatsApp. CoPulse treats Instagram and Messenger as inbox channels. When connected, AI can reply to public post comments as well as DMs — that is on the home FAQ, not a separate product. Capture is this hop. Qualification and visit booking still usually move to WhatsApp because templates, brochures, and the 24-hour session are stronger there. Do not clone a Meta-only playbook URL. Do not invent Meta Cloud WhatsApp; WhatsApp remains Gupshup.
Where this hop sits in the job
Meta is hop one (or two after web). WhatsApp qualify. Voice confirm. Email optional.
- Ad or organic Lead form, DM, or comment. Agent replies in Meta.
- Identity Create or merge the Buyer. Do not open a second anonymous lead on WhatsApp without linking.
- Continue on WhatsApp Floor plans and slots. Template rules apply after 24h on that number.
- Voice Visit confirmation as usual.
How it runs in CoPulse
Conversation agent deployed on Instagram/Messenger (and comments). Router by channel. Handoff if the comment is hostile. Campaigns on Meta are not a substitute for WhatsApp library templates. Autonomous outbound channels today are WhatsApp, email, phone — not IG blasts from autonomous tasks.
Comments
When IG/FB is connected, AI can reply to public post comments, then pull to DM.
Router
Comments vs CP dumps vs buyer WhatsApp are different.
Handoff
RM sees the comment thread in inbox, not a Community Manager spreadsheet.
Operator setup
Connect Instagram and Messenger under Setup → Channels. Product details live on /channels/meta.
Setup → Channels (Meta) → Studio (deploy agent on IG/Messenger) → Router → link WhatsApp on the same Project → Pipeline. Wallet for Meta messaging per pricing. No SMS.
Reel comment to Saturday slot
A reel comment asks price. The agent replies publicly with a safe line, then DMs. It captures locality and budget, creates the enquiry, and offers to continue on WhatsApp for the floor plan (knowledge files are awkward in comments). On WhatsApp the qualifier books Saturday. Voice confirms. That is meta-ad-leads plus site-visit-booking, two playbooks, one Buyer.
Lead ads that stay in Messenger forever never get template reminders. Move or mirror the number. Luxury ICP may stay in DM with guardrails and skip the blast. Affordable housing should not argue eligibility in public comments — hand off. Autonomous agents will not harvest comments into a visit-booked success metric.
Meta as capture hop
If the visit is booked in Messenger alone, you skipped the stronger WhatsApp toolset.
| Job | This channel | Other hops | Exit |
|---|---|---|---|
| Capture | Ad, DM, comment | Web optional | Enquiry |
| Qualify | Light questions in DM | WhatsApp deep qualify | Qualified |
| Book visit | Rarely the slot UI | WhatsApp + voice | Visit booked |
| Launch | Creative + comments | WhatsApp/email teaser | Replies |
Playbooks that use this hop
Each playbook is the full omnichannel job. This channel is one step, not a second URL tree.
Guide: Instagram ad to site visit
How this hop sits in the omnichannel job.
Guide →Meta ad leads
IG/Messenger in; rest of the job omnichannel.
Open playbook →Lead capture
Ads, web, walk-in onto one timeline.
Open playbook →Lead qualification
Usually finishes on WhatsApp.
Open playbook →Site visit booking
Slots after the DM handshake.
Open playbook →Frequently asked questions
Comments, DMs, and handoff to WhatsApp.
Do comments really get AI replies?
Yes when Instagram or Facebook is connected — same as the CoPulse home FAQ. Then pull to DM and CRM.
Why not stay on Messenger?
You can. Most RE teams still need WhatsApp templates, wallet campaigns, and voice confirmation.
Instagram URL?
/channels/instagram redirects to /channels/meta. This overlay is /industries/realestate/channels/meta.
Autonomous on Instagram?
Autonomous outbound is WhatsApp, email, phone today.
WhatsApp via Meta Cloud?
Not the live catalog path. WhatsApp overlay uses Gupshup.
Pricing?
Usage. Pricing.
Related
Hub, sibling hops, product channel page, and the surface operators actually open.
Real estate hub
Buyers & Tenants, Bookings, ICPs, and jobs.
Back to hub →Where most qualification finishes.
Open →Web
The other capture surface.
Open →Inbox
DMs and comments next to WhatsApp.
Explore →Instagram & Messenger
Product channel page for Meta messaging.
Product channel →Wallet-only pricing
Meta messaging usage on the Organization wallet.
See pricing →Stop leaving leads in the IG inbox
Connect Meta, deploy the agent, and continue the Booking on WhatsApp and voice.
Get started free