Z
Zappio Team
AI & Real Estate Experts · 13 July 2026 · 11 min read
Loading article...
Zappio Team
AI & Real Estate Experts · 13 July 2026 · 11 min read
Every AI Calling script for a Gurgaon or Faridabad real estate project operates inside a compliance envelope defined by the Haryana Real Estate Regulatory Authority (HARERA). An AI that discloses the wrong RERA registration number, cites an expired project phase, or makes a possession timeline claim that contradicts the developer's registered agreement is not merely making a sales error — it is creating a regulatory liability. Under Section 61 of RERA, a developer can face a penalty of up to 5% of the estimated project cost for false statements or omissions in connection with a registered project, and an AI Calling system generating 2,000 such calls per month magnifies that liability proportionally.
HARERA has been among India's most active state RERA authorities in enforcement, levying over ₹400 crore in penalties between 2022 and 2025. In 2026, HARERA's revised regulatory framework — including new disclosure requirements for AI-mediated and digital communications — has introduced specific obligations that affect how AI Calling scripts must be engineered for Haryana-registered projects.
HARERA's 2025–2026 circular framework, aligned with MoHUA's model RERA guidelines revision, requires that any digital communication referencing a registered project include the project's RERA registration number as a primary disclosure — not buried in fine print, but stated as part of the core project identification. For an AI Calling script, the HARERA registration number must appear in the first substantive mention of the project within the call: "Main aapko [Project Name] ke baare mein bata raha hoon — yeh HARERA registered project hai, registration number [HRERA-GGM-XXXXXX]. Gurgaon ke [Sector/Corridor] mein hai." The HARERA number must be pulled from the project's live CRM configuration, not hardcoded in the script — when a developer launches a new phase with a separate HARERA registration, the AI system must automatically update to the new registration number for that phase's leads.
HARERA's 2026 enforcement guidelines specifically address developer communications that cite possession timelines diverging from the RERA-registered possession date. Any AI Calling system that states a possession date must reference only the HARERA-registered date for that project phase — not a marketing timeline, a broker briefing estimate, or an informal sales team update. Non-compliant: "Possession December 2026 ke liye expected hai" (without HARERA-registered date verification). Compliant: "[Project Name] ka HARERA-registered possession date [Month Year] hai — aap HARERA portal pe verify kar sakte hain registration number [HRERA-GGM-XXXXXX] se." The engineering implication: the project knowledge base must integrate directly with HARERA's project registration database via the HRERA portal's public data feed, not rely on static configuration data updated manually.
HARERA's 2026 digital communications framework aligns with the DPDP Act 2023's consent architecture to require explicit disclosure when a call is AI-initiated rather than human-initiated, and recorded for quality or compliance purposes — within the first 30 seconds. Standard compliant opening: "Namaste [Name]ji, main [Project Name] ki team ka AI Assistant hoon — aapki inquiry ke liye call kar raha hoon. Yeh call quality ke liye record ho sakti hai. Kya aap 5 minute de sakte hain?" The phrase "AI Assistant" — or equivalent natural-language disclosure of automated origin — is the operative compliance element. An AI Calling system that presents itself as human without disclosure operates outside the acceptable boundary under both HARERA's digital communication standards and the DPDP Act's consent requirements.
RERA Section 4(2)(l)(C) mandates that all project communications reference carpet area as the primary unit measurement, not super built-up area. HARERA enforcement in 2025–2026 has specifically flagged marketing communications — including recorded sales calls — that quote only super built-up area pricing without carpet area disclosure. For a Gurgaon developer whose 3BHK has a carpet area of 1,150 sq ft but a super built-up area of 1,680 sq ft (a 46% loading factor common in premium high-rise projects), an AI script that says "3BHK, 1,680 square feet at ₹1.45 crore" without carpet area qualification cites the super built-up number in a way that could be construed as misleading. Compliant disclosure: "3BHK — carpet area 1,150 square feet, super built-up area approximately 1,680 square feet. Current pricing ₹1.45 crore for Phase 1." This distinction must be built into the script at the configuration disclosure turn, not left to the site visit stage.
A HARERA-compliant AI Calling system for Gurugram projects requires a structured compliance knowledge base for each registered project phase — all fields verified against HRERA portal registration data.
@dataclass
class HARERAProjectConfig:
"""
HARERA-compliant project configuration for AI Calling scripts.
All fields must be verified against HRERA portal registration data.
"""
harera_registration_number: str # e.g., "HRERA-GGM-45-2023"
project_name: str
developer_legal_name: str # As registered with HARERA
phase_number: int
sector: str
district: str # "Gurugram" or "Faridabad" etc.
corridor: str
configurations: list # ["2BHK", "3BHK", "4BHK"]
carpet_area_sqft: dict # {"3BHK": 1150, ...}
super_builtup_area_sqft: dict # {"3BHK": 1680, ...}
loading_factor_pct: dict # {"3BHK": 46, ...}
bsp_per_sqft_carpet: float
plc_charges: dict
registered_possession_date: date # From HRERA registration — DO NOT override
registered_amenities: list
occupancy_certificate_received: bool
completion_certificate_received: bool
escrowed_collections_pct: float # RERA mandates 70% in escrow
def get_compliant_script_disclosure(self, configuration: str) -> dict:
carpet = self.carpet_area_sqft.get(configuration, 0)
superbuilt = self.super_builtup_area_sqft.get(configuration, 0)
loading = self.loading_factor_pct.get(configuration, 0)
return {
'harera_disclosure': (
f"HARERA registered project — registration number "
f"{self.harera_registration_number}. Aap hrera.gov.in pe verify kar sakte hain."
),
'area_disclosure': (
f"{configuration}: carpet area {carpet} sq ft, "
f"super built-up area {superbuilt} sq ft ({loading}% loading factor)."
),
'possession_disclosure': (
f"HARERA-registered possession date: "
f"{self.registered_possession_date.strftime('%B %Y')}."
),
}A critical failure mode for AI Calling systems is calling leads with an expired or incorrect HARERA number — either because the developer manually updated the script with the wrong phase registration, or because the project received a HARERA extension not reflected in the calling system's configuration.
This automated validation eliminates the category of compliance failure caused by organizational lag — the gap between when HARERA data changes and when the calling system's configuration is updated.
| Script Element | HARERA Requirement | Non-Compliant Version | Compliant Version |
|---|---|---|---|
| Project identification | HARERA number in first mention | "Main [Project Name] ke baare mein..." | "[Project Name], HARERA reg. [number]..." |
| Area disclosure | Carpet area primary | "2,100 sq ft flat" (superbuilt) | "Carpet area 1,450 sq ft (superbuilt ~2,100 sq ft)" |
| Possession date | HARERA-registered date only | "Possession end of 2027" | "HARERA possession date: December 2027" |
| Price statement | Per sq ft on carpet area basis | "₹8,500/sq ft" (ambiguous basis) | "₹8,500/sq ft carpet area basis" |
| AI disclosure | AI origin disclosed within 30 sec | "Hi, I'm calling from [Developer]" | "I'm [Developer]'s AI Assistant..." |
| Recording disclosure | Within 30 sec of call start | Not mentioned | "Yeh call record ho sakti hai" |
| PLC charges | Must be mentioned if applicable | Silent on PLC | "PLC charges applicable for [orientation/floor]" |
HARERA governs real estate project disclosures and developer conduct. It does not govern the AI system's handling of buyer financial information, data retention, or consent for follow-up communications — these are governed by the DPDP Act 2023 and general contract law. AI Calling systems for HARERA-registered projects must comply with both regulatory frameworks simultaneously: HARERA scope covers project disclosures, possession dates, carpet area, RERA registration visibility, pricing basis, and amenity commitments, while DPDP Act scope covers consent for data collection, call recording consent, right to erasure, data localization, and purpose limitation for buyer data use. The practical engineering solution is a unified compliance layer at the system prompt level — disclosure rules and prohibited statements covering both frameworks, reviewed by the developer's legal team before deployment.
HARERA's 2026 updates make clear that compliant AI Calling is not a matter of writing a careful script once — it is a matter of building a system that pulls registration numbers, possession dates, and area disclosures from live, verified HARERA data on every call, and that automatically halts outreach when that data no longer matches the script's assumptions. Developers and channel partners running AI Calling at scale on HARERA-registered projects should treat the compliance knowledge base as a first-class piece of infrastructure — reviewed by legal counsel, validated nightly against the HRERA portal, and isolated per project phase — rather than a one-time script approval exercise.
Disclaimer: HARERA regulatory requirements, compliance benchmarks, and enforcement references in this article are based on publicly available HARERA circulars, MoHUA RERA guidelines, and real estate compliance data as of Q1–Q2 2026. RERA regulations, state authority circulars, and enforcement priorities change frequently — all AI Calling script content and compliance frameworks for Haryana-registered projects must be reviewed and approved by qualified legal counsel familiar with HARERA before deployment. This article does not constitute legal advice. Penalty figures and enforcement statistics cited are estimates based on publicly reported HARERA enforcement actions and should be independently verified.