How do I know if my dynamic phone number pool is too small?
Watch for session collisions. When more people are on the site at once than you have numbers, the platform recycles a number before the earlier visitor calls, and the call gets attributed to the wrong session. Symptoms include calls credited to campaigns that were not running, a sudden pile-up of calls on one keyword, and callers whose number was shown to several unrelated visitors that day.
How dynamic number insertion actually works
The platform holds a pool of phone numbers. When a visitor arrives, one number is checked out and displayed to that visitor, along with a record of their source, campaign and keyword. The number is held for that visitor for some window — often thirty minutes to a few hours — and then returned to the pool for reuse.
The attribution is entirely dependent on that hold. If the number is reassigned before the original visitor dials, the call arrives carrying the wrong story and nothing in the system flags it.
The sizing rule that matters
Pool size is not a function of daily traffic. It is a function of peak concurrent sessions multiplied by the hold window. A site with modest daily traffic that gets slammed for two hours after a storm, a cold snap or a television spot can exhaust a pool that looks generous on an average Tuesday.
Size for the peak hour of your worst week, not the average day. The whole point of call tracking in a home services business is to be right on the days that matter most, and those are precisely the days a small pool fails.
Symptoms you can check today
- Attribution to paused campaigns. Calls credited to a campaign that was not spending is a recycling signature.
- Improbable concentration. One keyword or one landing page suddenly collecting a disproportionate share of calls.
- Fallback number volume. Calls arriving on the static fallback number spike when the pool is dry.
- Number reuse history. Pull one call's number and look at how many distinct sessions saw it in the prior few hours.
The tradeoffs of a bigger pool
More numbers is not free of consequences. Numbers that sit unused can pick up spam-flagging reputations from carriers, local presence gets harder to maintain across many area codes, and there is real provisioning and maintenance overhead in keeping a large pool clean and correctly routed.
There is also a genuine tension in the hold window. A long hold protects the customer who writes the number down and calls the next morning; a short hold stretches a small pool further. Choose deliberately, and revisit it after any traffic step-change. Getting this right is the precondition for everything downstream in call analysis — a misattributed call produces a perfectly analyzed transcript credited to the wrong source.
Topics: call tracking · dni · number pool · diagnostics
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.