RERA Rules for WhatsApp and SMS Property Marketing

A marketing lead at a mid-sized developer has a WhatsApp broadcast list of 5,200 numbers ready for a festive-season offer — a locality-based project, a limited-time booking discount, and a link to a brochure PDF. His finger is over "send." He knows print ads need a RERA registration number stamped somewhere on the page. What he's genuinely unsure about is whether the same rule applies to a WhatsApp message that's mostly an image and two lines of text, or a 160-character SMS with barely enough room for the project name and a phone number. And underneath that uncertainty sits a sharper anxiety: if this broadcast gets flagged, is the exposure just a RERA complaint, or does an unregistered bulk-SMS sender also risk a TRAI penalty on top of it? Both risks are real, they come from two different regulators, and they don't cancel each other out. This guide walks through how a developer's WhatsApp and SMS campaigns can satisfy both.

Why WhatsApp and SMS Count as "Advertisement" Under RERA

RERA's definition of advertisement is built around function, not format: any notice, circular, brochure, or document — including electronic communication — that invites the public to purchase, book, or invest in a plot, apartment, or building. A WhatsApp broadcast promoting a specific project's price and booking window, or a bulk SMS reading "Book your dream home at [Project], starting ₹XX Lakh, call now," both meet that functional test as clearly as a newspaper display ad does.

This isn't a purely theoretical extension. MahaRERA — Maharashtra's real-estate regulator — has taken the explicit position that promotional SMS and other electronic messaging directed at prospective buyers fall under the Act's definition of advertisement and must therefore carry the project's registration number, treating the format of the message as irrelevant to the underlying obligation. That's a state-specific example, presented here as a public fact with its source rather than as a claim that every state authority has issued identical guidance — developers running multi-state campaigns should confirm the exact wording that applies through the relevant state RERA portal, since disclosure phrasing can differ from state to state.

The practical takeaway is the same regardless of state: if a message invites booking or investment in a specific registered project, treat it as a regulated advertisement and give it a defensible path to the RERA number, even in a channel that technically allows only a couple of lines of text.

Step-by-Step: Making a Messaging Campaign Compliant

1. Establish the canonical RERA number and status once. As with any other channel, the registration number, validity period, and project status should live in one place — the builder project record — so a marketing team building a festive campaign under time pressure isn't retyping it from memory or an old brochure.

2. Register the sender and template on TRAI's DLT platform before sending anything commercial. India's Telecom Regulatory Authority requires commercial SMS senders to register their entity, sender header, and message templates on a Distributed Ledger Technology (DLT) platform. Messages sent from unregistered headers or using unapproved templates are liable to be blocked by telecom operators — this is a separate compliance layer from RERA, run by a different regulator, and both apply simultaneously to a real-estate SMS campaign.

3. Build the message so the RERA number and a link do the disclosure work. A 160-character SMS realistically can't fit a full disclosure block. What it can fit is the RERA number in short form plus a link: "3BHK at [Project], Pune. RERA: P52100XXXXX. Details: [short link]." The link should point to the project's listing page, which carries the fuller disclosure — status, validity, promoter details.

4. For WhatsApp, use the same principle across message types. A text-only broadcast, an image with caption, or a WhatsApp Business catalog entry should each carry the RERA number as visible text (in the caption or message body, not only inside an image) plus a link to the disclosure-consistent landing page.

5. Confirm WhatsApp Business API opt-in before sending. WhatsApp's Business Platform requires documented opt-in consent before a business can message a user via template messages outside an active customer-service conversation window. A number scraped from a property portal or bought from a data broker, without that specific opt-in, exposes a developer to WhatsApp policy action independent of any RERA question.

6. Localize templates without dropping the disclosure. A Marathi, Telugu, or Tamil SMS template still needs the RERA number preserved exactly as registered — translating or transliterating the project name is fine; altering the registration number format is not, and each localized template typically needs its own DLT approval.

