> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brilo.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Control how fast a campaign dials
> Set max concurrent calls, a minimum gap between dials, and a daily call cap so a Brilo campaign paces itself instead of spending a month of minutes in one afternoon.
Three settings in **Concurrency & Pacing** decide how fast a campaign works through your list. They exist
for two reasons: your minutes are finite, and a list dialled all at once is both a bad experience for
whoever has to answer the callbacks and a good way to get a number flagged.
## Before you start
* A campaign with contacts. See [Add contacts to a campaign](/campaigns/add-contacts).
* Five minutes.
* Your plan's minute allowance and simultaneous call limit. See [Limits](/supported/limits).
* You will be working in the **Concurrency & Pacing** section of the campaign's **Settings** tab.
## Steps
Open the campaign, go to **Settings**, and expand **Concurrency & Pacing**.
This is the most useful of the three. It caps the most calls this campaign places in one day,
including follow up calls from later steps.
Set it deliberately low for a first run. A cap of 20 on day one tells you what your list is worth
before you commit the rest of your minutes to it.
The most calls this campaign places at the same time. Leave it blank for no campaign specific limit,
in which case your workspace limit still applies.
Set it below your workspace limit when you want to keep capacity free for inbound calls, which is
almost always the right thing to do during business hours.
Wait at least this long, in seconds, between consecutive dials. Leave it blank for no gap.
A gap of 10 to 30 seconds smooths a campaign out so calls trickle rather than burst.
Watch **placed today** against your cap on the **Contacts** tab. See
[Add contacts to a campaign](/campaigns/add-contacts).
## You will know it worked when
**placed today** stops at your daily cap rather than climbing to your list size, and inbound callers still
get through while the campaign is running.
## What each setting does
| Setting | Controls | Leave blank for | Set it when |
| ----------------------------- | ---------------------- | -------------------- | -------------------------------------- |
| **Calls per day** | Total dials in a day | No daily limit | Always. This is your minute protection |
| **Max concurrent calls** | Calls at the same time | Your workspace limit | You need capacity free for inbound |
| **Minimum gap between dials** | Seconds between dials | No gap | You want a steady trickle, not a burst |
## Working out a daily cap
Do the arithmetic before the campaign does it for you. Take your monthly minute allowance, subtract what
your inbound calls use, and divide what is left by your average campaign call length.
A worked example. You have 600 minutes on Pro, inbound uses about 300 a month, and your campaign calls
average 2 minutes:
* 300 minutes left, divided by 2 minutes, is about 150 campaign calls a month.
* Over 20 working days, that is roughly **7 calls a day**.
If that number feels too small for your list, the answer is a bigger plan or a shorter list, not a bigger
cap. See [What will this cost me](/account/what-will-this-cost-me) and
[What counts towards my usage](/account/what-counts-towards-my-usage).
## Leaving room for inbound calls
This is the mistake that costs real money. Your simultaneous call limit is shared: a campaign running at
full concurrency during business hours will take the capacity your actual customers need to reach you.
Set **Max concurrent calls** to roughly half your workspace limit if the campaign runs in business hours,
or narrow the calling window so the campaign runs when your phones are quiet. See
[How many calls at once](/calls/how-many-calls-at-once) and
[Choose when calls go out](/campaigns/choose-when-calls-go-out).
## Pacing protects your number too
A burst of calls from one number, especially to mobiles, is what carrier spam detection looks for. A
campaign that trickles is less likely to end up flagged than one that empties a list in twenty minutes,
and a flagged number stops working for everybody, including your inbound callers.
The same logic applies to text and email steps. See
[Add a text message step](/campaigns/text-message-step).
## What else you can do here
* Cap the length of each call as well as the number of them. See
[Limit how long a call runs](/calls/limit-how-long-a-call-runs).
* Stop calling contacts who will never convert, which saves more minutes than pacing does. See
[Stop calling a contact](/campaigns/stop-calling-a-contact).
* Narrow the hours instead of the volume. See
[Choose when calls go out](/campaigns/choose-when-calls-go-out).
## If it did not work
**The campaign is slower than your cap.** Something else is the bottleneck: the calling window, the
minimum gap, your workspace concurrency limit, or step delays. The tightest of them wins.
**placed today went past your cap.** The cap counts calls this campaign places. A contact in two campaigns
is counted by each one separately, so two campaigns with a cap of 20 can produce 40 calls to your list.
**Inbound callers get a busy line while the campaign runs.** Concurrency is being taken by the campaign.
Lower **Max concurrent calls** or move the campaign outside business hours.
**You cannot set concurrency above a certain number.** Your workspace limit is the ceiling. See
[Limits](/supported/limits).
**The campaign burned your minutes in one day.** There was no daily cap. Set one now, and check
[What counts towards my usage](/account/what-counts-towards-my-usage) to see where they went.
## FAQ
Set **Calls per day** in **Concurrency & Pacing** on the campaign's **Settings** tab. It caps the
total dials in a day, including follow up calls from later steps. Do this before your first big run.
Set a daily cap worked out from your allowance. Take your monthly minutes, subtract inbound usage,
divide by your average call length, and divide again by working days in the month.
It can, because the simultaneous call limit is shared. Set **Max concurrent calls** below your
workspace limit, or run the campaign outside your busy hours. See
[How many calls at once](/calls/how-many-calls-at-once).
Ten to thirty seconds if you want a steady trickle rather than a burst. Blank means no gap, which is
fine for small lists and worth avoiding on large ones.
Yes. It is the most calls the campaign places in one day, whichever step they come from, so a
sequence with two call steps shares one cap.
It helps. Carrier spam detection reacts to bursts of calls from one number, so trickling a list is
safer than emptying it. It is not a guarantee, and a flagged number affects inbound calls too.
They wait and are called the next day when the cap resets. Nothing is dropped because of pacing.
## Related
* [Choose when calls go out](/campaigns/choose-when-calls-go-out) for hours rather than volume
* [How many calls at once](/calls/how-many-calls-at-once) for the shared concurrency limit
* [What counts towards my usage](/account/what-counts-towards-my-usage) for where minutes go
* [Stop calling a contact](/campaigns/stop-calling-a-contact) to save minutes on lost causes
* [Limit how long a call runs](/calls/limit-how-long-a-call-runs) to cap each call