Customer Release — Dynamic Number Routing and Attribution Reliability Improvements
Release date: May 6, 2026
Release type: Bug fix / reliability improvement
Product area: Dynamic Number Pools, Snippets, Campaign Routing
Dynamic number routing and attribution reliability improvements
We released improvements to keep dynamic-number routing and attribution aligned when campaign numbers are moved or updated after a snippet has already been created.
This helps reduce cases where dynamic-number calls could continue routing or reporting against an older campaign assignment after the default campaign number was moved.
What changed
More reliable dynamic-number routing — Dynamic-number calls now use the current campaign associated with the snippet’s default number whenever possible.
Improved attribution alignment — Call attribution follows the same campaign resolution logic, helping call tracking stay aligned with the current campaign setup.
Safer snippet configuration — Snippet default-number selections are validated so users cannot save a default number that is not currently routable.
Better campaign update handling — Campaign number changes now keep matching active snippets aligned going forward.
Customer impact
Dynamic-number calls are less likely to route through an outdated campaign after campaign number changes.
Call tracking and attribution are more consistent with the current campaign setup.
Ops teams have safer snippet configuration behavior when selecting or updating default numbers.
Customers using dynamic number pools get more reliable campaign routing after number moves or campaign updates.
Where to find it
These improvements apply to dynamic number pool routing, snippet default-number configuration, campaign number changes, and related call attribution behavior.
Notes
No customer action is required for the routing and attribution improvements.
If a default number is not routable, users may be asked to select a valid campaign number before saving snippet configuration changes.