Outbound Capacity Calculator
Work out how many contacts an outbound call campaign can reach: dial attempts, calls per hour, days to finish and the concurrency you need.
An outbound capacity calculator estimates how many contacts a call campaign can reach, and how long it takes, from the list size, attempts per contact, calling window, call lengths, connect rate and concurrent calls. Enter your own numbers in the calculator below. Nothing is prefilled, because your connect rate and call length are yours, not an industry average.
Enter your own numbers. Every rate here is yours: the tool ships with no defaults and no benchmarks.
Fill in the fields to see results.
- Total dial attempts
- -
- Connected conversations
- -
- Contacts never reached
- -
- Talk minutes
- -
- Calls per hour at your concurrency
- -
- Working days to work the list
- -
- Concurrency needed to finish in your target
- -
- Talk minutes x your per-minute rate
- -
Expected values from your inputs, with every line busy for the whole calling window. Delays between retries, calls-per-second limits and time zones are not modeled, so a real campaign takes at least this long.
How to read the results
- Total dial attempts is the list size times the average attempts each contact gets. With "stop dialing after a connected call" ticked, a contact who answers gets no more dials, so the total is lower than contacts times attempts.
- Connected conversations and contacts never reached split the list by your connect rate across all attempts.
- Talk minutes is connected conversations times your average call length. Type a per-minute rate to turn it into a cost line. The tool has no price built in.
- Calls per hour is what your concurrent lines can place when each dial holds a line for its average time, ringing included.
- Working days to work the list divides the total line time by your concurrency and calling window.
- Concurrency needed is the number of lines that finish the same work inside your target.
These are expected values with every line busy for the whole window. Treat the days figure as a floor. This is outbound math: it sizes lines against a list. To staff people for inbound calls against a service level target, use the Erlang C calculator.
What sets outbound throughput
| Lever | What it changes | What it does not change |
|---|---|---|
| Concurrency | Calls per hour and days to finish, in direct proportion | How many people answer |
| Attempts per contact | Contacts reached, total dials and talk minutes | Calls per hour |
| Calling window | Dialing hours per day, so days to finish | Total dials |
| Ring time | Line time spent on calls nobody answers | Talk minutes |
Unanswered dials are short, but there are many of them. In a campaign where most dials ring out, ring time can take a large share of your line-hours, which is why this calculator asks for it.
Retries add a second limit that concurrency cannot remove. If your attempts are spaced days apart, the campaign cannot finish before the last attempt is due, however many lines you have.
Running the plan in the Retell AI Dialer
The Retell AI Dialer runs campaigns as a sequence of attempts with delays, inside a calling window set in each contact's time zone. According to the Retell docs, read on November 16, 2026:
- A contact moves to the next attempt only when the current one goes unanswered, which matches the calculator's default.
- With Double dial on, an unanswered dial gets a second dial right away as part of the same attempt. Count it as two attempts here.
- Campaign calls share the outbound part of your workspace concurrency limit. When no slot is free, the call waits and the contact does not lose an attempt.
- An attempt that comes due outside the calling window waits for the next opening.
- The Dialer's own Live estimates panel leaves out ringing time, retries and later sequence steps. This calculator includes ring time and retries.
Your concurrency limit and calls-per-second limit are set per workspace. Compare the "call starts per second" figure under calls per hour with your limit before you launch.
What the calculator leaves out
It does not model retry delays, calls-per-second caps, voicemail, callbacks, or lists spread across time zones. It also assumes the same connect rate on every attempt. It does not check calling-hour or do-not-call rules: those stay your responsibility. For how AI dialers work, see the AI dialer glossary entry, and for a campaign built on retries, see appointment reminder calls.





