How to Add WhatsApp Integration to a Mobile App
Three levels of WhatsApp integration for a mobile app
The difference between the levels is who sends the message and where the conversation lives. At level one, the customer sends the first message from their own WhatsApp and the conversation lives on your business phone. At level two, your backend sends and receives messages through Meta's API and the conversation lives in your system. Level three uses the same API for a narrow purpose: delivering one-time passcodes.
| Level | What it does | What you need | Effort | Ongoing cost |
|---|---|---|---|---|
| 1. Click-to-chat | A button in the app opens WhatsApp with your number and a pre-filled message | A WhatsApp Business App number | Hours | None |
| 2. Business Platform (Cloud API) | Your backend sends approved templates (order updates, receipts, reminders) and receives replies | Meta Business verification, dedicated number, approved templates, backend integration | Weeks | Per-message or per-conversation fees in USD; optional provider subscription |
| 3. OTP and login | Authentication codes delivered by WhatsApp instead of, or before, SMS | Same as level 2 with authentication templates | Days on top of level 2 | Per-message fees, often below SMS |
Most apps should start at level one immediately, then move to level two when message volume or the need for automated notifications justifies verification and integration work.
Level 1: click-to-chat links with context
A click-to-chat link opens WhatsApp on the user's phone with your business number selected and, optionally, a pre-filled message. From inside an app, this is a single button, and it becomes far more useful when the message carries context: "Hello, I need help with order #4471 placed on 12 March." The customer sends it with one tap, and your support staff see exactly what it is about. Practical design points:
- Route by purpose. Sales enquiries to one number, order support to another, complaints to a third, each with its own pre-filled message.
- Include the identifiers your staff will search for. Order number, booking reference, account phone.
- Handle the missing-app case. If WhatsApp is not installed, fall back to a phone call or an in-app form rather than failing silently.
- Track taps. Log which screens generate WhatsApp contacts; they show where the app is failing to answer questions on its own.
- Use a business number, not a founder's personal number. Numbers embedded in an app are hard to change later when staff leave.
For a small business with one or two support staff, this level is often all that is needed for months.
Level 2: the WhatsApp Business Platform for notifications and conversations
The WhatsApp Business Platform, also called the Cloud API, lets your backend send messages to customers and receive their replies programmatically. It is distinct from the free WhatsApp Business App on a phone. It is how an app sends "Your order has been dispatched" to a customer's WhatsApp automatically, delivers a receipt, reminds a patient of tomorrow's appointment, or lets a customer reply and have that reply appear in your support system. What Meta requires, as of 2026 (verify current requirements in Meta's documentation):
- A Meta Business account and business verification. Verification typically needs your CAC registration documents and proof of the business's name, address and phone. It can take days to weeks.
- A dedicated phone number registered to the Platform, with a display name subject to Meta's approval. Historically a number could be used on either the WhatsApp Business App or the Platform, not both at once; Meta has been introducing options for coexistence, so check the current position before choosing a number.
- Message templates. Any message you initiate outside an active customer-service window must use a template Meta has approved, in a category such as utility (order updates), authentication (OTPs) or marketing. Templates are reviewed for content and formatting.
- The customer-service window. When a customer messages you, you may reply freely for a period (historically 24 hours) without a template. Outside that window, only templates.
- Pricing. Meta charges per message or per conversation depending on category and has changed its pricing model over time, priced in US dollars and varying by country. Check current rates for Nigeria.
Direct Cloud API or a Business Solution Provider?
You can integrate directly with Meta's Cloud API or go through a Business Solution Provider (BSP), a company Meta authorises to resell access with extra tooling.
| Route | Pros | Cons | Fits when |
|---|---|---|---|
| Direct Cloud API | No middleman fees; full control; Meta's own documentation | You build the inbox, template management and analytics yourself | You have a backend team and clear, limited use cases |
| BSP or messaging platform | Shared inbox, template tools, analytics, support, often local payment in naira | Subscription or per-message markup in addition to Meta fees | You need agent tooling quickly or lack backend capacity |
The backend integration
Whichever route, your backend needs: a service that sends template messages triggered by business events (order paid, dispatched, appointment tomorrow); a webhook endpoint that receives incoming messages and delivery statuses; storage of conversations against customer records; a way for support staff to see and reply (your own admin screen, a BSP inbox, or your CRM); and logging of costs per message. If you already have a push notification service, WhatsApp becomes another channel it can select, with rules for which messages go where.
Level 3: WhatsApp as an OTP and login channel
Delivering one-time passcodes by WhatsApp uses authentication templates on the Business Platform. For Nigerian apps this matters because SMS delivery can be slow or blocked, SMS costs per message add up, and many customers read WhatsApp faster than SMS. The typical pattern sends the code by WhatsApp first and falls back to SMS if delivery is not confirmed within a short window, or offers the customer a choice. Points to design:
- Authentication templates have a fixed structure and may support a one-tap autofill or copy-code button; check current template options.
- Verify the phone number is a WhatsApp number before sending; the API reports delivery failures you must handle.
- Keep SMS as a fallback for customers without WhatsApp or with WhatsApp offline.
- Never send the same code through both channels at once without a reason; it confuses users and doubles cost.
Opt-in, consent and the Nigeria Data Protection Act
Meta requires that businesses obtain opt-in before sending messages to a customer on WhatsApp, and that the opt-in makes clear the business name and what kinds of messages will be sent. In an app, that means a clear checkbox or setting at sign-up or checkout, stored with a timestamp, and honoured when the customer withdraws it. The Nigeria Data Protection Act 2023 adds its own obligations: WhatsApp messages are personal data processing, marketing messages need a lawful basis and easy opt-out, and conversation data stored on your backend needs security, retention limits and a stated purpose in your privacy notice. Meta's infrastructure is outside Nigeria, which raises cross-border transfer considerations. Confirm your specific obligations with the NDPC's current guidance or a qualified adviser.
How to add WhatsApp integration to a mobile app: step by step
- Add click-to-chat now. Business number, purpose-based routing, context in the pre-filled message, fallback for no WhatsApp, tap tracking.
- List the messages you would automate. For each: trigger, category (utility, authentication, marketing), template text, and whether it needs a reply path.
- Decide direct API or BSP. Based on backend capacity, need for an agent inbox, and budget.
- Start Meta business verification early. Gather CAC documents and business details; it runs in parallel with development.
- Choose and register the number. A dedicated business number, with the display name Meta will show.
- Submit templates for approval and expect a round of revisions.
- Build the backend service. Sending on events, webhook for replies and statuses, conversation storage, agent view or CRM link, cost logging, and channel rules alongside push and SMS.
- Add opt-in and preferences in the app. Clear consent capture, stored and honoured.
- Test with real numbers across networks (MTN, Airtel, Glo, 9mobile) and on WhatsApp-offline phones to exercise fallbacks.
- Launch with utility messages first, measure delivery, read and reply rates, and cost per message, then consider marketing templates.
What changes for WhatsApp integration in Nigeria
- WhatsApp is the expected channel. Customers assume they can reach you there. An app without a WhatsApp path feels closed.
- Personal numbers are everywhere. Many businesses run on a founder's or a staff member's personal number. Moving to a dedicated business number before embedding it in an app avoids a painful migration later.
- Verification documents. Meta business verification relies on documents that match your registered business name; inconsistent names across CAC, bank and utility bills cause delays.
- USD pricing, naira revenue. Platform message fees are in dollars and change with the exchange rate. Model cost per order or per booking and set monthly caps.
- Data and connectivity. WhatsApp messages reach customers on low data and weak signal more reliably than app push, which is part of why they work as fallbacks.
- Trust. A verified business name on WhatsApp reassures customers who worry about scams; a message from an unnamed number does the opposite.
- Staff workflows. Replies will come in at all hours; decide who answers, from which tool, and how conversations are recorded before volume arrives.
Example (hypothetical): a Calabar hotel booking app connects WhatsApp
Example (hypothetical): a hotel in Calabar has a booking app where guests reserve rooms, but confirmations go out by email that guests rarely open, and the front desk answers the same questions on WhatsApp all day from a receptionist's personal phone. The hotel adds a click-to-chat button on the booking confirmation screen that opens WhatsApp to a new dedicated business number with the booking reference pre-filled, and a separate "Ask about events" button routed to the events manager. Meta business verification starts the same week using the hotel's CAC documents. Templates are drafted for booking confirmation, check-in reminder the day before, and a check-out receipt, all utility category. Once approved, the backend sends each template on booking events through the Cloud API and receives replies into a simple admin screen the front desk uses on a shared tablet. Guests opt in to WhatsApp messages at booking with a clear note of what they will receive. Confirmation open rates are visible for the first time, the receptionist's personal phone leaves the workflow, and the hotel sets a monthly cap on message spend in dollars. The figures are illustrative and not client results.
How much does WhatsApp integration cost?
Indicative 2026 ranges are shown below; actual quotes vary with scope, vendor and exchange rate. Level one is close to free; level two is a backend project whose cost depends on how many message types and reply workflows you need.
| Cost item | Indicative 2026 range | Notes |
|---|---|---|
| Click-to-chat buttons with context and tracking (both platforms) | ₦30,000–₦150,000 | Level one |
| Meta business verification support and number setup | ₦30,000–₦150,000 | Mostly document preparation and follow-up |
| Template design and approval cycles | ₦30,000–₦150,000 | Per batch of templates |
| Backend sending service and event triggers | ₦150,000–₦700,000 | Utility messages on business events |
| Webhook inbox, conversation storage and agent view | ₦200,000–₦1,000,000 | Or a BSP subscription instead |
| WhatsApp OTP with SMS fallback | ₦100,000–₦400,000 | On top of the Platform integration |
| Typical total, Platform integration | ₦500,000–₦2,500,000 | Higher end includes agent tooling and CRM links |
Recurring costs, separate from the build: Meta's per-message or per-conversation fees in US dollars, varying by category and volume; a BSP or messaging platform subscription if you use one, often priced in USD with some Nigerian providers billing in naira; SMS fallback messages; and maintenance of templates and API changes within the app's normal 15–25 percent per year budget. When comparing quotations, ask whether verification support, template approval, the webhook inbox and opt-in capture are included, and ask for an estimate of monthly Meta fees at your message volume. A quote for "WhatsApp API integration" that covers only sending has left out half the work.
Mistakes to avoid
- Embedding a personal number. Staff change; numbers in published apps are hard to change.
- Starting verification late. It gates everything at level two and can take weeks.
- Sending without opt-in. Meta can restrict your number, and it breaches data protection expectations.
- Marketing templates first. Quality ratings suffer and customers block you; begin with utility messages people want.
- No reply handling. Customers will reply to notifications; if nobody sees the replies, trust collapses.
- Ignoring the fallback. Customers without WhatsApp or offline need SMS or push for critical messages.
- Uncapped spend. Dollar fees on a viral promotion can exceed a month's budget in a day.
- Treating the Business App and the Platform as the same thing. They differ in capability, number rules and cost; decide which you are using.
Conclusion
WhatsApp integration for a mobile app comes in three levels. Add click-to-chat with context immediately; it costs almost nothing and meets customers where they are. Move to the WhatsApp Business Platform when you need automated confirmations, receipts, reminders and replies handled in your systems, and plan for Meta verification, template approval, opt-in capture and dollar-denominated fees. Use WhatsApp for OTPs with SMS fallback once the Platform is in place. In Nigeria, a dedicated verified business number, clear consent and a reply workflow matter as much as the code. If your app needs WhatsApp confirmations, reminders and support conversations wired into your backend and your team's workflow, Linestech integrates the WhatsApp Business Platform into Nigerian mobile apps and can guide the verification, templates and channel rules.
Frequently asked questions
Can I use my existing WhatsApp Business App number for the API?
Historically a number could be registered on either the WhatsApp Business App or the Business Platform, not both at the same time, and moving it to the Platform meant it stopped working in the phone app. Meta has been introducing ways to use both; check the current position in Meta's documentation before you decide, and consider a dedicated number for the app.
Do I need Meta business verification to send WhatsApp messages from my app?
For the Business Platform, yes; verification enables sending at meaningful volume and a verified display name. Click-to-chat links need no verification because the customer initiates the conversation with your ordinary WhatsApp Business App number.
How much does each WhatsApp message cost from the API?
Meta charges per message or per conversation depending on category, in US dollars, with rates that vary by country and have changed over time. Check Meta's current pricing for Nigeria, add any provider markup, and convert at a buffered exchange rate when budgeting.
Is WhatsApp OTP better than SMS OTP in Nigeria?
Often faster and cheaper per message, with higher read rates for customers active on WhatsApp, but it requires the Platform integration and does not reach customers without WhatsApp or with it offline. Most apps use WhatsApp first with SMS fallback, or let the user choose.
Can customers reply to automated WhatsApp messages from my app?
Yes, on the Business Platform. Replies arrive at your webhook, and you can respond freely within the customer-service window. You need somewhere for staff to see and answer those replies, whether your own admin screen, a provider's inbox or your CRM.
Do I need a developer to add a WhatsApp button to my app?
For click-to-chat, a developer adds it in a few hours as part of any app update. The Business Platform integration is a backend project that needs a developer and a few weeks, plus Meta's verification and template approval timelines.
Sources and further reading
Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.