Channel-by-Channel Disclosure Placement

Geographic and Demographic Specifics: TRAI DLT, MahaRERA, and DPDP

Three regulatory threads run through this specific channel that don't apply the same way to display or search advertising, and a developer's marketing and compliance teams need to track all three together rather than treating "RERA compliance" as the only checkbox.

TRAI DLT registration. Since telecom operators enforce DLT compliance at the network level, an unregistered sender header or an unapproved template can simply fail to deliver — which is a business problem before it's even a legal one. Registering the sender entity and pre-approving message templates (including localized versions) is a prerequisite step that should happen well before a campaign's planned send date, not the week of.

MahaRERA's stance on electronic advertisement. As noted above, Maharashtra's regulator has explicitly extended the "advertisement" definition to promotional SMS and electronic messaging. Developers marketing projects in Maharashtra should treat this as settled guidance for that state; developers marketing across multiple states should independently confirm each relevant RERA authority's position rather than assuming uniform national guidance exists.

DPDP Act, 2023 consent obligations. According to Deloitte India's analysis of the DPDP Rules 2025, the Act requires clear consent before sharing personal data with third parties and imposes penalties that can run into hundreds of crores for significant non-compliance. For a developer's marketing operation, the practical implication is that a buyer's mobile number collected through a consented enquiry — say, via a builder's leads workflow — carries a defensible consent trail, while a purchased or scraped number list does not. This is a genuine tailwind for developers who build campaigns from their own consented leads rather than resold databases: it reduces exposure on the DPDP side while also naturally producing a warmer, more responsive audience for the campaign itself.

Mini Scenario: A Pune Developer's Festive WhatsApp Blast, Reworked

A Pune-based developer's marketing team has a Diwali offer ready: a WhatsApp broadcast to 8,000 numbers pulled from a mix of website enquiries and a purchased database from a previous campaign. The draft message is an image of the project's tower with a caption reading "Diwali Dhamaka Offer! Book Now!" — no RERA number, no link, and no clarity on which numbers ever opted in.

Before sending, the team makes three changes. First, they filter the send list down to numbers with a documented enquiry or opt-in on file — cutting the list to about 5,100 numbers but removing the consent risk entirely. Second, they update the caption to read "Diwali offer at [Project Name], Baner. RERA: P52100XXXXX. Full details: [link]," with the link pointing to the project's DrawMagic listing page. Third, they confirm the WhatsApp Business template used for the broadcast is pre-approved and includes a standard opt-out line. The resulting campaign reaches fewer numbers than the original list but carries materially lower regulatory exposure on both the RERA and DPDP fronts, with a consent trail the team can point to if ever asked.

Consent and Opt-Out: DPDP and TRAI Obligations for Builders

Beyond the RERA disclosure question, two separate obligations govern who a developer can message and how. Under TRAI's regulatory framework for commercial communication, every promotional SMS and template message should include a clear opt-out mechanism, and numbers that have opted out (including via the National Customer Preference Register / DND registrations for promotional content) shouldn't be re-targeted with fresh campaigns. Under the DPDP Act, consent for marketing communication should be specific to that purpose — a number collected for a "download the floor plan" enquiry doesn't automatically license months of unrelated promotional broadcasts unless the original consent covered that use. Neither of these is a RERA requirement, but both sit in the same compliance conversation for any developer running bulk messaging, and getting them wrong creates exposure that has nothing to do with the RERA number being correct or not.

Pro Tips

1. Build your send lists exclusively from consented enquiry channels — /builder/leads — rather than purchased or scraped number databases, which reduces DPDP exposure and typically improves response rates.
2. Pre-register DLT templates for every localized language variant you plan to use well ahead of a campaign's launch date, since approval isn't instant.
3. Keep the RERA number in every message as plain text, never only inside an image, so it's visible even on devices that don't auto-load images.
4. Route every short link in an SMS or WhatsApp message to the same disclosure-consistent listing page used across your other ad channels, not a campaign-specific microsite.
5. Maintain a simple internal log of opt-outs and DND-registered numbers so future campaigns don't accidentally re-include them.

