Supported WhatsApp Business Calling scenarios
WhatsApp Business Calling supports several inbound and outbound call flows. Each scenario depends on the call initiator (user or business), the routing logic, and the destination platform (for example, Conversations, SIP, or WebRTC).
Use the tables below to understand how to configure and route different WhatsApp call flows using Infobip products and APIs.
User-initiated calling scenarios
The following call flows are supported when the user initiates a WhatsApp call to your business. Select to expand each scenario context.
Scenario | Description |
|---|---|
WhatsApp calls to Conversations | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to Conversations.
|
WhatsApp calls to Conversations with IVR API (opens in a new tab) | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to an IVR created with the IVR API. The IVR scenario can transfer this incoming call to an agent in Conversations.
|
WhatsApp calls to Conversations with Moments IVR | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to an IVR created as a flow in Moments. The flow can transfer this incoming call to an agent in Conversations.
|
Scenario | Description |
|---|---|
WhatsApp calls to IVR (API) (opens in a new tab) | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to an IVR created with the IVR API.
|
WhatsApp calls to Moments IVR | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to an IVR created as a flow in Moments.
|
Scenario | Description |
|---|---|
WhatsApp calls to SIP trunking | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to your voice equipment (SBC, PBX) over SIP trunking. This can allow WhatsApp end users to reach a business on their own contact center platform or regular phone environment, but calling at no cost (for the end user).
|
Scenario | Description |
|---|---|
WhatsApp calls to webRTC | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to a predefined webRTC user in the web or mobile application you developed based on our webRTC SDKs. This can allow WhatsApp end users to reach a business in their voice-enabled application but call at no cost (for the end user).
|
Scenario | Description |
|---|---|
WhatsApp calls to the custom voice application of the customer, built with the Calls API platform | Incoming calls from WhatsApp users to our WhatsApp sender will be redirected to the custom voice application that the customer has developed (and is hosting) based on our Calls API platform.
|
It is strictly forbidden to connect WhatsApp Business Calling to PSTN. For instance, forwarding an inbound WhatsApp call to your existing business phone number is not allowed.
Business-initiated calling scenarios
These flows start with your business placing a call to a user, based on accepted call permissions. Select to expand each scenario context.
Scenario | Description |
|---|---|
WhatsApp calls from Conversations | This scenario allows an agent in Conversations to initiate a voice call to a WhatsApp end user. |
Scenario | Description |
|---|---|
SIP trunking to WhatsApp end user | Incoming call requests from your voice platform are sent to Infobip over a SIP trunk. Using Infobip call routing, this call request is converted into a business-initiated call to a WhatsApp end user.
NOTE You must get the end user's call permission separately. |
Scenario | Description |
|---|---|
webRTC to a WhatsApp end user | The WebRTC SDK does not have a method to place a call to WhatsApp end users directly. Call routing can be used as a bridging system.
NOTE You must get the end user's call permission separately. The webRTC call to |
Scenario | Description |
|---|---|
Your custom voice application built with the Calls API platform is triggering outbound WhatsApp calls. | Your application can implement whatever use case is needed, including bridging WhatsApp calls to WebRTC, SIP, or even other WhatsApp participants. WhatsApp calls are handled in a similar way as any other Calls API-supported endpoint type (phone, webRTC, SIP, Viber). NOTE You must get the end user's call permission separately. |