WhatsApp Business API integration for your CRM, chatbot and notifications

The free WhatsApp Business app is enough for a small team answering chats on one or two phones. You need the API when WhatsApp must talk to your software: messages sent automatically when a booking is confirmed or a payment is due, a chatbot that answers outside office hours, several staff working the same number from a computer, or every conversation saved against the customer in your CRM.

If all you want is broadcast campaigns and a shared inbox, a provider's ready-made dashboard will usually be cheaper than a custom build, and I will tell you so. Custom WhatsApp Business API integration makes sense when the messages depend on data in your own system, when the chatbot needs to look things up for the customer, or when staff should work from the admin panel they already use instead of a separate tool.

There are two ways in. Meta's WhatsApp Cloud API is hosted by Meta and you connect to it directly: no middleman fee, full control, and you pay Meta only for the messages it charges for. Business Solution Providers (BSPs) such as Twilio, Gupshup, WATI, Interakt or AiSensy sit in between and add their own dashboard, campaign tools, support and onboarding help, usually for a monthly fee or a markup on messages.

For a business with its own CRM or software, I usually recommend the Cloud API directly, which is what the travel agency CRM uses. A provider is the better choice if your team wants their dashboard and campaign tools as well as the integration, or if you already pay for one and are happy with it. In that case I build against the provider's API instead, and the rest of the work is the same.

WhatsApp is strict about how businesses message people, and the rules decide what your integration can do. I design around them from the start:

• The 24-hour customer service window. When a customer messages you, a window opens for 24 hours, and every new message from them restarts it. Inside it you can reply freely with text, media and interactive menus. Outside it, you can only send an approved template.
• Template approval. Templates are submitted to Meta in a category (marketing, utility or authentication) and reviewed before use. Approval is often quick, but templates are rejected for vague wording or a category that does not match the content, so I write them to fit the rules.
• Opt-in. You must have a customer's permission before you message them first. I add a clear opt-in to your forms or booking flow, store when and how it was given, and honour opt-outs automatically.
• Quality and messaging limits. New numbers can start only a limited number of business-initiated conversations a day. The limit rises as you send more with good quality, and falls if many people block or report you, so careful templates protect your number.

The travel agency's CRM manages customers and their family members, trips, tour packages, departures, travelers, vendors, documents and payments in one Laravel admin panel. WhatsApp is connected to it through Meta's Cloud API, which turns the CRM into a WhatsApp CRM for the agency's staff.

• Interactive menu. Customers get a menu with reply buttons and lists, so common requests are answered without typing or waiting for staff.
• Templates and quick replies. Approved message templates and quick replies for the messages the agency sends again and again.
• Staff takeover. A staff member can step in and reply to a customer directly from the admin panel, and the automated flow steps aside for that conversation.
• Around the chat. The CRM also runs daily reminders, browser push notifications and festival greetings, with role-based permissions deciding who sees which conversations.

WhatsApp API integration in PHP is mostly about webhooks: Meta sends every incoming message and every status update (sent, delivered, read, failed) to an HTTPS endpoint on your server. Getting that endpoint right is what separates a chatbot that works in a demo from one that works for a year. For WhatsApp Business API integration in Laravel, I build it like this:

• The webhook verifies Meta's signature on every request and rejects anything unsigned
• Each message is stored by its WhatsApp message ID, so a webhook Meta delivers twice is processed once
• The endpoint replies to Meta at once and hands the real work to a queued job, so slow lookups never cause timeouts and resends
• Outgoing sends are retried with backoff on temporary errors and flagged for staff on permanent ones, such as a number not on WhatsApp
• Media such as tickets, invoices or ID copies is downloaded from Meta and stored on your server with the conversation
• Access tokens and secrets live in server configuration, never in code or the browser

A WhatsApp chatbot for business does not have to be AI. Menus, buttons and simple rules answer most common questions reliably, cost nothing per conversation beyond Meta's charges, and never say something you did not approve. That is how the travel agency's bot works, with staff one click away.

AI is worth adding when customers ask open questions that menus cannot cover. Then an AI step can answer from your own content or draft a reply for staff, as described on my ChatGPT and OpenAI integration and AI automation pages, with the same takeover so a person can always step in. If you use Perfex, see Perfex CRM customization for WhatsApp inside Perfex.

There are two separate costs. Meta charges per message for templates you send, priced by category and by the recipient's country, while replies inside the 24-hour customer service window are not charged at the time of writing. Rates and rules change, so check Meta's WhatsApp pricing page (opens in a new tab) for current figures. A BSP adds its own fees on top. The build is a fixed quote from me after a short call or written brief.

WhatsApp API integration cost in India, as anywhere, depends on how many templates and flows the chatbot needs, whether it must look up data in your CRM, whether staff need a shared inbox in your admin panel, how many other systems are involved, and whether you go direct to Meta or through a provider.