Guide · Template approval

WhatsApp template approval for property

Utility vs marketing templates for property, submitted from the library, with Gupshup as the live WhatsApp path. Approval is a BSP/provider process. CoPulse stores the artefact and sends it. Autonomous tasks will not create the template your plan wishes existed. AI draft is text-only; you upload IMAGE headers.

Library is the source of truth
Gupshup, not invented Meta Cloud
Planner only picks existing approved templates

Start free Property campaigns playbook

Definition

WhatsApp template approval is submitting a named message (category utility or marketing, language, body, optional header/buttons) from the CoPulse library through the connected Gupshup WhatsApp channel until the provider marks it approved — after which Growth, inbox template sends, and autonomous tasks may pick it for closed-window outbound.

Why launch morning is the wrong time to submit

Approvals take time and can reject property claims. Teams then type free text to 2,000 numbers and fail the 24-hour rule. Or they reuse a rejected marketing body as ‘utility’ and get blocked.

Companion to the 24h guide and property-campaigns playbook.

HowTo: submit without drama

Write conservative copy. Pick category honestly. Upload media yourself. Wait. Then attach to Growth or autonomous.

Choose category Visit confirm / docs = often utility. Listing teaser = marketing.
Draft in Library AI text draft optional. Add buttons yourself if you need them (G8).
Upload IMAGE if any No auto-generated IMAGE headers (G7).
Submit via Gupshup path Setup → Channels already connected.
Only then plan sends Wallet preview. Autonomous clarify can now pick it.

How it runs on the platform

Library is the artefact store. Campaigns and autonomous are consumers. Inbox agents mostly free-text in-session. 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: visit_confirm vs listing_teaser

Operator creates visit_confirm utility with appointment variables. Submits. Approved in a day. Qualifier still free-texts in-session; T-24h send uses the template. Second artefact listing_teaser marketing with uploaded facade photo. Rejected once for exaggerated ROI language — rewrite conservative, resubmit. Launch waits. No Meta Cloud toggle.

RERA-sensitive words belong in the RERA guide. Not legal advice. Opt-out language belongs in templates you will blast.

Category cheat sheet (operational, not legal)

Your BSP is the authority. This is how desks usually split property copy.

Use	Typical category	Consumer in CoPulse	If still pending
Visit reminder	Utility	Growth or template send	Do not free-text blast
Docs request	Utility	Inbox / workflow	Wait
New stack teaser	Marketing	Growth / autonomous	Delay launch
Win-back dormant	Marketing	Autonomous / campaign	Pick existing only
Construction alert	Utility if truly transactional	Careful Growth	See cadence guide

Honest limitations

G1, G7, G8, G9, G15 (Meta Cloud commented). We do not promise approval times. We do not auto-fix rejections with adaptive copy.

Keep this Template approval 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 templates → create/submit. Setup → Channels WhatsApp Gupshup. Growth / Autonomous / inbox send. Organization wallet. 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.

24-hour window. WhatsApp product. RERA.

Frequently asked questions

Teams submitting copy at 9:55 on launch day.

Does CoPulse approve templates itself?

No. The provider does. We submit via the connected Gupshup path and store status.

Can autonomous create a missing template during plan?

Not today. Clarify asks you to pick one that exists.

IMAGE headers?

You upload. AI draft is copy-only.

Quick reply Interested?

Add in the template builder. Draft JSON may omit buttons. Interested is still not a first-class CRM state.

SMS templates?

Do not plan them as live.

Cost?

Submission/sends meter per channel and wallet. See pricing.

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

Submit before you schedule the blast

Library on Gupshup, honest category, then Growth — property campaigns playbook.

Get started free