> 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/general/voip/how-the-voip-queue-works/operators-block-voip.md).

# Operators Block - VoIP

<figure><img src="/files/af9ab46dce552e6f263fbf4fee20ba46180b4783" alt=""><figcaption></figcaption></figure>

&#x20;**What is the Operators Block?**

It is a component within Sprinthub's call flow that serves to define which users will receive calls at each stage of the service.

<figure><img src="/files/359bb7d1c21e6f90aa2eabd1d638455cfbde7f71" alt=""><figcaption></figcaption></figure>

#### **Service Options**

* **Sprinthub VoIP**\
  Sprinthub's native cloud telephony service. Eliminates physical PBX and offers features such as call recording, reporting, and scalability.
* **Vox Implant**\
  Third-party telephony solution integrated with Sprinthub, ideal for those who need more advanced features such as voice bots and call transcription.
* **External SIP**\
  Allows connecting an existing VoIP provider or PBX to Sprinthub using SIP credentials. Recommended for those who already have their own infrastructure or contracts with other carriers.

#### **How to Configure**

<figure><img src="/files/9ac9f73fed8325e7f09ab899dd184649e2dd059a" alt=""><figcaption></figcaption></figure>

1. Create or edit a call flow in Sprinthub.
2. Drag the **Operators Block** into your service diagram.
3. Select a service (Sprinthub VoIP, Vox Implant, or External SIP).
4. Add the operators (users) who should receive the calls.
5. Define the distribution method (simultaneous, sequential, etc.).
6. Save and test the flow to ensure calls are routed 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/general/voip/how-the-voip-queue-works/operators-block-voip.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.