WhatsApp Bot &
Business API Service
Turn WhatsApp into your busiest sales and support channel. We build the bot flows and run the platform underneath — OTP verification, approved templates, delivery receipts and inbound routing, all on the official Meta Cloud API.
Typical outcomes across our deployments and published WhatsApp benchmarks. Your results depend on message volume, category and how the flows are designed.
Your customers already live on WhatsApp. Meet them there.
Emails go unread and calls go unanswered, but a WhatsApp message gets opened within minutes. A well-built bot uses that attention properly — it replies instantly, asks the right questions, and hands your team a warm, qualified conversation instead of a cold form submission.
What the Platform Does
Every build is assembled from these modules and shaped around your actual conversations — never a generic template.
WhatsApp OTP Verification
Sign users in over WhatsApp instead of SMS. Codes are hashed at rest, never logged, single-use, and rate limited per mobile and per IP — your application never sees or stores the code itself.
Approved Template Messaging
Send Meta-approved utility and authentication templates with variables: payment confirmations, renewal reminders, appointment alerts, order updates.
Service-Window Conversations
Free-form replies inside the 24-hour customer service window, with the window tracked per conversation and enforced before a call ever reaches Meta.
Delivery & Read Tracking
Every message moves through queued → sent → delivered → read, each transition timestamped and appended to an audit log you can query by message id.
Inbound Routing & Bot Flows
Incoming messages are captured, matched to a conversation, and answered by your flows — with a clean handover to a human agent when the bot reaches its limit.
Webhooks Into Your App
Delivery receipts and inbound messages are POSTed to your endpoint with an HMAC-signed header, retried with backoff, and logged attempt by attempt. No polling.
Operator Admin Console
A full admin panel: clients and credentials, WhatsApp accounts and templates, message log, queue depth, API request log, webhook events and an audit trail.
Usage & Quota Reporting
Per-client usage endpoints and dashboards so you can see volume by channel, watch quotas, and attribute conversation cost accurately.
We don't resell someone else's chatbot tool.
Dev-Shree runs its own multi-tenant communication platform, written in core PHP 8 against the Meta WhatsApp Business Cloud API. Your application authenticates once and calls a handful of REST endpoints — it never sees a Graph API URL, a phone number id or a Meta access token.
Because we own the platform, we can change how it behaves for you. That is the difference between a feature request and a support ticket that goes nowhere.
-
POST
/api/v1/whatsapp/send-otpSend a one-time code over WhatsApp -
POST
/api/v1/whatsapp/verify-otpVerify the code the user typed -
POST
/api/v1/whatsapp/send-templateSend an approved template with variables -
POST
/api/v1/whatsapp/send-textFree-form text inside the service window -
GET
/api/v1/whatsapp/message/{id}Full record and status history -
GET
/api/v1/whatsapp/messagesSearch and page through message history -
GET
/api/v1/whatsapp/templatesList approved templates -
GET
/api/v1/usageVolume and quota by channel
Each transition is timestamped and appended to an audit log you can query by message id.
The Guarantees Underneath
Messaging that touches money, health records or logins has to behave correctly on its worst day, not its best one.
No duplicate sends
Every send endpoint accepts an Idempotency-Key. A retried request replays the original response instead of sending a second message.
Survives provider outages
Sends are queued, never inline. A Meta outage delays delivery rather than failing your API call, and the worker retries with exponential backoff and jitter.
Verified webhooks
Meta callbacks are HMAC-SHA256 verified against the raw body before a single byte is trusted, and redeliveries are deduplicated on a deterministic event key.
Secrets encrypted at rest
WhatsApp credentials are AES-256-GCM encrypted, API secrets are hashed, and tokens are stored as SHA-256. Logs pass through a secret redactor.
Strict tenant isolation
Every query is scoped by client id and public identifiers are ULIDs, not sequential integers — so one application can never read another's messages.
Ordering that holds
Status never moves backwards. A late delivered callback cannot undo read, which matters because Meta does deliver callbacks out of order.
Built Around Your Industry
The flows that matter differ by sector. Here is where we usually start.
Finance & FinTech
WhatsApp OTP login, SIP and EMI reminders, payment confirmations, statement delivery and KYC document nudges.
Healthcare & Clinics
Appointment booking and reminders, report-ready alerts, prescription refill requests and follow-up scheduling.
Retail & Ecommerce
Catalogue browsing in chat, order confirmation, COD verification, dispatch and delivery updates, returns.
Education
Admission enquiry capture, fee reminders to parents, timetable changes and result notifications.
Real Estate
Enquiry qualification, brochure delivery, site-visit scheduling and post-visit follow-up.
Logistics
Shipment tracking on demand, delivery slot confirmation and proof-of-delivery messages.
NGOs & Communities
Membership verification by OTP, donation links, event RSVPs and volunteer coordination.
Manufacturing & B2B
Dealer order updates, dispatch notifications, service requests and field-team escalations.
From Kick-off to Go-Live
A clear, staged rollout — you always know what is happening and what we need from you next.
Discovery & Flow Design
We map the conversations your team already has, then design the bot flows, template copy, fallbacks and the point at which a human takes over.
Meta Business Verification
We guide you through Meta business verification, WhatsApp Business Account setup, display-name approval and the permanent system-user token.
Templates & Integration
We write and submit your message templates for approval, then connect the platform to your CRM, ERP, calendar or payment gateway.
Sandbox Testing
Everything is tested against a sandbox provider first, so no test run can reach Meta, send a real message or bill a conversation.
Launch & Optimise
Controlled go-live on your verified number, agent training on the console, then monthly transcript reviews to close the gaps the bot missed.
Connects to what you already run
If it has an API, we can wire WhatsApp into it. These are the ones we integrate most often.
One platform, more channels later
WhatsApp is fully implemented today. SMS, email and push are built as provider interfaces, so adding a channel later means one new class — not a rebuild.
Choose the Scope That Fits
Each package is a fixed-scope build quoted after a short discovery call. Meta's per-conversation charges are billed to you directly by Meta, at cost.
Starter
A first WhatsApp presence — automated replies and lead capture
- Official WhatsApp Business API onboarding
- Meta business verification support
- Up to 10 conversation flows
- FAQ automation and auto-replies
- WhatsApp OTP verification
- Lead capture to email or Google Sheet
- Shared team inbox (2 agents)
- 30 days post-launch support
Growth
Teams that need WhatsApp wired into the systems they already run
- Everything in Starter
- Up to 30 conversation flows
- Full API access with SDK and cURL examples
- CRM / ERP two-way integration
- Approved template library and variables
- Delivery, read and failure webhooks
- Catalogue, order and payment-link flows
- Live agent handover (10 agents)
- Usage dashboard and reporting
- 90 days support and optimisation
Enterprise
Multi-application, multi-branch and high-volume operations
- Everything in Growth
- Multi-tenant deployment — several apps, one platform
- Unlimited flows, templates and agents
- Per-tenant WhatsApp numbers and senders
- Dedicated instance or on-premise install
- Custom rate limits and quotas
- Role-based admin access and audit logs
- SLA-backed priority support
Questions We Get Asked
Yes. The platform talks to the Meta WhatsApp Business Cloud API and nothing else. That means a verified business profile, eligibility for the green tick, and no risk of the number being banned — unlike unofficial tools that automate the consumer WhatsApp app and routinely get business numbers blocked.
No. We built and run our own communication platform in core PHP 8 — queue, webhook verification, OTP handling, admin console and all. That is why we can change behaviour for you rather than telling you a SaaS vendor does not support it.
Yes. Your application authenticates with a client id, API key and secret — bearer token or HMAC signature — and calls a handful of REST endpoints. It never sees a Graph API URL, a phone number id or a Meta access token. We ship a single-file PHP SDK, runnable integration examples and cURL examples for every endpoint.
A Starter build is typically live in 2–3 weeks. Growth builds with CRM integration usually take 4–6 weeks. The main variable is Meta business verification, which moves at the speed your documents are ready.
Meta bills per conversation, and the rate depends on the category — marketing, utility, authentication or service — and the country. We set billing up inside your own Meta account so you pay Meta directly at cost, with no markup from us.
Yes, provided it is not currently active on the WhatsApp consumer or Business app. We can migrate an existing number, or provision a new one if you would rather keep the two separate.
Nothing breaks on your side. Sends are queued rather than dispatched inline, so your API call still succeeds and the worker retries with exponential backoff once Meta recovers. A message Meta has already accepted is never sent twice, even if the worker died before recording success.
No. Every flow has an escape hatch. If the bot cannot help, or the customer asks for a person, the conversation moves to your team inbox with the full history attached and the remaining service window visible to the agent.
See Your Bot Before You Commit
Book a free 30-minute session. We'll map two or three of your highest-volume conversations and show you exactly how they would run on WhatsApp — no obligation.