> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/whatsapp-calls.md).

# WhatsApp Calls

This article explains how to configure and use the calling feature through the WhatsApp Business API within the platform.

Read all the requirements carefully before starting the setup.

{% embed url="<https://youtu.be/NDsh4DEytBY>" %}

***

### 1. Requirements

To use the calling functionality, it is necessary to:

* Have the account connected via **WhatsApp Business API**.
* Have the calling module active in your plan.
* Carry out the setup with a user who has access to the **System Settings**.

If the module is not yet available, contact the sales team to request activation.

Only users with administrative permission will be able to:

* Activate the feature.
* Define call operators.
* Configure access permissions.

***

### 2. Call pricing

The billing amounts for calls made through the WhatsApp Business API are defined by Meta Platforms.

Currently, prices are shown in the **dollar (USD)** currency and may vary according to factors such as region, call type, and Meta's current policies.

To check the updated amounts and understand how the billing model works, access the official documentation:

{% embed url="<https://developers.facebook.com/documentation/business-messaging/whatsapp/calling/pricing/>" %}

On that page it is also possible to download the **official document with the pricing table**, made available by Meta itself.

> **Important:**\
> As the amounts are set directly by Meta, they may change without prior notice. It is recommended to always consult the official documentation to check the latest prices.

***

### 3. Configuration

The configuration is divided into three steps: account connection, feature activation, and permission definition.

***

#### 3.1 Connect the WhatsApp API account

Access:

**System Settings > Account Settings**

Add or verify the account connection in **WhatsApp API**.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FZYGqt52uvyf6F6VJrXgF%2Fimage.png?alt=media&amp;token=5267150e-81fb-44be-831a-8a92b449eaf2" alt=""><figcaption></figcaption></figure>

***

#### 3.2 Activate WhatsApp Calls

In the side menu, access:

**WhatsApp Calls**

Then:

* Select the desired account.
* Enable the feature status.
* Define the departments or users that will act as call operators.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FIDL29VyvfEeidjk1EiQp%2Fimage.png?alt=media&amp;token=730e64ef-7a4f-44c9-bfbf-f0f318c5ec46" alt=""><figcaption></figcaption></figure>

***

#### 3.3 Configure access permissions

Go to the **Permission Group** and enable the path:

**SAC 360º > WhatsApp API > Calls**

Important:\
After enabling the permission, link the group to the corresponding department.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FJ4GKJVoxm2J1UEzmIoZd%2Fimage.png?alt=media&amp;token=5ae7d8ee-6663-43fe-8590-9c04496704fa" alt=""><figcaption></figcaption></figure>

***

### 4. How to make calls

Before making a call, it is mandatory to send a **call request** to the contact and wait for acceptance.

Authorization can be:

* Temporary
* Permanent

***

#### 4.1 Send call request

In the **SAC**, **CRM** or **Contacts**, use the service options button to send the request.

The contact will receive a message with options to **accept or decline** the call.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F0OQhg6PXt8mvzQ5zazXN%2Fimage.png?alt=media&amp;token=20d3dfd9-36bf-4647-bf5e-75f372b3fcd1" alt=""><figcaption></figcaption></figure>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F7kZGV0uH0SLUUIQjDRnQ%2Fimage.png?alt=media&amp;token=451f71ea-69ac-4625-8ab6-83018e4b8517" alt=""><figcaption></figcaption></figure>

***

#### 4.2 Rules for sending the request

The call request can only be sent if:

* The contact has the **WhatsApp** field filled in.
* The service window is open.
* The service is being carried out by the **WhatsApp API**.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F7AB2Dx60pan6ehEwBDgf%2Fimage.png?alt=media&amp;token=abc6f244-d257-4033-9324-e08f9b23ec48" alt=""><figcaption></figcaption></figure>

***

#### 4.3 Make the call

After the request is accepted, the call button will be available anywhere in the system that has the call action.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FxYjNfjfVvFxnCq6GW0gm%2Fimage.png?alt=media&amp;token=282a4f32-3526-4d70-a56f-21533be3c621" alt=""><figcaption></figcaption></figure>

***

### 5. Final considerations

* The feature depends exclusively on integration with the **WhatsApp Business API**.
* The call can only be initiated after the contact authorizes it.
* Permissions and operators must be configured correctly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/system-settings/whatsapp-calls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.