Digital Marketing

WhatsApp Business API for small business: setup, costs, providers

11 min readBy Davinder Kumar Meen

A hand holding a paper takeaway bag with an orange tape seal beside a phone on a restaurant counter

The WhatsApp Business API, which Meta now calls the WhatsApp Business Platform and offers mainly as the Cloud API, is how a business sends WhatsApp messages from its own systems: order confirmations from the till, reminders from a booking system, replies from a shared inbox or an AI assistant. The free WhatsApp Business app is enough while one or two people answer chats by hand. Move to the platform when messages need to be sent automatically, by several staff, or at volume. You can connect to the Cloud API directly or through a provider such as Twilio or respond.io, and as of November 2026 Meta charges per delivered message, by message category and the customer's country.

Key takeaways

  • The app and the platform are different products. The app is for typing chats on a phone; the platform is an API that your software, a provider's inbox or an automation tool uses.
  • Outside a 24-hour customer service window you can only send pre-approved templates (marketing, utility or authentication). Inside the window you can reply freely.
  • Since 1 July 2025 Meta charges per delivered message, not per conversation. From 1 October 2026 service replies beyond 1,000 a month per number, and utility templates sent inside an open window, are charged again.
  • A provider adds a fee or subscription on top of Meta's charges in return for an inbox, tooling and support; going direct leaves that work to you.
  • You need opt-in before you message anyone, and new accounts start at 250 unique customers per 24 hours for business-initiated messages.

Is the WhatsApp Business app enough, or do you need the API?

The app is enough if a person answers every message and nothing needs to be sent automatically. It is a free download from your phone's app store, and gives you a business profile, a place to show products and tools for replying quickly (WhatsApp Business app).

You need the platform when any of these is true:

  • Messages come from a system. An order, booking or payment should trigger a WhatsApp message without anyone typing it.
  • Several people share one number. A shared inbox with assignment and history needs the API underneath.
  • You want automation or AI. Chatbots, AI assistants and workflow tools all connect through the API. Meta's own Meta Business Agent also runs on the platform.
  • You send at volume. Reminders or updates to many customers a day.

You may not have to give up the app: Meta's "coexistence" option connects an existing app number to the Cloud API through a provider's sign-up flow, keeps the app for one-to-one chats and syncs history between the two (Meta, onboarding WhatsApp Business app users).

If you are still choosing between WhatsApp, SMS and RCS for a given message, our comparison of RCS, SMS and WhatsApp covers reach and fallback; this guide assumes WhatsApp is the channel.

Should you go direct to the Cloud API or use a provider?

Both routes use the same platform, templates and Meta charges; the difference is who builds and runs the parts around it.

Direct Cloud API Through a provider (Twilio, respond.io and others)
What you get Meta's API and WhatsApp Manager; nothing on top The API plus the provider's console, inbox, SDKs or automation tools
Who pays Meta You, with a payment method in Meta's Billing Hub You or the provider, depending on the provider's arrangement with Meta
Extra fees None beyond Meta's charges Per-message fees or a subscription (examples below)
Best fit A product team that will build its own sending, inbox and webhook handling A business that wants a working inbox or one account for SMS, voice and WhatsApp
Support Meta developer support The provider's support

Meta's own terms for the companies in the middle are Solution Partners, which can extend credit and invoice their clients for API usage, and Tech Providers, whose clients add their own payment method and are billed by Meta directly (Meta, Partners overview). Ask any provider which one it is, because it decides who sends you the WhatsApp bill.

Two examples, as of November 2026:

  • Twilio charges $0.005 per WhatsApp message, inbound or outbound, plus Meta's fee for the message, and $0.001 for a message that ends in "failed" status (Twilio WhatsApp pricing). It suits products that also need SMS, voice or one-time passcodes from one account.
  • respond.io is a customer conversation platform with plans from $79 a month billed yearly (Starter) to $279 (Advanced), plus Enterprise on quote; it states that "WhatsApp fees are not included in any respond.io subscription" (respond.io pricing). It suits teams that want a shared inbox and workflows rather than writing code.

Compare any provider on three points: its fee on top of Meta's, who bills you for Meta's charges, and whether you can move your number later.

What do Meta's charges look like as of November 2026?

Meta charges per delivered message, only for messages from the business to the customer, at a rate set by message category and the country calling code of the recipient (Meta, pricing on the WhatsApp Business Platform). Messages customers send you are free. The categories are:

Category What it is for Can start a conversation?
Marketing (template) Offers, announcements, reminders to come back Yes
Utility (template) Order, booking and account updates tied to something the customer did Yes
Authentication (template) One-time passcodes Yes
Service (non-template) Replies typed by staff or a third-party AI inside the 24-hour window No
Meta Business Agent (non-template) Replies written by Meta's own AI agent No

