Skip to content
Meta Business Partner

OTP Authentication WhatsApp Template for Real Estate

Property portals, broker CRMs and RERA-registered developers all need one thing before a buyer can act: a verified phone number. This is a ready-to-use, Meta-compliant WhatsApp OTP template built specifically for real estate logins, site-visit bookings and document access. It ships with the correct Authentication category, a secure copy-code button, and pre-filled variables — so you copy it, drop in your brand name, submit for approval, and start verifying buyers on the channel they actually open. OTPs delivered on WhatsApp are typically read within seconds, which matters when a code expires in ten minutes and a serious lead is waiting on the other end.

A Meta-approved WhatsApp Authentication template for real estate OTPs — with a copy-code button, two variables, and approval notes — that you can copy, personalise and send through InfiQ in minutes.
authentication

Variables

  • {{1}} = 482917
  • {{2}} = UrbanNest Realty

Verified business

482917 is your UrbanNest Realty verification code. It is valid for 10 minutes. Do not share this code with anyone.

10:24

Copy code

Preview · as customers see it

When to use this OTP template in a real estate journey

An Authentication template exists to confirm a user actually controls the number they entered, so trigger it at genuine identity checkpoints in the buyer or tenant journey — never as a nudge or a promotion. In real estate, that means the moment a lead signs into your listings portal or app, when a prospect books a physical site visit and you want a verified callback number, when a buyer requests a floor plan, brochure or price sheet gated behind a login, or when an existing customer accesses their booking, payment schedule or KYC documents. Because the code is time-boxed to ten minutes and shown with a one-tap copy button, the friction between 'I want this property detail' and 'I'm verified and viewing it' collapses to a few seconds.

  • Portal or mobile-app sign-in for buyers, tenants and channel partners
  • Site-visit and show-flat booking confirmations that need a verified number
  • Access to gated brochures, floor plans, cost sheets or RERA documents
  • Booking-account, payment-schedule or KYC document logins for existing customers
  • Broker or sub-agent onboarding into your CRM

Personalising it without breaking the Authentication rules

The Authentication category is deliberately strict: the body must be a security message and nothing else. Your two levers are {{1}}, the one-time code your system generates, and {{2}}, your brand or project name — for example 'UrbanNest Realty' or a specific tower like 'Prestige Lakeside'. Using a recognisable project name in {{2}} raises trust and cuts the chance a buyer dismisses the code as spam, which is a real problem in property where scam messages are common. What you cannot do is add a greeting with the customer's name, a listing image, a marketing line, a discount, or a link to your project page — any of that will get the template rejected or downgraded out of Authentication. Keep personalisation to the brand variable and let the copy-code button carry the interaction. If you need a name or richer context, that belongs in a separate Utility or Marketing template, not this one.

Getting it approved on the first submission

Submit this as Authentication (not Utility, and never Marketing) and use the standard OTP structure Meta expects: the code variable first, a validity window, and a 'do not share' warning, paired with a copy-code button. Templates that follow this canonical shape are usually reviewed within a day and often much faster. The common reasons real estate OTP templates get rejected are avoidable — a marketing phrase slipped into the body, a URL button, an image or document header, or wording that reads like a notification rather than a verification. Keep the body to a single clean security sentence, keep the copy-code button as the only interactive element, and match {{2}} to the display name on your verified WhatsApp Business number so the sender and the brand in the message line up.

  • Category must be Authentication with a copy-code button
  • No greeting, name, image, link, emoji or promotional text in the body
  • State the validity window and a 'do not share' warning explicitly
  • Match the brand variable to your verified sender display name

Why WhatsApp beats SMS for property OTPs

SMS OTPs in India routinely land in spam folders, hit DLT-template friction, or arrive late enough that the code has expired by the time the buyer taps back into your app — a costly stumble when the lead is a high-intent property enquiry. Delivering the same OTP on WhatsApp gives you near-real-time delivery, read receipts you can actually see, and a one-tap copy button that removes typos. It also sits in the low-cost Authentication category. WhatsApp bills per delivered message by category — Authentication is priced separately from Utility and Marketing — so a verification code is one of the cheapest messages you can send. Through InfiQ you pay transparent ₹ pricing (ex-GST), with your BSUID and WhatsApp Business Account fully owned by you, so there is no lock-in on the asset your verification flow depends on.

Like this template? Send it live in 24 hours.

Talk to InfiQ

Use this template in your account

Tell us your volume — we’ll load your templates and get you a sandbox in about 2 hours.

Step 1 of 2
WhatsApp

Protected by invisible spam checks · replies within 1 working day

Frequently asked questions

Which category should this template be submitted as?+
Authentication. OTP and verification-code messages belong in the Authentication category, which uses the secure copy-code button format and is priced separately from Utility and Marketing.
Does an OTP template need opt-in?+
Consent still applies — you should only message users who have shared their number and expect to hear from you. Authentication messages are tied to a real action the user just took, such as logging in or booking a site visit, which is what makes them compliant to send.
Can I edit the wording of the OTP message?+
Yes, within Authentication rules. You can adjust the validity window or the security warning, but you cannot add greetings, names, links, images or any marketing content. Any edit means re-submitting the template for approval.
How is this template billed?+
WhatsApp bills per delivered message by category, and this is an Authentication template, so it bills at the Authentication rate each time a code is delivered. The 24-hour window is a free service window for replies, not a billing unit. With InfiQ you see transparent ₹ pricing, ex-GST.
How fast can I start sending after submitting?+
Authentication templates in the standard OTP format are usually approved within a day, often sooner. Once approved, you can trigger it instantly from your login or booking flow through InfiQ's API.
Why put my project or brand name in the second variable?+
Property buyers receive a lot of scam messages, so a recognisable project or company name in {{2}} — like 'Prestige Lakeside' — signals the code is genuine, lifts trust, and reduces the chance the OTP is ignored. It should match your verified sender display name.
Can I add a link to the property or app in this template?+
No. Authentication templates cannot contain URLs, buttons other than copy-code, images or promotional wording. If you need to send a listing link, use a separate Utility or Marketing template instead.
What causes real estate OTP templates to get rejected?+
The usual culprits are a marketing phrase in the body, a URL or CTA button, an image or document header, or wording that reads like a general notification rather than a security code. Keep it to one clean verification sentence with a copy-code button and it should pass.