WhatsApp Business API Programs for Travel and Regulated Teams

Since July 2025 WhatsApp template messages are priced per message rather than per twenty-four-hour conversation, and utility templates sent inside an open customer service window are not billed at all. That change decides most of the architecture. A travel brand that moves booking confirmation, check-in reminder and disruption notice into utility templates, and lets those templates open the service window, pays for a small fraction of the volume a brand running the same content as marketing pays for. Almost every WhatsApp programme we inherit is built the expensive way, and the rebuild pays for itself before the second quarter. The economics we model before quoting: We take twelve months of your message volume by type and price it three ways: as marketing templates, as utility templates, and as utility templates that successfully open a service window into which the follow-up lands free. The gap between the first and third number is the business case, and where it is small we say the channel is not worth the integration. Meta re-categorises templates, and a utility template carrying one promotional sentence gets reclassified and billed as marketing, so the copy discipline is the cost control. That is a writing job, not a procurement job. Quality rating and messaging limits: A new sender starts limited and climbs through tiers as quality holds. Quality rating is driven by blocks and reports, and a red rating drops your limits at exactly the moment you need them. We treat the first ninety days as a rating build: fewer templates, tighter audiences, and no marketing template sent before the utility programme has established that your number sends things worth opening. Brands that launch with a promotional broadcast to a cold file usually spend the following quarter recovering. What we build: Cloud API through 360dialog, Twilio or Infobip, chosen against your existing infrastructure rather than our preference. A template library with categorisation reasoning documented per template, because the appeal argument you may need later has to have existed at authoring time. Opt-in captured off WhatsApp with explicit phrasing naming WhatsApp specifically, since consent to email or SMS is not consent here. Flows where structured collection replaces a form, which for pre-arrival details on a roaming phone is the entire point. Webhook routing into your CRM or service desk so an inbound reply reaches a human inside the window rather than after it has closed. Regulated content: For medtech and pharma clients, template bodies carry no diagnosis, no therapy detail, and nothing that would constitute health data in transit. Any inbound message containing what could be an adverse event is routed to pharmacovigilance on a defined clock, with the routing tested and evidenced before launch. Meta's own commerce and healthcare policies rule out more than clients expect, and we map that against your regulatory affairs team's list in week one, not at approval. Markets where we advise against it: WhatsApp penetration is not uniform and neither is the willingness to be marketed to inside it. In Brazil, India and much of Southeast Asia this channel outperforms email outright. In Czechia it sits behind Messenger and SMS for consumer reach, and we will say so rather than build you a channel with a domestic audience of a few thousand. In the United States it is a support channel for specific communities, not a broadcast surface. Out of scope: Customer service staffing on the inbound path. Conversational AI agents. Catalogue and in-chat commerce build. Negotiation of your BSP rate card, which we will read and challenge but not sign. Who this is not for: Anyone looking for a cheaper newsletter. WhatsApp punishes broadcast with blocks, and blocks cost you the operational messaging you actually needed the channel for.