Common Mistakes to Avoid

• Sending from an unregistered DLT header or template, which telecom operators can block outright regardless of RERA status.
• No RERA number anywhere in the message, relying solely on the recipient calling to ask for details.
• Using purchased or scraped number lists with no documented consent trail, creating DPDP exposure independent of the RERA question.
• Superlative or certainty language ("guaranteed returns," "best deal in the city," "assured possession") in SMS or WhatsApp copy — the same claim-words that create risk in every other ad channel apply here too.
• Ignoring opt-outs across campaigns, re-messaging numbers that have already asked not to be contacted.

Integrating This With Other DrawMagic Features

This workflow is designed to reuse a developer's existing DrawMagic setup rather than requiring a separate messaging-compliance tool. /builder/leads is where consented buyer enquiries live, giving marketing teams a documented-consent send list instead of a purchased database. /builder/listings is the canonical, disclosure-consistent project page that every short SMS or WhatsApp link should point to, so the message itself only needs to carry the RERA number and a link rather than a full disclosure block. And /builders is the portal overview for developers setting this up for the first time. As IBEF's Real Estate Industry in India report (as of February 2026) frames it, the sector's growth is increasingly digital and direct-to-consumer, which makes bulk messaging one of the fastest-growing — and most easily mishandled — channels for developer marketing teams to get compliant early rather than retrofit later.

Value Note

The value of working from consented leads isn't only regulatory — it compounds. A send list built from /builder/leads enquiries already contains people who've shown some interest in the project or locality, so a compliant, well-disclosed campaign to that list tends to outperform a larger but cold, purchased list on response rate — the same practice that reduces RERA and DPDP exposure also tends to produce a better-performing campaign. Consider exploring the builder portal if you're currently running bulk campaigns from purchased number lists.

Key Takeaways

• WhatsApp broadcasts and bulk SMS promoting a specific registered project are advertisements under RERA's functional definition, regardless of character-count constraints.
• MahaRERA has explicitly extended the advertisement definition to promotional electronic messaging — a state-specific precedent worth knowing, not a universal national rule; confirm your specific state's position.
• TRAI's DLT registration for sender headers and message templates is a separate, mandatory compliance layer on top of RERA disclosure.
• DPDP Act, 2023 consent obligations mean purchased or scraped number lists carry real regulatory exposure that consented enquiry lists don't.
• Fit the RERA number and a link to the full disclosure page into the message itself; don't rely on a follow-up call to disclose it.
• WhatsApp Business API messaging requires documented opt-in consent, independent of RERA requirements.
• Keep one canonical RERA record and route every SMS/WhatsApp short link to the same disclosure-consistent listing page.
• This is a compliance workflow guide, not legal advice — confirm exact state RERA wording and current TRAI/DPDP rules with a licensed professional before large-scale campaigns.

FAQ

Can a 160-character SMS really disclose a RERA number properly? Yes, in short form plus a link — the SMS carries the RERA number as text and a short link to the project's full disclosure page, rather than trying to fit the entire disclosure block into one message.

Does TRAI DLT registration replace the need for RERA disclosure? No — they're separate regulators addressing separate concerns. DLT registration governs who can legally send commercial messages through telecom networks; RERA disclosure governs what a real-estate advertisement must reveal to the public. A campaign needs to satisfy both independently.

Is a purchased WhatsApp number database ever safe to use for property marketing? It carries meaningfully higher DPDP consent exposure than a list built from documented, purpose-specific enquiries. Building campaigns from consented leads is the lower-risk and generally better-performing approach.

Bring your project's RERA number and buyer enquiries into one place — start with the DrawMagic builder portal and manage consented leads through /builder/leads.