Electricity board
Verified · WhatsApp
Electricity bill · Aug
₹1,248.00
Due 24 Aug · Consumer 4471 9920
Pay ₹1,248
Paid by UPI
Receipt · Settled
Payment confirmed
T+1 settlement · ref PL-88214
Message
Billers
A billing base this big needs the chat every customer already opens.
Whether you bill a lakh customers a cycle or a crore, every bill lands in the chat they already use, and they pay it right there by UPI, card, net banking or wallet. Nothing to install, no portal to log in to, and one customer record behind WhatsApp, RCS, Voice AI and WhatsApp Calling.
Illustrative animation of one monthly bill run. Bills for electricity, broadband, property tax, water, cable TV and civic fees go out to six customers' chats. Each customer pays by UPI, card, net banking or wallet, the payment returns to the centre and is counted, and a receipt is sent back in the chat.
Trusted by
Power distribution · Maharashtra
Life insurance
Broadband
Urban transit
Municipal corporation
Power distribution · Odisha
Life insurance
Direct-to-home television
Housing finance
Urban transit
Power distribution · Indore
Business process services
Broadband
Life insurance
Urban transit · Chennai
Financial infrastructure
Power distribution · Bengaluru
Municipal corporation · Mumbai
Digital cable television
Payments
Urban transit
Power distribution · Bhopal
Life insurance
Broadband
Municipal corporation · Ranchi
Two-wheeler finance
At utility volume
Volume and settlement terms
- households in network
100Mn+
households in network
- outcomes delivered per month
8Mn+
outcomes delivered per month
- Settlement
T+1
Settlement
settlement, working days
One thread
They get the bill, pay it and keep the receipt, all in one chat.
- The bill arrives as a message, with the amount and due date up front.
- One tap to pay by UPI, card, net banking or wallet, without leaving the chat.
- The receipt lands in the same thread, easy to find next month.
- Your team sees every payment matched to its bill. No spreadsheet chase.
Three sample chat threads. An electricity board sends a bill that is paid by UPI; a broadband provider answers a customer's voice note and the plan is renewed by card; a municipal corporation sends a property tax notice that is paid by net banking. Each receipt returns to the same thread.
Illustrative threads. Amounts and reference numbers are examples.
Whatever you bill for
Power, broadband or property tax. Paying works the same way.
The bill looks different in each case. What your customer does with it does not: open the message, pay, keep the receipt.
Utilities
Electricity and water
The monthly bill reaches every connection on the chat they already use, and meter questions get answered in the same conversation.
- Bill in the chat
- Paid by UPI
- Receipt saved
Subscriptions
Cable and broadband
A reminder before the plan runs out, a one-tap renewal, and every complaint tracked against the operator's two-tier redressal duty.
- Renewal reminder
- Renewed by card
- Plan stays on
Civic
Property tax and civic fees
Tax notices and civic charges paid straight from the message, with a receipt the resident can pull up whenever they need proof.
- Tax notice
- Paid by net banking
- Receipt on file
What changes
Six things that change from your very next bill.
The bill goes straight to the chat.
Each person gets their bill in the chat they already check every day, right between messages from family and friends. Nothing new to install, nothing to log in to.
They pay right inside the message.
Embedded payments put the checkout in the chat itself: UPI, cards, net banking or a wallet. No redirect to a payment page, and the receipt drops into the same conversation.
Reconciliation runs itself.
Every delivered bill is matched to its payment as it comes in, so your collections team works from one number instead of two spreadsheets.
Every complaint leaves a trail.
Complaints are logged against the customer record with a reference number, and map to the operator's redressal duty.
Outage updates come from the same sender.
Planned maintenance, restoration times and complaint updates arrive from the same verified name as the bill, so nobody mistakes them for spam.
Customers can just ask, out loud.
With Voice AI, a person sends a voice note like “how much is my bill?” in their own language and gets the answer back in the chat, with the bill and a way to pay.
Four channels, one console
Every customer answers differently. You only need one place to reply.
Some read WhatsApp, some only open the inbox their phone came with, and some would rather just talk. Send the bill on RCS, answer the question on WhatsApp, sort out the dispute on a call, and it is still one customer, one history and one consent, in one console.
WhatsApp Business API
Verified sender, template governance and payment by UPI, cards, net banking or wallets inside one thread, provisioned by an official Meta Business Solution Provider.
- Provisioning
- Official Meta BSP
Google RCS
Verified sender branding in the native Android inbox, for the reach of SMS with the surface of an app.
- Surface
- Default Android inbox
Voice AI
Indian-language voice agents that resolve routine calls end to end and hand the rest to your team with context intact.
- Languages
- English, Hindi, 10+ regional
WhatsApp Calling
Voice inside the thread the customer already trusts: no unknown number, no callback roulette.
- Escalation
- Verified, in-thread call
Not sure where to start?
See all four side by side
What each channel does best, where a customer can pay, and how a conversation moves from one to the next without losing its history.
Two ways to collect
Collect straight into your own account, or through BBPS.
Your own collection
A biller collecting its own dues.
When the money is owed to you and settles to your own account, the bill and the payment sit in the chat and nothing routes around you.
Through a BBPS partner
Where the Bharat Bill Payment System applies.
The bill and the settlement route through an authorised operating unit, and your customer still sees the same bill, the same payment and the same receipt in the chat.
Built to pass inspection
Four things a risk committee will ask for.
Meta BSP, in-house
Verification, WhatsApp template review, number migration and throughput are run by Pelocal, not resold.
BBPS where it applies
Where bill payment routes through BBPS, it runs through an authorised operating unit.
TRAI redressal, mapped
Complaints for cable and broadband operators map to the two-tier redressal structure.
DPDP consent, per purpose
Consent is captured per purpose and can be withdrawn, held as one state across channels.
Questions
Burning questions.
No. The bill and the payment sit entirely within the message thread, on a channel customers already have WhatsApp. There's no separate app download, no portal login, and no redirect required. For utilities, DISCOMs, and cable/broadband operators managing millions of households, this removes the single biggest adoption barrier: asking customers to install something new just to pay a bill.
No, billers can collect through their own payment setup, or connect through Bharat Bill Payment System (BBPS) if that's already part of their existing operating structure. Pelocal's billing layer supports both, so utilities aren't forced to re-architect their payment stack just to bring bill presentment and collection onto WhatsApp.
Payments collected through WhatsApp settle on a T+1 working-day basis. Delivery status reconciles automatically against settlement, so collections teams work off one number rather than manually matching message logs against payment gateway records, a critical requirement for utilities and DISCOMs processing 8Mn+ billing outcomes per month.
Every complaint raised through the billing thread is logged against the customer record and mapped directly to the operator's redressal duty creating a complete, auditable trail from complaint to resolution. This matters specifically for cable and broadband operators, where renewal notices and service complaints often live in the same conversation as the bill itself.
Consent is captured once and applies consistently across every channel WhatsApp, RCS, and Voice AI, so it can be revoked as easily as it was given, with no gaps between systems. For risk and compliance committees, this creates a single, defensible consent trail rather than fragmented opt-ins managed separately per channel or per vendor.
Yes. Pelocal supports migration of existing WhatsApp Business numbers and approved templates, so utilities already running WhatsApp billing communication don't lose message history, verified sender status, or approval history when switching infrastructure providers.
The underlying message thread is consistent, but the billing logic adapts to what's being billed: electricity and water follow the monthly consumption cycle with receipt and complaint history in the same thread; cable and broadband map renewal notices to the operator's two-tier redressal duty; municipal and civic billing tie property tax and civic-service payments to a receipt the resident can keep. One infrastructure layer, three adapted billing shapes reduces integration complexity for billers operating across multiple utility types.
Get your bills paid in the chat.
Send us one billing cycle. We'll show you how it runs.