How to Disable Calls on WhatsApp Business: 2026 Guide

Disabling calls on WhatsApp Business became a hot topic after Meta rolled out voice and video calls on WhatsApp Web on July 28, 2026, and confirmed that business video calls on the official API are coming in Q4. If your business number rings all day and no one picks up, you have two very different technical paths—and choosing wrong costs you customers.

TL;DR

• In the WhatsApp Business App, disabling calls is a local device setting: App settings → Call settings → turn off Receive calls.
• In the Official API (Cloud API), it's an API field: POST /<PHONE_NUMBER_ID>/settings with calling.status = "DISABLED". The call icon disappears from the chat and business profile.
• There's a better middle ground than the on/off switch: call_hours (business hours by timezone and holiday) and callback_permission_status (call-back requests).
• Meta already limits business-initiated calls: 1 permission request per day and 2 per week per user, on production accounts.
• With business video calls expected in Q4 2026, turning everything off today could close a channel that's valuable for telemedicine, identity verification, and inspections.

Why so many businesses want to disable calls in 2026

The question isn't new, but search volume exploded for a concrete reason. On July 28, 2026, WhatsApp announced audio and video calls directly in the web version, plus call transfer between phone and desktop, waiting rooms on call links, high-definition video from the first seconds, and noise suppression. The feature is rolling out gradually.

In practice, this changed the geography of the problem. Before, an unwanted call only rang on the phone sitting on the agent's desk. Now it can ring in the browser of someone working all day on WhatsApp Web—and interrupt text-based service, which is where most US SMBs actually convert.

Two factors add up. First: the business number receives calls from anyone who has the contact, with no queue, no hours, no recording, and no record in the CRM history. Second: those using the free app have no routing layer—the phone just rings. It's a phone system without a PBX. If you're still deciding between the app and the paid platform, read the comparison WhatsApp Business App vs Official API first, because the answer for calls changes completely depending on the scenario.

How to disable calls in the WhatsApp Business App (step by step)

This is the path for those using the free app downloaded from Google Play or the App Store.

The official path inside the app

1. Open WhatsApp Business on your phone.
2. Tap the three dots in the top right corner.
3. Go to App settings (in some versions, the menu appears as Settings → Business tools).
4. Open Call settings.
5. Turn off the Receive calls option.

From then on, the device stops receiving voice calls on that number. It's a per-device setting, not per-account.

If the option doesn't appear in your version

WhatsApp's feature rollout is gradual, and not every device gets the same menu at the same time. In that case, use the native privacy alternatives:

• Silence unknown numbers: in Settings → Privacy → Calls, enable the option. Any number not in your contacts stops ringing—but the call still appears in the Calls tab and in notifications.
• My contacts except…: in the same privacy menu, restrict who can call you to a controlled list.
• Individual block: for the specific number that keeps calling, blocking cuts both calls and messages at once.

What the customer sees on the other end

This is the part almost no one explains. With Receive calls off, the call button disappears from the conversation. But with Silence unknown numbers, the customer still hears the ringing tone—they think you're ignoring them. The difference between "the button doesn't exist" and "you didn't answer" is huge for brand reputation.

The three traps of disabling calls only in the app

I've seen entire operations break by trusting this setting. The three recurring problems:

1. It's not auditable. The setting lives on the device. Switched phones, formatted, reinstalled the app, or a new agent with another linked device? It reverts to default without anyone knowing.

2. It doesn't scale. The app was designed for one or two people answering directly. When the business grows and decides to automate externally with an unofficial API, it enters the territory that causes the most headaches: number bans. I've detailed the triggers in How to avoid WhatsApp business number blocking.

3. Silencing isn't disabling. Silencing unknown numbers solves noise, not flow. The call is still logged, still generates a notification, and still occupies the agent who needs to check if it was a hot lead.

How to disable calls in the Official API (WhatsApp Cloud API)

On the WhatsApp Business Platform, behavior is fully controlled by API—and that's where things get truly configurable. Meta exposes a number settings endpoint:

POST /<PHONE_NUMBER_ID>/settings

To turn it off completely, the payload is straightforward:

{
  "calling": {
    "status": "DISABLED"
  }
}

With status set to DISABLED, according to Meta's official documentation, calls are disabled and the call icon is not shown in the conversation or on the business profile info page. A GET on the same path returns the current configuration. Note the conceptual difference: here, disabling calls applies to the entire number, not to a device—that's what turns the decision into a service policy, not a preference of whoever has the phone in hand.

The fields you need to know

Field	Values	Purpose
calling.status	ENABLED / DISABLED	Turns the calling feature on or off for the number
calling.call_icon_visibility	DEFAULT / DISABLE_ALL	Hides the call button in the chat bar, profile, and other entry points
calling.callback_permission_status	ENABLED / DISABLED	Allows the user to request a call-back
calling.call_hours	object	Defines phone support hours by timezone and holiday
calling.sip	object	Integrates calls with your SIP server (requires explicit enablement)

