The WhatsApp Business API: customer service at scale

WhatsApp passed 1.5 billion monthly users last year, and in many markets it is the default way customers contact a business, whether the business has set anything up or not. In the US it is smaller but growing fast among immigrant communities, international travelers and anyone with family abroad, and businesses with customers in Latin America, Europe, India or the Middle East often find that half their support demand would move there given the chance.

Two products exist. The WhatsApp Business app, launched in January 2018, is free, runs on a single phone number and device, and gives a small business a profile, quick replies, labels and away messages. The WhatsApp Business API, opened in August 2018, has no app at all. It is a programmatic interface that you or a partner host, connected to your help desk, CRM, commerce platform or custom code. Access requires approval from WhatsApp, and most businesses go through an official Business Solution Provider such as Twilio, MessageBird, Infobip or Nexmo rather than hosting the client themselves.

Every decision about the API comes back to this distinction.

Session messages. When a customer messages you, a 24-hour window opens. Inside it, you can send free-form replies, including text, images, documents and location, at no per-message cost. This is the support use case: the customer starts, you respond, the conversation flows.

Template messages. To contact a customer outside that window, or to start a conversation, you must use a pre-approved template. Templates are submitted to WhatsApp with placeholders, such as "Your order {{1}} has shipped and should arrive by {{2}}," and reviewed before use. They are charged per message at a country-specific rate. In 2019 approved templates are limited to transactional and service content: order and shipping updates, appointment reminders, payment and account alerts, ticket updates, travel itineraries. Anything promotional is rejected.

Pricing varies widely: template messages run from under a cent in some markets to several cents in others, with the US toward the upper end of the range. Volume matters less than country mix when forecasting cost.

Before you send the first template to anyone, they must have agreed to receive WhatsApp messages from you, through a visible, active choice that names WhatsApp specifically. A checkbox at checkout, a toggle in an account page, a reply to an SMS or a tap in an in-app prompt all work. Burying it in terms of service does not.

This matters beyond compliance. WhatsApp assigns each business number a quality rating based on how often customers block or report it, and a falling rating reduces your messaging limits and can get the number restricted. Messaging people who did not clearly opt in is the fastest way to find that out.

Resist starting with notifications. The sequence that works is support first, then transactional templates, then the automation that joins them.

1. Route inbound conversations into the tool your team already uses. Most help desks, including Zendesk, Freshdesk and Intercom, have WhatsApp connectors through a solution provider. Agents see WhatsApp as another channel beside email and chat, with the same assignment, tags and reporting.
2. Write the greeting and the handoff. An automatic acknowledgment inside the 24-hour window, with expected response time, and a clear path to a person. Keep bots minimal for now: a menu of three or four common requests, with everything else to an agent.
3. Submit the first templates. Pick the three notifications customers most want: order confirmation, shipping update with tracking, and appointment or delivery reminder are the usual winners. Write them plainly, keep placeholders few, and expect approval in a few days with revisions if the wording reads as marketing.
4. Connect the triggers. The template fires from the event in your commerce, booking or ticketing system, through the provider's API. This is integration work and it is where most of the project time goes.
5. Measure the right things. First response time, resolution time, share of support volume moved from phone and email, template delivery and read rates, and the opt-in rate at each collection point.

For a mid-sized business the first phase usually looks like this: two to four weeks for provider onboarding and number verification, including business verification through Facebook Business Manager; one to three weeks to connect the help desk and go live for inbound; and another two to six weeks to build and approve templates and wire the triggers. Ongoing cost is the provider platform fee, commonly a few hundred to a few thousand dollars a month by volume, plus per-template charges that are small unless you are sending hundreds of thousands of notifications.

The number itself is a decision: a dedicated number that has never been on the WhatsApp app is simplest, and migrating an existing app number to the API is possible but one-way.

• Treating templates as a newsletter channel and getting every submission rejected.
• Messaging a customer list that opted in to email, not WhatsApp.
• Answering outside the 24-hour window with a template that reads like a sales pitch.
• Launching with a bot and no agent handoff, so customers loop and block.
• Forgetting business hours: a session message at 2 a.m. still expects an answer by morning.
• Building the integration on the app instead of the API and hitting the single-device wall.

We treat WhatsApp as a service and technology channel that has to fit the brand voice, the support workflow and the systems behind it. Discover: we map where customers contact you today, which conversations and notifications would move to WhatsApp, and how opt-in can be collected at each touchpoint. Plan: we choose the solution provider and help desk connection, design the conversation flows and handoffs, and draft templates that will pass review. Build: we complete verification, integrate the help desk and the event triggers in your commerce or booking systems, and launch inbound before outbound. Improve: we track response times, template read rates and quality rating, and expand automation where the data supports it. Brand, growth, web and technology stay connected so the channel sounds like you and works with what you already run.

A representative engagement is described in our WhatsApp work, where a business with high inbound support volume moved conversations onto the API through its existing help desk, then added transactional notifications triggered from its order system, with opt-in collected at checkout and in account settings. The lasting result was a channel the support team ran daily with a documented template library and a clean quality rating.