Telecalling
Get a whole list of leads called — without losing track of who called whom, what happened, or who still needs a follow-up. A manager uploads the leads, splits them across the calling team, and hands each person a script to read and a short feedback form to fill in. Executives work their own call queue, log the outcome of every call, and schedule callbacks — while the manager watches progress and per-person performance in real time.
Calling is manual — Brixi doesn't auto-dial. Each lead's number is a tap-to-call link, so the executive places the call from their own phone and then logs what happened. That keeps setup simple: no dialer hardware or telephony account is needed to start.
Entry pointAutomation → Telecalling
| Section summary | Details |
|---|---|
| Best for | Sales teams running phone outreach over a list of leads. |
| Roles | Managers/admins build campaigns; calling executives work the queue. |
| Calling style | Manual — tap to call, then log the outcome. |
Start Here If…
- You manage a calling team. Begin with Set Up a Calling Campaign for Your Team, then Run and Adjust a Live Campaign to upload leads, assign them, and attach a script.
- You make the calls. Go straight to Work Your Call Queue — it covers your queue, the call workspace, and how to log each outcome.
- You write what the team says on the call. See Call Scripts.
- You track results. See Telecalling Reports.
How Telecalling Works
A telecalling campaign moves through five stages. The manager owns the first three; the executive owns the calling; everyone shares the results.
| Stage | Who | What happens |
|---|---|---|
| 1. Build the campaign | Manager | Name the campaign, set dates, and upload a leads file (CSV or Excel). |
| 2. Assign the work | Manager | Split the leads across executives by percentage. |
| 3. Prepare the call | Manager | Link a call script and, optionally, a call feedback form. |
| 4. Make the calls | Executive | Work the queue, tap to call, and log each outcome and any callback. |
| 5. Track results | Everyone | Watch calls, connections, and callbacks per campaign and per executive. |
Scripts live in a shared library, and the call feedback form is a normal Brixi Form. Build them once and reuse them across campaigns.
In This Section
| Article | What you do there |
|---|---|
| Set Up a Calling Campaign for Your Team | Use the step-by-step wizard to create a campaign, upload leads, assign executives, and publish. |
| Run and Adjust a Live Campaign | Upload more leads, re-assign work, link a script and feedback form, and move the campaign through its lifecycle. |
| Write the Script Your Team Reads | Write and edit the scripts your executives read on the call. |
| Work Your Call Queue | The executive's guide: call queue, call workspace, dispositions, callbacks, and feedback. |
| Track How Your Calling Team Is Doing | Campaign totals and per-executive performance. |
The Three Tabs
The Telecalling workspace has three tabs:
| Tab | What it shows |
|---|---|
| Campaigns | The list of telecalling campaigns, and the Create campaign button. |
| My Queue | The leads assigned to you to call. |
| Scripts | The shared script library. |
Calling executives land on My Queue by default and also see Scripts — they spend their day in the queue. Managers start on Campaigns.
Reports in This Section
Each campaign has a Reports tab with two views:
- Campaign totals — total leads, assigned, pending, called, and connected.
- Executive performance — leads assigned, leads called, calls made, and callbacks due, per person.
See Telecalling Reports for how to read them.
Troubleshooting
Most "telecalling is broken" reports turn out to be setup: a campaign left in Draft, leads not yet assigned, or a missing telecalling permission. If you can't see the Telecalling entry under Automation, or executives say their queue is empty, start with your admin or the campaign manager.
Reserve Brixi support for things that fail with correct setup — a published campaign whose leads never reach any queue, or tabs that won't load. Name the campaign and describe what you expected to happen, with a screenshot of any error.