What changed on 1 October 2026, from Meta's pricing page:

  • Service messages: every business phone number gets 1,000 free service messages a month, with no roll-over; from the 1,001st, they are charged. Without a payment method on file, Meta stops delivering service messages once the free tier is used.
  • Utility templates inside an open customer service window, free since July 2025, are charged again.
  • Free entry point: when a customer messages you from a Click to WhatsApp ad and you reply within the window, Meta does not charge for marketing, utility, authentication or service messages for up to 7 days (Meta Business Agent messages are still charged).
  • Meta Business Agent messages are billed at one global rate of $2.00 per million tokens, which Meta estimates at about 4 to 5 US cents per message.
  • Utility and authentication messages have volume tiers: lower rates as your monthly count in a market grows, reset each month.
  • India: Meta now bills Indian businesses in rupees. If your business is billed with India as the Sold-To country, directly or through a Solution Partner, your WhatsApp messaging accounts must move to INR by 31 December 2026; from 1 January 2027 Meta stops delivering messages from accounts that have not moved.

Meta may change rates only on the first day of a quarter, with at least a month's notice, so check its rate cards for your countries rather than any figure copied elsewhere.

How do templates and the 24-hour window work?

A customer service window opens when a customer messages or calls you and lasts 24 hours, resetting with each new message from them. Inside it you can send any normal message. Outside it, the only thing you can send is an approved template (Meta, template fundamentals).

Practical points for templates:

  • Each template has a category. Choose it honestly. Since 9 April 2025, if you submit a template as utility and Meta decides it is marketing, it is approved as marketing and priced as marketing (Meta, template categorization).
  • Utility means tied to a specific transaction. Meta's own example: a feedback request about a particular order can be utility, but "a general/generic survey or request for feedback will not be approved as utility".
  • Templates are per language, with variables (order number, date, name) filled in at send time.
  • Plan the content first. Write the order, booking or reminder messages you need before development, so approval does not hold up launch.

What about opt-in, messaging limits and your display name?

Opt-in. Meta requires opt-in before you message anyone. It must name your business and make clear the person is agreeing to receive messages from you; it can be collected on your website, by SMS, by phone or on paper, and does not have to mention WhatsApp specifically (Meta, getting opt-in). Privacy and marketing laws differ by country (Canada's anti-spam law, GDPR in Europe, India's DPDP Act), so check the rules where your customers are. This is general information, not legal advice.

Messaging limits. A new business portfolio can send business-initiated messages to 250 unique customers in a moving 24-hour period. Verifying your business, or sending 2,000 delivered template messages of good quality in 30 days, makes you eligible for 2,000 after Meta reviews your message quality, and from there to 10,000, 100,000 and unlimited as quality holds. Replies inside a customer service window do not count (Meta, messaging limits).

Display name. You set a display name when you register the number. Once you reach a higher messaging limit it is checked against Meta's guidelines, and an approved name appears at the top of chats; you can change it up to 10 times in 30 days, and each change is reviewed again (Meta, display names). Use your trading name as customers know it, and have business verification documents ready.

What have we built with WhatsApp?

Two of our published projects show the two routes.

Through a provider, with no custom app. A restaurant business ran its orders in the Foodics restaurant system and spoke to customers through respond.io. We connected the Foodics orders API to Zapier so that each order sends a confirmation and, after checkout, a request to rate the service, delivered through respond.io. (Foodics to respond.io order messages). For a small business this is often the right shape: the provider holds the connection and inbox, and the integration only delivers the right event.

Directly on the Cloud API, inside a product. For Froono, a multi-tenant customer loyalty platform for retail chains, we built WhatsApp Cloud API campaigns, templates, conversations and webhook handling into the platform's own admin, with one schedule model and a calendar planner for marketing, messages and lucky draws, and background workers that send on schedule (Froono customer loyalty platform). Going direct made sense there because WhatsApp is one feature of a larger product that each client company runs for its own stores.

Our Twilio integration service covers products that need SMS, voice, passcodes and WhatsApp from one account: a registered WhatsApp sender, approved templates, status callbacks, opt-out handling and webhook signature checks.

What should you decide before you start?

List each message and its category (order confirmation is utility, abandoned cart is marketing, passcode is authentication, support replies are service), the system that triggers it, and who answers replies: a person in a shared inbox, an AI assistant with a hand-off, or no one. Then choose direct or provider, decide who pays Meta, decide how you collect and record opt-in, and pick the number: a new one, or your existing app number through coexistence.

FAQ

Is the WhatsApp Business API free?

No. The free product is the WhatsApp Business app. On the platform, messages customers send you are free, and as of November 2026 each phone number gets 1,000 free service replies a month, but templates and further service replies are charged per delivered message at Meta's rates, plus any provider fee.

Can a small business use the WhatsApp Cloud API without a provider?

Yes. Meta offers the Cloud API directly; you create the accounts, add a payment method, register a number and build or buy the software that sends and receives messages. A provider is optional and mainly saves you building an inbox and tooling.

Can I keep using the WhatsApp Business app on the same number?

Often yes, through Meta's coexistence option, which keeps the app for one-to-one chats and syncs history with the API. Check that your provider supports it.

Why was my utility template approved as marketing?

Meta reviews the category. If the content promotes something, or is a generic request rather than an update about a specific order, booking or account, Meta approves it as marketing and it is priced as marketing. You can request a review up to 60 days after the category was changed.

Sources (13 links)
Share this article