WhatsApp Business API for PG owners: a 2026 guide

If you run a PG, every rent cycle you send roughly 3 to 5 WhatsApp messages per tenant per month — a pre-due nudge, a due-date reminder, maybe an overdue one, plus the receipt. For a 30-bed building that's around 120 messages a month. For a 60-bed building, ~250. Multiply by 12 months and the messaging bill is no longer rounding error.

Meta changed how that bill is computed twice in 2025. If the last article you read about WhatsApp Business pricing was from 2024, throw it out — it's wrong about almost everything. This is the 2026 version.

The four message categories (and what they cost in 2026)

Since 1 July 2025, Meta prices messages by template category, not by conversation. For India-originating business numbers in INR, the shape of the card looks like this:

Those figures are indicative, not a quote. Meta publishes the India rate card itself and revises it periodically — check the current one in WhatsApp Manager or on your provider's pricing page before you budget, and treat any rupee figure in a blog post, this one included, as a starting point rather than a number to plan on.

Read the shape of it carefully, though. Utility messages — which is what almost all of your rent-related comms are — cost around 11 to 12 paise each. A 30-bed building doing 120 utility messages a month is paying somewhere around ₹14 in Meta fees. Even with a provider markup on top, you'll struggle to spend ₹500/mo on the actual messaging unless you're a 200-bed operator.

Meta-direct vs. BSP — the practical choice

WhatsApp Business API isn't something you connect to directly from a web dashboard — you need a Business Solution Provider (BSP). Or rather, you did. Since late 2024 Meta allows direct cloud API access, and the line has blurred. Here are the actual options in 2026:

Option A: Meta Cloud API direct

Free hosting from Meta, you pay per-message prices above. Sounds cheapest, and is — if you have an engineering team. You manage template submissions, phone number registration, webhooks, error handling, retries, opt-out lists, and the FB Business Manager verification dance. For a single PG owner, this is not a real option. You're not going to write Node webhooks at 11pm.

Option B: A messaging BSP

These wrap the Cloud API with a UI and handle verification. They typically charge a per-message markup on top of Meta's rate plus a monthly platform fee — rates and fees vary by provider and change often, so check each vendor's current pricing page before you commit. If all you need is to send template messages, this works. The usual trade-off: you're paying for a generic CRM-ish dashboard you mostly don't use, and for a small PG the platform fee is normally a lot bigger than the messages themselves.

Option C: A vertical app (us, and a few others)

The WhatsApp piece is one feature inside a product that does the rest of the rent workflow — ledger, receipts, leakage reporting, defaulter list, exit settlements. You pay the platform one flat per-hostel subscription — ours is ₹499/mo for up to 75 beds — plus a per-message wallet: we charge a flat ₹0.20 per WhatsApp message, whatever the category. No separate messaging platform fee on top of that.

Which to pick depends on whether you want a messaging tool or a PG tool. If you already run your books in a notebook and want to keep it that way, a BSP is fine. If you want the rent reminder, the receipt, the ledger, and the “who owes me what right now” dashboard to be the same thing, you want option C.

DLT, opt-out, and the legal small print

TRAI's DLT (Distributed Ledger Technology) regime applies to SMS, not WhatsApp. If you're sending rent reminders by SMS — as a fallback, or because some tenants don't use WhatsApp — you need:

• A registered Principal Entity ID
• An approved Header (sender ID like AIRSTY)
• Approved templates for each message type, with variable slots
• Opt-out keyword handling (STOP usually)

WhatsApp's equivalent is the template approval flow inside Meta Business Manager. You submit a template, Meta categorises it (utility / marketing / authentication), and you can only send within that template structure to tenants who haven't blocked you. There's no DLT fee for WhatsApp; Meta's per-message price is the whole bill.

The big question: your own number, or a platform's?

This is where opinions get heated. Three real options:

1. Your personal WhatsApp number

Free. Familiar. Tenants already chat with you on it. Also: no automation, no template fees, no analytics, no way to know who read what, and if your phone breaks you lose the entire history. Plus WhatsApp's terms technically prohibit business use of the personal app at any scale. They won't ban you for 30 messages, but you're on the wrong side of the line.

2. A new dedicated business number, on WhatsApp Business app

Free, still no real automation, but at least your personal life is separate. You can use labels and quick replies. The big problem: tenants now have two contacts for you, and the rent number gets muted because it “feels like spam.” In our own testing, a message from a number the resident already recognises gets engaged with noticeably more often than the same message from an unfamiliar business number.

3. A platform number (or your own number, via WABA)

This is what Aira Nexus Stay does, and our position is opinionated: use your own number, registered through us into the WhatsApp Business API. The tenant sees the same name they already saved. Receipt, reminder, ledger all flow through the same contact. Familiarity matters more than anything else we've tested: a resident who recognises the sender opens; one who doesn't, often won't. We optimise for recognition rather than volume.

“The number tenants already trust is doing the work. The platform is invisible. That's the only way this should work.”

— On using your own number

The catch: once a number is migrated to WABA, you can no longer use it on the regular WhatsApp app on your phone for that account. You'll need a second number for personal use — a basic prepaid SIM, and plans start low. Budget an hour for the switchover itself, not just the SIM: that, rather than the cost, is the real friction.

An actual reminder template, with the math

Here's the utility template we ship as default for the 3-day pre-due nudge — Meta-approved, English-and-Hindi versions, with cost:

Hi {{1}}, your rent of ₹{{2}} for {{3}} is due on {{4}}.
Pay via UPI / Cards: {{5}}
You'll get an instant receipt.
Reply STOP to opt out of reminders.

Five variable slots, 4 lines, ~210 characters. Meta categorises it as Utility. Cost per send from your wallet: a flat ₹0.20. For a 30-bed PG sending this once a month: ₹6. Add the due-day and overdue templates: under ₹20/mo in messaging cost.

That's the part of the bill that's actually about the messages. The rest of what you pay any platform — including us — is for the product that decides when to send, to whom, and what to do with the receipts when they come back. If you'd rather skip the API setup for now, grab the copy-paste WhatsApp rent reminder templates you can send by hand today — or start a free trial and let the reminders run themselves.