Guide · Listing campaigns how-to

How to run listing campaigns on WhatsApp

How-to companion to the property-campaigns playbook: templates, wallet preview, matched audience, reply triage. This is not a second omnichannel job and not a playbook×WhatsApp nested URL. If you are launching a tower, the launch-day runbook plus property-launch playbook own that moment. This page is inventory pings: new stack, price revision, leftover 3BHKs.

Canonical job: property-campaigns playbook
Wallet before send
Replies need a qualifier

Start free Property campaigns playbook

Definition

A listing campaign is a Growth send (sometimes autonomous) of an approved marketing template to a matched, opted-in audience about specific inventory, with a conversation agent ready when replies open the 24-hour window, Organization wallet previewed, and conversion measured as reply rate unless you track visits on the pipeline.

Why broadcast lists feel like campaigns and fail like spam

Personal WhatsApp broadcast. No template. No opt-out. No wallet preview because it is a phone. No pipeline. Replies at 1 a.m. unanswered. Next day window closed.

Property-campaigns is the job URL. Launch is a different playbook. Do not fork listing×WhatsApp.

HowTo: listing ping

Same bones as launch, smaller audience, inventory-specific template, still honest metrics.

Approved marketing template This inventory. Conservative claims. RERA guide.
Matched audience BHK/budget fields help. Exclude STOP, booked-angry, wrong BHK.
Wallet preview Organization wallet. Pricing.
Growth send Autonomous optional; still sends/reads if you do.
Triage replies Qualifier + capacity-honest slots. Conversion tile is replies.

How it runs on the platform

Growth primary. Conversation agent on replies. Autonomous if you insist on a task — success still not visits. 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: leftover 3BHKs Tuesday 11:00

Template names the stacks that exist. Audience 320 opted-in 3BHK-fit. Preview wallet. Send. 14% reply (campaign conversion). Qualifier books Sunday not over-cap Saturday. Two STOP — exclude everywhere. No SMS. No adaptive second creative (G2). If they do not reply, closed-window again needs a template, not a casual ping (24h guide).

Do not attach marketplace unreavealed leads (G5). Do not use construction-booked buyers as a listing audience (cadence guide).

Listing vs launch vs win-back

Pick the job URL correctly.

Motion	Playbook	This guide?	Typical template
Inventory ping	Property campaigns	Yes, how-to	Marketing listing
First teaser day	Property launch	Use launch-day guide	Launch teaser
Dormant list	Cold-buyer win-back	Autonomous win-back guide	Win-back marketing
Visit confirm	Visit reminder	No	Utility
Construction facts	Construction updates	No	Email / utility

Honest limitations

G1, G2, G6, G7, G8, G9, G11, G17. IMAGE headers uploaded. Buttons may need manual add. Conversion = replies. Wallet-only.

Keep this Listing campaigns how-to 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 Library. Growth campaigns. Wallet. Agents → Studio. Pipeline. Property-campaigns playbook as the job you execute. Canonical playbook: Property campaigns 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.

Campaigns. Pricing. Launch day. Approval.

Frequently asked questions

Performance teams wanting a WhatsApp-only campaign microsite.

Is this a WhatsApp-only playbook URL?

No. The job is property-campaigns, omnichannel (WhatsApp + email etc.). This is a how-to.

Can I skip the playbook and only read this?

This is the checklist. The playbook is the job page we want operators to run.

Autonomous instead of Growth?

Possible with existing template. Monitor sends/reads. Still staff inbox.

Interested button?

Add on the template if you want; not a CRM state. Conversion still replies unless you track pipeline.

When to use email?

SES for long decks. WhatsApp for the ping. One contact.

Money?

Preview Organization wallet every send. Pricing.

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

Preview the wallet, send the listing template, staff replies

Then operate from the property-campaigns playbook — not a nested WhatsApp URL.

Get started free