Guide · Instagram to visit

From Instagram ad to site visit

Meta lead to qualify to book to remind is one contact timeline, including comment replies when Instagram is connected. The ad is not a CRM. If comments sit in Meta inbox, leads sit in a CSV, and WhatsApp sits on a broker phone, you will book the loud commenter and lose the form fill. CoPulse is the Project timeline across Meta, WhatsApp, and phone.

One contact
Comments are inbound too
WhatsApp continues the ad, not a new silo

Start free Meta ad leads playbook

Definition

Instagram-ad-to-site-visit is the omnichannel job of capturing a Meta lead or comment, continuing on WhatsApp (and voice if silent), qualifying against a project knowledge base, booking an appointment, and reminding — on one contact — without a second anonymous lead when they hop channels.

Why the ad account is not the journey

Media teams optimize CPM. Sales never sees the comment thread. Lead forms dump to email. Speed-to-lead dies. Duplicate contacts appear when the same person fills the form and WhatsApps the number in the ad.

Instagram and Messenger are live CoPulse channels when connected. They are not a substitute for qualification fields or calendars.

HowTo: ad to gate

Run meta-ad-leads as the job. Booking still uses site-visit-booking. This guide stitches the hops.

Connect Meta Setup → Channels. Instagram/Messenger as catalogued. Comments can land in omnichannel inbox.
Land the lead on the Project Form or comment → contact. Merge if the WhatsApp number matches.
Qualify on WhatsApp Five questions. Knowledge for the advertised tower only.
Book capacity-honest slots Calendars. Pickup. Not every commenter gets Saturday 11:00.
Remind T-24h utility template + optional Visit Caller. Reads ≠ visited.

How it runs on the platform

Conversation agent on Meta and WhatsApp. Do not start with autonomous. 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 site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

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 visit booked.

Worked example: reel comment Tuesday 21:12

Buyer comments ‘rate?’ on an Oakshire reel. Inbox shows Instagram. Agent (routed to Oakshire qualifier) asks BHK/budget, offers to continue on WhatsApp, sends the Project number or click-to-chat. Same contact. Wednesday qualifier books Sunday 11:00 because Saturday is at cap. Friday utility reminder. Saturday Visit Caller if no reply. Stage Site visit booked until gate confirms.

If they only submitted a lead form and never commented, speed-to-lead still applies: WhatsApp within minutes, not a weekly Meta insights meeting.

Hop sequence

Channel sequence from ad to visit.

Hop	Channel	What happens	Exit
0	Instagram / ads	Comment or form	Contact on Project
1	Messenger or IG	Short qualify / hand to WA	Do not leave them in Meta only
2	WhatsApp	Full qualify + slot	Qualified / booked
3	Phone	If silent	STT ≠ interested
4	WhatsApp utility	T-24h reminder	Still not Visited

Honest limitations

Marketplace vs CRM suppression is a known gap if you also buy marketplace leads (G17). Interested is not first-class (G6). We do not invent Meta Cloud WhatsApp; ads are Meta, WhatsApp business is Gupshup. SMS not live. Adaptive retargeting not shipped.

Keep this Instagram to visit article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Setup → Channels → Meta + WhatsApp Gupshup + Phone. Agents → Studio + router. Inbox. Pipeline. Appointments. Growth only if you retarget with templates, not as the first hop. 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 Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Meta overlay. Web chat to WhatsApp is the similar hop from site, not ads. Booking: site-visit-booking playbook.

Frequently asked questions

Performance marketers handing CSVs to sales on Mondays.

Do comment replies count as the 24-hour WhatsApp window?

No. Instagram is not WhatsApp. When you move to WhatsApp, the WhatsApp window starts from WhatsApp inbound (or a template they answer).

Can the same agent speak on IG and WhatsApp?

Yes if you attach it and route correctly. Knowledge must match the advertised project.

Lead form duplicates the commenter?

Merge using duplicate-leads. Speed without merge double-texts them.

Should we blast all form fills with a launch template?

That is a campaign job, usually after or besides qualification. First hop should still qualify. Wallet preview.

Does CoPulse optimize the ad creative?

No. This is the CRM journey after the click or comment.

Pricing?

Channel and AI usage from Organization wallet. Ad spend stays in Meta. See pricing for CoPulse meters.

Hub, sibling guides, canonical playbook, product, pricing.

Put the comment and the form on one contact

Connect Meta and Gupshup, qualify, book a real slot — meta-ad-leads playbook.

Get started free