Conversation agent
Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.
RERA and WhatsApp property messages
What automated messages can claim, with a compliance posture, not legal advice. CoPulse will send whatever approved template you store. It will not be your advocate. ROI guarantees, invented inventory, and ‘RERA approved returns’ in a marketing blast are how desks get into trouble. Keep knowledge bases and Library copy conservative; RMs still own exceptions in inbox.
- Not legal advice
- Templates are statements
- Knowledge base can lie if you upload lies
Definition
RERA-aware WhatsApp operations means treating library templates, knowledge-base FAQs, and agent replies as customer-facing statements about a registered project: factual inventory and process, no invented returns, with opt-out on marketing sends — implemented as operator policy on a CoPulse Project, not as a built-in legal engine.
Why bots amplify brochure sins
A PDF with a footnote becomes a WhatsApp sentence without the footnote. Autonomous win-back repeats it at scale. Reads look like success. Counsel is not in the clarify wizard.
Opt-out-compliance playbook is the operational job. This guide is claims posture. Pair with opt-in guide.
HowTo: a desk policy (still not legal advice)
Have counsel review Library marketing templates and knowledge FAQs. Agents should cite files, not invent schemes.
- Inventory facts only in KB Price bands you honour. No fantasy stacks.
- Marketing templates reviewed Launch and listing copy. No return guarantees.
- Utility stays transactional Visit times, docs, delays.
- RM exceptions in inbox Handoff for anything legal/financial.
- Opt-out on blasts Honour stops. See opt-in guide.
How it runs on the platform
There is no RERA API in CoPulse. Policy is yours. Product sends what you approved. 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.
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: rejected template, rewritten
Listing template claims ‘assured rental 8%.’ Provider or counsel rejects. Rewrite: ‘See the project RERA page and price list in the knowledge base; book a visit.’ Agent on WhatsApp cites the file. NRI asks FEMA — immediate RM handoff, no bot essay.
Construction updates: delays factual. Do not hide. Cadence guide. Still not legal advice.
Claim × surface × owner
Who is allowed to say it.
| Claim type | Template / KB? | Who says it | Guide note |
|---|---|---|---|
| Price band you sell at | Yes if true | Agent cite KB | Keep updated |
| ROI / assured rental | Usually no | Never bot | Counsel |
| RERA registration number | If official | KB / site | Do not invent |
| Loan approval odds | No | RM / bank | Loan guide |
| Visit time | Utility yes | Agent / Growth | Capacity honest |
Honest limitations
Not legal advice. No automatic RERA scraping. G7 will not generate compliant images for you. Adaptive ‘safer copy’ is not shipped (G2).
Keep this RERA and WhatsApp 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 review. Agents → Studio knowledge. Growth audiences. Inbox. Opt-out-compliance playbook. Not a ‘RERA module’ button. Canonical playbook: Opt-out compliance 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.
Related
Frequently asked questions
Desks pasting brochure superlatives into WhatsApp.
Does CoPulse block non-compliant templates?
The provider may reject. We do not replace your counsel. Conservative copy is an operating choice.
Can knowledge bases include the RERA certificate PDF?
Yes, if you upload it. The agent can cite it. Keep it current.
Launch teasers?
Marketing templates. Review before T-3. Launch-day runbook.
Broker speaking for a developer?
Do not claim principal discounts you cannot honour. Developer vs broker scripts.
Is this a substitute for RERA filings?
No.
Wallet?
Sends still meter. Compliance does not change pricing markups. See pricing.
Related
Hub, sibling guides, canonical playbook, product, pricing.
All real estate guides
How-to articles. Jobs live on playbooks.
Directory →Opt-out compliance playbook
The omnichannel job this guide teaches.
Playbook →Opt-in / opt-out
Consent on the same blasts.
Guide →Template approval
Category and submit.
Guide →Campaigns & drips
Matching product surface.
Product →Pricing
Wallet-only. No seat fees. Preview before send.
Pricing →Cite facts you uploaded, not returns you invented
Review Library and knowledge bases — then send. Not legal advice.
Get started free