> 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/power-dialer.md).

# Power Dialer

## Power Dialer Manual

The **Power Dialer** is SprintHub's queued calling mechanism. It allows you to create a contact list and have the system make calls automatically, respecting simultaneous volumes and intervals defined by you. It is the fastest and most organized way to run active calling, follow-up, and mass prospecting campaigns.

This manual shows, step by step, how to configure and use Power Dialer in your day-to-day.

***

### Contents

1. [What is the Power Dialer](#id-1.-o-que-e-o-power-dialer)
2. [Creating a call list](#id-2.-criando-uma-lista-de-ligacoes)
3. [Managing your lists](#id-3.-gerenciando-suas-listas)
4. [Starting dialing](#id-4.-iniciando-a-discagem)
5. [Tracking execution](#id-5.-acompanhando-a-execucao)
6. [Creating lists from other modules](#id-6.-criando-listas-a-partir-de-outros-modulos)
   * [6.1 From Contacts](#id-6.1-a-partir-dos-contatos)
   * [6.2 From Companies](#id-6.2-a-partir-das-empresas)
   * [6.3 From Support Tickets](#id-6.3-a-partir-dos-atendimentos-do-sac)
   * [6.4 From CRM Opportunities](#id-6.4-a-partir-das-oportunidades-do-crm)
7. [Best practices in day-to-day use](#id-7.-boas-praticas-no-dia-a-dia)

***

### 1. What is the Power Dialer

Power Dialer is a tool within the module **VoIP** of SprintHub that organizes several calls into a single queue and executes them in sequence. Instead of calling each contact manually, you create a list, define who is responsible, who can operate it, and the call pace — and the system takes care of the rest.

You can access it through the menu **VoIP → Power Dialer**.

***

### 2. Creating a call list

When creating a new Power Dialer list, the following screen is displayed:

<figure><img src="/files/020a41fafa2caffd2306011b8ade470d71f1c68b" alt=""><figcaption></figcaption></figure>

Fill in each field as follows:

| Field                                | Description                                                                                                              |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| **First name**                       | List identification. Use a descriptive name to find the queue later (e.g.: `Prospecting May`, `Gold Clients Follow-up`). |
| **Contacts**                         | Select the contacts that will be part of the call queue.                                                                 |
| **Responsible party**                | Main person responsible for the queue. The owner always has permission to run it.                                        |
| **Operators**                        | Other users who will be able to run the queue besides the owner. Useful when an entire team can handle the calls.        |
| **Parallel quantity**                | How many calls are made at the same time. Increase this value when several operators are available to answer.            |
| **Interval between calls (seconds)** | Waiting time between each batch of calls. Allows the team to catch their breath between conversations.                   |
| **Description**                      | Free text explaining the purpose of the queue. It appears to all operators who use the list.                             |

> **Tip:** just below the form, an automatic summary appears explaining how the queue will behave — for example: *"Calls will be made in batches of 1 contacts until reaching the total number of contacts, with a 10-second interval between each batch."*

After filling in the fields, you can choose between two buttons:

* **Save** — only saves the queue for future use.
* **Save and run** — saves and already opens the screen to start dialing (see section 4).

***

### 3. Managing your lists

All created queues appear in the main Power Dialer listing:

<figure><img src="/files/50e50ba8d62b1f1da6b584628c88169a2e7d2675" alt=""><figcaption></figcaption></figure>

In the list, you can quickly check:

* **Status** — current queue status (`Stopped`, `Running` etc.).
* **Name and description** — queue identification.
* **Contacts Qty** — how many contacts were selected.
* **Numbers Qty** — how many phone numbers exist in those contacts.
* **Total Calls** — how many calls have already been made from that queue.
* **Responsible party** — who owns the queue.
* **Created on** — creation date and time.

In the column **Actions**, you will find three buttons:

| Button         | Role                                                                 |
| -------------- | -------------------------------------------------------------------- |
| ▶️ **Run**     | Starts dialing the queue.                                            |
| ✏️ **Edit**    | Opens the edit screen to change contacts, operators, intervals, etc. |
| 🗑️ **Delete** | Removes the queue from the system.                                   |

You can also use the filter **Responsible party** and the **search by queue name** to quickly locate a list among several.

***

### 4. Starting dialing

<figure><img src="/files/90f23fe0d89c71288eddddd709c73879a4873f59" alt=""><figcaption></figcaption></figure>

When clicking on **Run**, the system requests the outbound number — that is, the phone number that will appear to the contact being called:

Select one of the numbers available in your account and click **Start dialing**. From that moment on, the queue goes into execution.

> **Why choose the number?** The outbound number defines which caller ID will reach the recipient (area code, country, purpose). In local campaigns, use numbers with the same area code; in international campaigns use the compatible number.

***

### 5. Tracking execution

When the queue is running, the status in the listing changes to **Running** and a fixed bar appears in the lower corner of the screen:

<figure><img src="/files/586ef98c199c1d2e785436a29680610b6824dd26" alt=""><figcaption></figcaption></figure>

In this bar you can see:

* The **queue status** (e.g.: `Running (1/1)`) indicating the current progress.
* The **number being called at this moment**.

The bar can be **dragged horizontally** if it gets in the way of viewing any element on the screen, but it remains visible at all times while the queue is active — so you don't lose track of the progress even while navigating other areas of SprintHub.

***

### 6. Creating lists from other modules

In addition to creating a queue from scratch through the VoIP module, Power Dialer can be triggered directly from other SprintHub modules. This makes it easy to turn contact lists, companies, support tickets, or opportunities into immediate calling campaigns.

In all cases, the path is the same:

1. Select the desired items.
2. Click the button **Power Dialer** that appears in the actions bar.
3. Fill in the queue details (name, interval, operators, etc.) — the contacts are already preloaded.

#### 6.1 From Contacts

In the module **Contacts**, select one or more contacts from the list. Then open the bulk actions menu and click on **Power Dialer**:

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

Use this path when you already have a segmented contact base (by filters, segments, or spreadsheet import) and want to call them all.

#### 6.2 From Companies

In the module **Companies**, select the desired companies and click on **Power Dialer** in the bottom bar:

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

In this flow, the system uses the contacts linked to each selected company to build the queue. Useful for B2B campaigns where you want to talk to all the contacts at the target companies.

#### 6.3 From Support Tickets

No **SAC 360°**, select the support tickets you want to turn into calls and click on **Power Dialer** in the bottom bar:

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

This path is ideal for active callbacks, follow-ups, and contacts that were left open in support — with one click you create a queue with all selected customers.

#### 6.4 From CRM Opportunities

No **CRM**, select the opportunities and click on **Power Dialer** in the actions bar:

<figure><img src="/files/150450859df4826ed50761fef68e4a43750ab3d7" alt=""><figcaption></figcaption></figure>

The system builds the queue with the contacts linked to the opportunities. Use it for sales actions focused on a stage of the funnel — for example, calling all opportunities in "Negotiation" or all leads from a specific campaign.

***

### 7. Best practices in day-to-day use

To get the most out of Power Dialer, consider these recommendations:

* **Standardize queue names.** Use a pattern like `[Type] - [Period]` (e.g.: `Prospecting - May/2026`) to easily locate campaigns.
* **Adjust the parallel quantity to the size of the team.** If there are 3 logged-in operators, setting 3 parallel calls makes use of all of them. If there is only 1, keep it at 1 so you don't miss calls.
* **Use the interval between calls strategically.** A short interval speeds up the campaign, but reduces the breathing room between calls. A longer interval is more comfortable for the team and improves conversation quality.
* **Take advantage of the operators.** Add all coworkers who can help run the queue — they see the same list and share the work.
* **Start queues from the right module.** Already have a filter ready in the CRM or a contact segment? Create the queue directly from there instead of selecting everything manually.
* **Keep track via the bottom bar.** Even while working on other screens, the execution bar keeps you aware of the queue's progress.

***

Done! With Power Dialer configured, your team gains agility and consistency in active calls, keeping all contacts, companies, support cases, and opportunities centralized in SprintHub.


---

# 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/power-dialer.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.
