Sammaan Capital
Verified · WhatsApp
Home loan EMI · Sep
₹18,450.00
Due 12 Sep · Loan HL-4471
UPICardNet bankingWallet
Net banking
Receipt · Reconciled
₹18,450 received
Loan HL-4471 · Net banking · ref HL-8450
Message
Banking and Lending
Your customer keeps one app open. Pelocal puts their banking inside it.
Pelocal sends reminders, balances and statements in the thread your customer already reads, takes the payment there by UPI, cards, net banking or wallets, and reconciles it against settlement. Every message runs inside RBI outsourcing and recovery-agent rules, on a number Pelocal verified as a Meta Business Solution Provider.
One round trip
01Consent on file
Pelocal sends
A reminder, a balance or a statement, into the thread your customer already has open.
Pays with
Paid by UPISettlement T+1
Illustration of the flow, not a live customer record.
The thread
What your customer reads, and pays.
Reminder or request
The message names the lender, the account and the amount due, or answers a balance or statement request on the spot.
Payment
The customer pays by UPI, cards, net banking or wallets without leaving the chat.
Receipt
The receipt lands in the same thread and reconciles against settlement.
Both threads are sent with consent on file: a pre-due reminder and a statement the customer asked for. Neither is an overdue chase.
Two sample threads. Sammaan Capital reminds a customer of a home loan EMI of 18,450 rupees due on 12 September; the customer picks net banking from UPI, card, net banking and wallet, pays without leaving the chat, and the receipt arrives in the same thread. Credit Wise Capital answers a customer's request for a balance and statement, and the customer pays the next EMI of 3,260 rupees by card in the same thread.
Illustration with sample figures. Not a live customer record.
In deployment
The jobs to be done
- 01
Reminders that end in a payment
The due date, the amount and the payment sit in one thread. The customer pays by UPI, cards, net banking or wallets, with no redirect to a gateway page and no separate app to install.
- 02
Servicing without a call-centre queue
Balances, statements, due dates and loan updates arrive on the channel the customer already reads, and are resolved on WhatsApp or voice, escalating to an agent only when the request needs judgement.
- 03
One record, one consent state
One customer record and one consent state hold across WhatsApp, Google RCS, Voice AI and WhatsApp Calling, so a message sends only where consent covers it.
- 04
Evidence for the audit file
Template versions, consent state, delivery status and payment reference are held against every conversation, and every payment reconciles against settlement for the lender to inspect.
One console
Reach your customer where they are already present.
WhatsApp, Google RCS, Voice AI and WhatsApp Calling share one customer record, one consent state and one template pipeline, so a reminder on RCS and a call on WhatsApp are one conversation, not two vendors and two reconciliation problems.
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
Together
One conversation, not two vendors
The RCS reminder and the WhatsApp call sit on one customer record, with one consent state and one payment reference, so reconciling them is a lookup instead of two exports matched by hand.
At scale
What the network already carries.
100Mn+
households in network
T+1
settlement
settlement, working days
4
channels, one console
one consent state across all
40+
large enterprise customers
Settlement is on a T+1 working day basis.
Lenders, insurers and billers
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
FAQ
Frequently asked questions
Loan defaults often result from borrowers missing repayment dates buried in emails or SMS they don't check. Pelocal's WhatsApp-based repayment journeys deliver due-date reminders, payment links and receipts directly inside the same thread borrowers already use. This improves on-time repayment rates without requiring a new app download or portal login.
A Meta Business Solution Provider (BSP) is directly authorised by Meta to offer WhatsApp Business API access and enterprise messaging infrastructure, as opposed to a reseller operating through a third-party layer. For regulated lenders, this distinction matters for compliance, data handling and audit accountability. Pelocal operates as a native Meta BSP, not a reseller, giving lending institutions direct infrastructure ownership rather than intermediated access.
Yes. A key requirement for lending institutions is that every payment reminder and confirmation delivered on WhatsApp reconciles cleanly against the loan management system, with no manual matching required. Pelocal's servicing layer ties each conversation-based payment event back to the lender's ledger, creating an audit trail suitable for compliance and reconciliation review.
For regulated lenders, knowing where borrower consent lives and how it is captured, stored and audited is a foundational procurement requirement, not an afterthought. Pelocal's WhatsApp lending journeys are built with consent management embedded at the infrastructure layer, ensuring every borrower communication is compliant with data protection and RBI digital lending guidelines.
Beyond WhatsApp Business API, Pelocal supports Google RCS, Voice AI and WhatsApp Calling — giving lenders a multi-channel servicing stack that adapts to borrower device capability and network access, while keeping every interaction inside the same audit-friendly infrastructure. This ensures repayment reminders and account updates reach borrowers even where WhatsApp adoption or connectivity varies.
WhatsApp enforces messaging limits tied to a business's phone number quality rating and conversation-based pricing tiers, not a fixed 1,000-message cap. For high-volume lenders sending repayment reminders and servicing updates at scale, understanding these tiering rules — and how to maintain a high-quality rating — is critical for uninterrupted borrower communication. Pelocal manages this tiering and quality optimisation as part of its collaboration with your business.
Traditional collections rely on call centres and field agents, both of which carry high per-contact costs. By moving repayment reminders, payment collection and receipt delivery into a single WhatsApp thread, lenders reduce dependency on outbound calling for routine servicing, reserving human collections effort for genuinely at-risk accounts. This lowers cost-per-borrower while improving the borrower experience.
Compliance
The rules lenders work under, and how Pelocal handles each one.
The recovery agent's particulars must reach the borrower by email or SMS before the agent makes contact.
How Pelocal handles it
The lender configures the disclosures its templates carry, and the message log shows what was sent and when.
The Scale Based Regulation Master Direction bars undue harassment, naming “persistently bothering the borrowers at odd hours”.
How Pelocal handles it
Pelocal templates carry no coercive language, and the lender sets the send window each campaign runs in.
No contact before 8:00 a.m. or after 7:00 p.m. for recovery of overdue loans.
How Pelocal handles it
Send windows are configured per campaign and recorded against every message.
Notice in clear and plain language, consent that is specific and as easy to withdraw as to give, and use limited to the purpose consented to.
How Pelocal handles it
One consent state records the purpose a customer agreed to, and it travels with the record across all four channels.
The lender remains responsible for its service provider, whatever the extent of delegation.
How Pelocal handles it
Pelocal runs verification, WhatsApp template review, number migration and throughput in-house as a Meta Business Solution Provider, and hands the lender the audit trail.
Clause references are a guide to where each requirement sits, current as of the 2025 Directions, which repeal the 2022 Digital Lending Guidelines. They are not legal advice. Check each one against the RBI or government source before relying on it.
Other sectors
Nearby deployments
Reminders, statements and payments. One thread.
A payment reminder can sit unread in an SMS inbox for a week. Pelocal moves reminders, balances, statements and payments to the thread your customer reads, and reconciles every one.