Use Case
Stop your outbound caller IDs getting flagged as Spam Likely
Rotate DIDs the second a number trips a carrier spam threshold. Hold conn% above 50% week after week — without anyone watching the pool.
Weekly conn%
DIDs flagged per week
Manual DID swaps / week
The problem on a real floor
Monday morning your team launches a fresh campaign on four DIDs. By Wednesday afternoon Jio and Airtel have tagged two of them as 'Spam Likely' because of call-volume velocity. Conn% slides from 62% to 24%. By Friday it is 11% and the floor is half-idle. Nobody notices until the weekly review on Monday — five days of pipeline lost. The fix is not 'more DIDs'. The fix is rotation that happens the moment a number flips, not the moment a human notices.
The workflow
How VoIPSetu fixes it — step by step
Scroll down. Each step lights up as you reach it — the same way the workflow lights up on your floor.
- 1
Pool your DIDs by department
Caller ID Management → Department Assignment. Drop every DID into Sales, Collections or Support. Each pool has its own per-day call-count ceiling per number — set it once at 250–300 dials/day/DID and Jio/Airtel reputation scoring stays under the heuristic.
- 2
Watch Safe vs Flagged status live
Active Caller IDs board. Each DID is a green Safe tile or a red Flagged tile, with today's call count, longest streak, and last carrier-flag timestamp. No CDR export, no Excel filter — it's a wallboard.
- 3
Auto-rotate the instant a DID flips
The dialer holds a pointer to 'next Safe DID in this department's pool.' The moment a DID goes Flagged, the next outbound burst is stamped with the next Safe one. Zero agent action, zero supervisor click.
- 4
Cool flagged numbers down, don't burn them
Flagged DIDs sit in a 48–72 hour cool-down bucket. They are not deleted — they re-enter the pool clean, because the carrier reputation decays with silence. Most teams never have to buy a new DID again.
- 5
Prove the lift in the Hourly Dashboard
Hourly Dashboard → ASR / Conn% row. You see the rotation working hour by hour, not three days later. The story becomes 'conn% held flat through the carrier sweep' instead of 'the floor died and we don't know why'.
Which feature does what
The exact mapping
Every row is a feature already on your VoIPSetu console — and the precise job it does in this workflow.
| Feature | Role in this workflow |
|---|---|
| Department Assignment | Bucket DIDs by purpose so Sales velocity doesn't poison Support numbers. |
| Active Caller IDs board | Live red/green view — supervisor sees flags the moment they appear. |
| Auto-rotation pointer | Dialer always grabs the next Safe DID; flagged numbers cool down automatically. |
| Hourly Dashboard ASR | Hour-by-hour proof that rotation is holding connectivity. |
"Boss, we didn't lose Tuesday. The pool rotated, conn% held at 58%, and nobody on the floor even noticed."
In the wild
Real configurations on real floors. Names changed, numbers not.
Credit-card cross-sell · 40-seat outbound
Before
Week 1 conn% 62% → Week 2 11% (4 of 6 DIDs spam-tagged). Manager finds out Friday. 1,800 dials wasted.
After
Pool of 12 clean DIDs, 250-call daily ceiling each, auto-rotation on flag. Week-4 conn% 56%. Sales hold flat.
Insurance renewal · 18-agent campaign
Before
Customers swipe-block calls because numbers show 'Spam Likely'. Reach rate collapses to 9%.
After
Rotation keeps every DID under the per-day velocity heuristic. Reach steady at 47% through the renewal cycle.
Collections · regulated debt portfolio
Before
Compliance forbids buying random DIDs; existing 8 numbers stay flagged for weeks.
After
Cool-down bucket lets the same 8 numbers rotate back clean every 72 hours. No new DID purchases, conn% recovers.
The outcome
Conn% protected automatically. Caller-ID reputation managed by maths, not by a person watching a screen.
Try this on your floor
7-day trial. Full features. Cancel anytime.