Waaplink
← Blog

WhatsApp Business Calling in 2026: Voice and Video Calls From the Same Chat

A practical 2026 guide to WhatsApp Business Calling: how voice calls work in the Business App versus the Calling API, when to route customers to a call, how to set calling hours, and how to keep one thread for chat and voice.

2026-10-19

WhatsApp Business Calling in 2026: Voice and Video Calls From the Same Chat

Most customer conversations can be finished in text. Some can't: a delivery that needs a human, a booking with special requests, a complaint where the customer just wants to talk. In 2025 and 2026 Meta moved calling into the WhatsApp Business Platform, so a customer can now tap a call button on your profile and speak to your team without leaving the thread you already share.

This guide covers what calling looks like today, what the WhatsApp Business App gives you for free, what the Calling API adds, and how to set it up so calls reach the right person instead of ringing an unattended phone.

Chat first, call when text hits a wall

Calling is not a replacement for messaging β€” it is an escape hatch. The value is deflection in reverse: when a thread stalls, a two-minute call closes it, and everything stays in one recorded conversation.

| Situation | Best channel | Why |

| --- | --- | --- |

| Price, hours, address, stock check | Chat | Instant, no interruption, reusable answers |

| Booking with special requests | Chat, then optional call | Questions first, confirm by voice if needed |

| Delivery problem or dispute | Call after chat | Tone de-escalates faster by voice |

| Post-sale support for a product | Call or video | Screen share or visual guidance |

| Marketing or promotions | Chat only | Calls cannot carry opt-in offers legally |

The rule of thumb: text to capture, voice to resolve. Every call you take should be tied to an existing WhatsApp thread, so the context travels with the customer.

WhatsApp Business App: free calling for small teams

If you run the free WhatsApp Business app on a phone, calling already works and costs nothing for you or your customer.

  • Inbound calls: customers can call your business number directly from your profile β€” the same number they use to message you.
  • Outbound calls: you can call any customer back inside the chat, including from a desktop session.
  • Video calls: available one-to-one, useful for quick consultations.

For a shop, salon or tradesperson, this is usually enough. Pair it with a click-to-chat link so people arrive in the right conversation, then use the tools under /en/tools to build that link. If you are still deciding between the app and the platform, the comparison in WhatsApp Business API vs the Business App breaks down the trade-offs.

The Calling API: what it adds for larger teams

The WhatsApp Business Calling API is a Cloud API feature that puts voice (and, in rollout, video and screen share) on the same number your business already uses for messaging. It is aimed at support and sales teams, call centres and telehealth-style services.

Key capabilities:

  • One number, one thread. Inbound and outbound calls live in the same conversation history as text, so an agent can see the order number before answering.
  • User-initiated and business-initiated calls. Customers can call you from your profile or a call button; you can request permission to call them back from inside the chat.
  • Call icon control. Turn the call button on or off on your profile β€” useful when a queue would only create missed calls.
  • Business call hours. Route callers to messaging outside opening hours instead of letting the phone ring out.
  • Callback requests. When nobody answers, the customer can ask to be called back later, captured automatically in the thread.
  • Click-to-call buttons and call deep links. Add a "Call us" button in a template, a website, an app or a QR code.
  • Call deflection. Point customers toward chat when voice is not the right channel, which keeps support costs down.

Two constraints matter before you plan a rollout. Your number must be on the Cloud API (not the Business App), and your account needs a messaging limit of at least 2,000 unique recipients per day. There is also a short list of countries where business-initiated calling is not yet available β€” the United States, Canada, Egypt, Vietnam and Nigeria β€” while user-initiated calling is available everywhere the Cloud API operates. Pricing for the underlying messaging still follows the per-delivered-template model described in the WhatsApp Business API pricing guide, and customer-initiated service conversations inside the 24-hour window remain free.

Setting up so calls actually get answered

The technology is the easy part. Staffing is where most businesses lose calls.

Decide who owns the phone. In the Business App, that is one or two people. On the API, assign calls to a queue or a rotating owner so nobody assumes someone else picked up. Write down call hours. Customers should be able to see when you are reachable. Outside those hours, an automatic reply such as "We're closed β€” message us and we'll call you back at 9am" is far better than a dead ring. Automated replies and greeting messages are covered in the quick replies and greeting guide. Prepare the 20 seconds before pickup. The agent should already see the thread. A greeting that references what the customer wrote ("Hi Sara, I can see the tracking issue on order 4471") sounds like service; "Hello, how can I help?" sounds like a call centre. Give a reason to call. A click-to-chat link gets people into chat. Add a "Prefer to talk? Call us" line in your link page, email signature or Google Business Profile, where a call genuinely speeds things up β€” complex orders, quotes, complaints. Respect consent. Voice is a support and service channel. Marketing offers still belong in opted-in message templates, not in unsolicited outbound calls. The consent rules are explained in the opt-in consent guide, and the window that governs outbound messaging after a customer goes quiet is in the messaging limits 2026 guide.

Can AI answer the phone?

Yes, and this is where 2026 differs from the year before. Purpose-built voice automation can handle routine calls β€” order status, opening hours, appointment changes β€” and hand off to a human when the request falls outside its scope. The direction of Meta's platform is clearly toward this: an AI agent that answers, acts and escalates rather than a general-purpose assistant that tries to answer anything. If you are weighing that route, the WhatsApp AI chatbot guide covers the compliant, task-scoped approach.

Keep voice AI narrow: one job per bot β€” order tracking, bookings, lead qualification β€” is both the policy-safe design and the one that actually converts.

A simple rollout checklist

  • Confirm your number works for calls in the app, and test inbound and outbound once.
  • Add a click-to-chat link everywhere you publish your number.
  • Set call hours and an after-hours automatic message.
  • Nominate an owner or queue for calls, with a fallback.
  • Log call outcomes in the thread so chat and voice share one history.
  • Review weekly: how many calls were resolved on the call, and how many should have stayed in chat.

Start with chat, add voice where it removes friction, and keep both in one conversation.