Number reputation & guardrails

A vishing campaign dials targets from a phone number your tenant owns. If too many calls go out from one number too quickly, or from a number that was just provisioned, carriers and call-screening apps flag it as "Spam Likely," which tanks answer rates and burns the number's long-term usefulness. Callstrike protects this automatically: every number has a per-hour and per-day call cap, freshly provisioned numbers warm up gradually instead of starting at full volume, and the campaign builder explains the pacing in plain language before you launch. You don't configure any of this; it's enforced server-side and surfaced for transparency, not as a setting to tune.

Prerequisites

• A campaign with at least one audience country resolved to a callable number (see Phone numbers and Target audience).
• Country-compliance gating already applies to the same call, number-reputation pacing runs on top of it, never instead of it. A call blocked by country rules is never "paced in." See Country compliance.

How to use it

There's no separate reputation-guardrails screen, the guardrails show up inline wherever a number and a schedule come together in the builder:

1. Target Audience (Step 3): if your selected audience is approaching or over a country's number capacity, an "Approaching number capacity" card appears, showing <eligible> / <capacity> callable per country and a Rent a number link. This is a warn-only, non-blocking heads-up.
2. Call Settings → Your Numbers (Step 4): each audience country shows its resolved caller number, a status pill (Active or Warming up N days), and an inline pace read-out: "≈ N days to reach everyone", or "Won't fit the window" with an overflow count and a rent another → link if the audience can't clear at the current cap within the campaign's window. A number still warming up shows "trickling while it warms up" under the estimate.
3. Call Settings → Dialing pace (Step 4): a Recommended vs Aggressive toggle. Aggressive raises the per-number daily/hourly ceiling (more reach, sooner) and shows a "Higher spam-flag risk" warning when selected. Warm-up on fresh numbers is never bypassed by either mode.
4. Campaign Summary: the Distribution card restates the schedule and, when the real paced estimate differs from a naive read of the window, adds a note that calls are paced "so your numbers aren't flagged as spam."
5. At launch and during dispatch, nothing further is required; calls are scheduled under the cap automatically, and if a call's number is unexpectedly at its rolling cap when it's due to dial, the platform reschedules it to the next available in-window slot rather than failing it.

Configuration & options

Reputation caps are global defaults managed by Callstrike (configured via environment settings rather than a self-serve control):

Setting	Default	What it does
Steady-state day cap	50 calls/day	Ceiling for a fully-warmed number under Recommended pacing.
Steady-state hour cap	10 calls/hour	Rolling 60-minute ceiling under Recommended pacing.
Aggressive day cap	150 calls/day	Raised ceiling a number ramps toward under Aggressive pacing.
Aggressive hour cap	30 calls/hour	Rolling 60-minute ceiling under Aggressive pacing.
Warm-up window	14 days	A number's effective cap ramps linearly from a low trickle on day 0 up to the full steady/aggressive cap by day 14, based on the number's provisioning date.
Dialing pace	Recommended	Per-campaign choice (Recommended / Aggressive) in Call Settings; selects which steady cap the warm-up ramp climbs toward. Warm-up itself is never skipped.

The effective cap for a number at any moment is steady cap × min(1, (age_days + 1) / warmup_days) for the day cap, and min(steady hour cap, effective day cap) for the hour cap, so a number is never given an hourly allowance bigger than what its current daily allowance would support.

Gotchas & limitations

• The cap is per number, shared across campaigns. If two campaigns use the same number (only possible serially, see below), the rolling-window count includes calls from both. You can't get more throughput by splitting one big campaign into two smaller ones on the same number.
• A number can't be assigned to two active campaigns at once. Assigning a number already held by another non-completed vishing or callback campaign is rejected outright ("A selected number is already in use in another campaign."). The per-number cap's cross-campaign protection mainly matters for serial reuse, campaign A completes, frees the number, campaign B launches while A's last-hour/day calls still weigh on the number's rolling window.
• Aggressive pacing raises the ceiling, not the warm-up. A brand-new number still trickles up over the 14-day warm-up window even under Aggressive, only the steady-state target it's ramping toward is higher.
• Overflow is surfaced, not dropped. If an audience can't fully clear within the campaign's scheduling window even at the effective cap, the builder shows "Won't fit the window" with the overflow count and a link to rent another number ; it never silently truncates the target list.
• A due call can be deferred, not failed. If a scheduled call's number happens to be at its rolling cap right when dispatch fires, the call is rescheduled to the next in-window slot instead of erroring or dropping. This is a backstop for edge cases (e.g. concurrent scheduling); it shouldn't happen often if the build-time pacing is working correctly.
• This is additive to country compliance, not a replacement. A call that's blocked by country-compliance rules is filtered out before pacing ever sees it; the cap/pacing logic only ever orders calls that are already legally permitted.

Best practices

• Treat the Recommended pacing mode as the default; only switch to Aggressive when you specifically need higher daily reach and accept the higher spam-flag risk the builder warns about.
• If Step 4 shows "Won't fit the window" or the Step 3 capacity card shows a country over capacity, either extend the campaign's scheduling window, rent an additional number for that country, or trim the audience, the platform tells you which countries are affected and links straight to renting a number.
• Expect a freshly rented number to show "Warming up N days" and a slower "≈ N days to reach everyone" estimate for its first two weeks; this is expected and protects the number; it isn't a bug or a misconfiguration.

Troubleshooting / FAQ

Why is my campaign spread over more days than I expected? The number's effective per-hour/per-day cap, not the fixed spacing you might remember from before, determines how many calls can go out per window. A large audience on one number, especially a fresh one still warming up, gets paced across more days so the number's cap is never exceeded.

Why does a number show "Warming up"? It was provisioned within the last 14 days. Its effective cap ramps up linearly from a low trickle toward the full steady-state cap over that window; after day 14 it dials at full capacity like any other number.

Can I raise or override the per-number cap myself? Not in the product today, caps are global backend defaults. The only per-campaign control is the Recommended/Aggressive Dialing pace toggle, which changes the steady-state target the warm-up ramp climbs toward.

A call I scheduled didn't go out at its exact time, is something broken? If the assigned number happened to be at its rolling cap at that moment, the call is deferred to the next available in-window slot rather than dropped or failed. It will still go out, just slightly later.

Related

• Phone numbers
• Target audience
• Create and launch
• Country compliance
• Campaigns overview