Bring us the use case. We'll show you how it runs on WhatsApp, RCS or Voice AI.
This isn't a lead form. It's the fastest way to get a straight answer out of us.
Possibly already answered
If one of these covers it, you have saved yourself the wait for a reply.
Yes. Pelocal holds official Meta BSP status, which means WhatsApp Business Account provisioning, display-name verification, template review and throughput requests run through our direct Meta relationship rather than through a reseller.
Self-serve pricing is per transaction: 0.5% on UPI and 2% on other payment methods, with no platform subscription. Enterprise messaging deployments (RCS sender verification, Voice AI, dedicated throughput) are quoted against volume and channel mix.
Transactions captured before 3 PM on a working day settle the same day. Transactions after the cut-off settle on the next working day.
Your email address and mobile number, PAN and business details, and a bank account. After you enable payments we send a ₹1–5 penny-drop credit to verify the account, then issue your Merchant ID.
Consent state, purpose and retention are recorded against the conversation itself. Conversation and payment data is stored in India, and data-principal requests are handled through a documented process we can walk your compliance team through.
No. Pelocal sits on the messaging and collection layer and reads from your system of record. A guided rollout starts by mapping those systems before any template is submitted for review.
Yes. WhatsApp, RCS, Voice AI and WhatsApp Calling share one customer record and one consent state, so a conversation that starts as an RCS bill notice and ends as a voice call stays a single thread.
Hindi, English and Gujarati are already running in production, including code-mixed speech on voice. Additional regional languages follow the same template and review pipeline.