Western Office — CallRail Static Number vs Pool Clarification
Overview
Wade reported that the Western Office website's CallRail number pool had not swapped in five days. After review, this was a non-issue: the Western Office site uses a static tracking number, not a dynamic number pool. No corrective action was required.
What Happened
Wade flagged the following: "Western Office website pool has not swapped in past five days."
The concern was that a dynamic number pool — which swaps the displayed phone number based on the visitor's traffic source — had stopped functioning. However, the Western Office site was never configured with a website pool. It uses a static tracking number, which by design does not swap.
The likely explanation is that a website pool was partially created at some point but never deployed to the site, causing it to appear idle or broken in the CallRail interface.
Resolution
No action needed. The static tracking number is functioning correctly. The site is tracking calls — the number is simply not being dynamically swapped, because that was never the intended configuration.
Key Distinction: Static Number vs. Number Pool
| Configuration | Behavior | Use Case |
|---|---|---|
| Static tracking number | Displays a fixed number; tracks all calls to that number | Sites where source attribution per-session is not needed |
| Website number pool | Dynamically swaps the displayed number per visitor session | Sites where you need to attribute calls to specific traffic sources (e.g., Google Ads vs. organic) |
For Western Office, a static number is the correct setup. If session-level source attribution becomes a requirement in the future, a website pool would need to be properly configured and the swap script deployed on the site.
Related
- [1] — Adavacare Karosh has a pending CallRail setup request (separate issue, same call)
- [2] — General call tracking practices