Connecting a website to WhatsApp can cost almost nothing—or become a substantial software-integration project. The price depends on what must happen after someone clicks: open a conversation, capture a qualified enquiry, assign it to a team, or connect the conversation to bookings, payments and customer records.
For most small businesses, start with a clear WhatsApp contact button and a reliable way to respond. Do not pay for an API integration until you can explain the operational problem it will solve.
These are illustrative Nigerian project-planning allowances, not surveyed market averages or fixed quotations. Existing website quality, software licences, Meta message charges and ongoing support affect the actual price.
| What you need | One-time planning allowance | Sensible outcome |
|---|---|---|
| Click-to-WhatsApp on an existing website | ₦0–₦100,000 | Visible, tested contact links and useful prefilled context |
| Structured enquiry form plus WhatsApp handoff | ₦150,000–₦450,000 | Enquiry stored before chat opens; owner receives usable details |
| Shared inbox and WhatsApp Business Platform integration | ₦450,000–₦1.5 million | Team assignment, consent-aware messaging, basic monitoring |
| Custom WhatsApp, CRM, booking or payment workflow | ₦1.5 million–₦4 million+ | Business records, reliable events, recovery, testing and handoff |
A new website, complex CRM, chatbot training, software subscriptions and message usage may need separate budgets. The ₦450,000+ projects are generally the ones where WhatsApp must become part of a dependable business process—not merely a button.
First decide what “WhatsApp integration” means
1. A click-to-chat link
WhatsApp’s official click-to-chat guidance documents links using wa.me and optional prefilled messages. A website can use these on service pages, product pages and contact sections.
This is often sufficient for a solo consultant, photographer, local contractor or small shop. The page should tell visitors what they are enquiring about, what information to include and when to expect a reply.
Important limitation: A website click does not prove the visitor sent a message. They may open WhatsApp and abandon the conversation. Treat a click as intent to contact, not a confirmed lead.
2. A form that captures the enquiry before WhatsApp opens
Suppose a property business needs location, budget, property type and preferred viewing date. A generic “Chat with us” button makes the customer repeat those details to a salesperson.
A short website form can capture the request, save a reference and then offer a WhatsApp conversation. The business retains a recoverable enquiry even if the customer does not complete the chat.
This requires thoughtful form design, privacy notice, spam protection and delivery testing. If your existing form says “sent” but staff receive nothing, diagnose the missing-enquiry failure before adding another messaging channel.
3. A shared inbox using the WhatsApp Business Platform
When several employees respond to one business number, the real purchase is no longer a website button. It is a system for assigning conversations, controlling access and keeping the customer relationship with the business.
You may use an established inbox provider rather than building your own. The developer’s job is to configure the connection, map website enquiries, define assignment rules, train staff and prove that the workflow works.
The WhatsApp Business Platform documentation is the starting point for platform capabilities and requirements. The ordinary WhatsApp Business app and the API-based platform are not interchangeable; confirm number and provider arrangements before migrating a live customer channel.
4. Custom integration with bookings, payments or a CRM
Custom engineering is justified when a WhatsApp conversation must create or update a record elsewhere. For example, a clinic could receive a consultation enquiry, check appointment availability, record the booking and send an appropriate confirmation.
The booking system, not the chat transcript, should remain the authoritative record of the appointment. The same principle applies to orders and payments.
If the business already uses a CRM, read the separate website-to-CRM integration cost guide. That article covers CRM procurement generally; this one is about choosing the right WhatsApp channel and integration depth.
Why a cheap button can become an expensive lead problem
Imagine a professional-services firm receiving 25 website-to-WhatsApp clicks in a day. The analytics dashboard reports 25 clicks. The owner assumes 25 enquiries arrived.
But some visitors never sent a message, others sent incomplete requests, and a few received no response because the responsible staff member was away.
That is a hypothetical example, not a conversion benchmark. It shows why measurement must separate:
- Website button clicks.
- Confirmed form submissions or received messages.
- Qualified enquiries.
- Conversations assigned and answered.
- Bookings or sales actually completed.
Google’s GA4 event guidance recommends generate_lead for an acquired lead, such as a form submission. Do not label every WhatsApp-button click as a completed lead, and do not send personal chat contents into analytics.
If your website already attracts visitors but fails to produce qualified enquiries, diagnose the conversion journey before paying for a redesign.
What changes the quotation?
Volume and staff roles. One owner answering manually is different from several agents across locations with assignment, escalation and reporting.
Data ownership. Decide whether your website, CRM, booking system or inbox is the source of truth. A staff member leaving should not take the only copy of customer enquiries with them.
Message and software charges. A simple wa.me link is not an API message service. API implementations may involve Meta charges, provider subscriptions, template rules and other operating costs. Check Meta’s current WhatsApp pricing documentation and request a monthly estimate by message category and customer country. Do not accept an unqualified promise of “unlimited free messages.”
Consent and privacy. A person opening a WhatsApp chat has not necessarily agreed to promotional broadcasts. Define what data is collected, why it is stored, who can access it and how long it is retained. Nigerian businesses should assess their obligations under the Nigeria Data Protection Act and NDPC guidance.
Reliability. Ask what happens if an inbox connection expires, an API request fails, a staff account is disabled or a customer sends the same request twice. A useful integration should preserve the enquiry and show the team what needs attention.
Payment state. If a booking or order involves payment, a screenshot or “I’ve paid” message must not mark it as paid. Paystack’s webhook guidance explains server-to-server notifications and signature verification; its transaction verification documentation covers checking the actual payment status. Prevent duplicate fulfilment if a notification is retried.
Which approach should you buy?
| Business situation | Better first purchase |
|---|---|
| One person answers occasional questions | Click-to-chat, good service copy and response expectations |
| Leads arrive without enough information | Short website intake form and recorded enquiry |
| Several people share customer conversations | Supported shared inbox with ownership and assignment rules |
| WhatsApp must update bookings, orders, CRM or payments | Scoped API integration with tests and monitoring |
Do not start with an AI chatbot because it sounds more advanced. If staff cannot fulfil the promise, identify the correct booking, or recover a lost enquiry, automated replies will not fix the underlying operation.
For appointment-heavy businesses, the booking website cost guide explains when real availability, deposits and staff scheduling should live outside the chat.
Seven acceptance tests before you pay the final balance
Ask your developer to demonstrate these on mobile and desktop:
- A visitor can identify the right WhatsApp action from the relevant service page.
- The correct business-owned number opens, with accurate context and no broken link.
- A click is measured as a click—not falsely counted as a received message.
- If a form is included, its submission is saved and can be recovered even when messaging fails.
- A new enquiry reaches the correct staff member, and an absent employee does not strand it.
- Duplicate submissions and failed connections have a documented handling procedure.
- The business controls the website, messaging account or provider contract, credentials, records and handoff documentation.
If bookings or payments are included, add real end-to-end tests for cancellation, failed payment, duplicate events and staff access changes. A demo of one successful chat is not enough.
What to send a developer for an accurate quote
Provide your website URL, what customers currently ask on WhatsApp, how many staff answer, whether you already use a CRM or booking tool, and the one outcome you want to improve: qualified enquiries, appointment confirmations, order handling or response time.
Ask for separate figures for setup, software subscriptions, message usage and maintenance, plus a written list of exclusions. A developer should be able to explain why a native tool is insufficient before recommending a custom system.
If you need the website and the lead-handling workflow designed together, see my web design service. For a more complex custom booking or customer application, see MVP and product development. You can send me the existing website and the broken handoff for a scoped recommendation rather than paying to rebuild something that only needs a better connection.