Monitor changes with webhooks

Those managing multiple numbers need to know when someone changes this setting. Subscribe to the account_settings_update field (with the whatsapp_business_management permission) and you'll receive notifications of changes to status, call_icon_visibility, callback_permission_status, sip.status, and the SRTP key exchange protocol. That's the audit trail the free app will never give you.

Middle ground: business hours instead of disabling calls entirely

In most projects we handle, the real problem isn't the call—it's the call outside business hours. No one complains about a call at 2 PM on Tuesday; they complain about the 11 PM Sunday call that no one answers and turns into a bad review.

That's what call_hours is for. The structure accepts timezone, weekly schedule, and holiday calendar:

{
  "calling": {
    "status": "ENABLED",
    "call_hours": {
      "status": "ENABLED",
      "timezone_id": "America/New_York",
      "weekly_operating_hours": [
        { "day_of_week": "MONDAY", "open_time": "0900", "close_time": "1800" }
      ],
      "holiday_schedule": [
        { "date": "2026-12-25", "start_time": "0000", "end_time": "2359" }
      ]
    }
  }
}

Outside the configured window, the customer is directed to the text conversation instead of falling into the void. Combine that with callback_permission_status enabled: those who really need to talk request a call-back, and your team calls when someone is available. It's the difference between a closed door and a door with a doorbell.

When NOT to disable calls on WhatsApp Business

Before turning off the channel, look at the calendar. According to MobileTime's reporting published on July 17, 2026, Meta is testing business video calls on the WhatsApp Business Platform, with a launch expected in Q4. The use cases cited are exactly the highest-ticket ones: telemedicine, identity verification, technical support, product demos in retail, and insurance claim inspections. A video call button will appear in the conversation, with configurable hours and consumer authorization for each call.

The US context matters: WhatsApp is present on a significant portion of smartphones in the country. Authenticating a legitimate call within the app—with an official account badge—solves a problem no carrier has solved: customers not answering unknown numbers for fear of scams.

The limits Meta already imposes

The fear of "they'll call me nonstop" makes less sense than it seems, because the platform is already restrictive with business-initiated calls:

Rule (production account)	Limit
Call permission requests per user	1 per day and 2 per week
Business-initiated calls	up to 100 per day
Consecutive unanswered calls	2 trigger a warning to reconsider
Consecutive unanswered calls	4 revoke permission automatically

In the sandbox environment, the numbers are different: 25 permissions per day and 100 per week, with a warning after 5 unanswered calls and revocation after 10. In other words: the business doesn't call when it wants; it calls when the customer authorized it.

The cost comes into play before you decide

Disabling calls is often a cost decision disguised as an experience decision. It's worth having the numbers on the table. Brazilian accounts started being billed in reais as of July 1, 2026, in the same move that reorganized message pricing. Voice calls via the API are billed by duration, with 6-second pulses, variable rates by country, and volume discounts—a fraction of a pulse counts as a full pulse.

On the messaging side, industry press points to two dates for 2026: August 1, when Meta Business Agent billing began based on token consumption (around $2 per 1 million tokens), and October 1, when service and utility messages within the 24-hour window start being charged. Confirm current rates on the platform's official pricing page before closing a budget—they change.

Two practical points: if your inbox platform charges on top of Meta's price, every call minute and every message becomes third-party margin—the subject of the post Markup on WhatsApp messages. And if it charges per agent, disabling calls won't save your account at the end of the month, as I argued in Unlimited agents on WhatsApp.

How we handle this in Agathas Web projects

I've been a full-stack developer for over 15 years and have run Agathas Web since 2008, with much of my work today in official WhatsApp API integrations for SMBs. The playbook we apply before touching any call configuration is always the same:

1. Measure: how many calls come in per week, at what times, and how many turned into sales or resolved tickets. Without that data, disabling calls is a guess.
2. Separate channels: sales numbers and support numbers rarely need the same voice policy.
3. Set hours before disabling: call_hours first, status: DISABLED only if out-of-hours volume remains unmanageable.
4. Leave a trail: account_settings_update webhook active and the configuration versioned with the rest of the infrastructure.
5. Review in Q4: with business video calls coming, today's policy could be obsolete in three months.

In projects running on our service platform, this configuration lives in the dashboard, alongside automation flows—not hidden in a phone menu that any team member can change without notice.

Conclusion: turn off the noise, not the channel

Disabling calls on WhatsApp Business is easy in both worlds: a toggle in the app, a DISABLED field in the Cloud API. The hard part is deciding whether you should. In most operations we analyze, the right answer wasn't to cut voice, but to put hours, permission, and logging around it—because in 2026, WhatsApp's voice channel stopped being an accessory to chat and became part of the service journey.

If you don't have clarity on how many missed calls your number accumulates per month, start there. The natural next step is to migrate the number to the Official API, where all this policy becomes auditable configuration instead of device preference.