BluePoint CallRail Misconfiguration — Homepage Phone Numbers

Overview

During the November 2025 BluePoint ATM marketing review, two non-working phone numbers were discovered on the homepage. The numbers change depending on the visitor's browser and cache state, indicating an active but misconfigured call-tracking implementation — most likely ^[1]. This is a live issue affecting inbound lead capture while paid advertising spend is active.

Symptoms

• Two broken numbers displayed: 540-253-1668 and a 720-xxx-xxxx number
• Browser/cache-dependent behavior: The number shown changes between a normal browser session and an incognito window, and again after clearing cookies and browsing history
• Neither number routes calls correctly

Wade Zirkle confirmed the behavior live on the call by clearing his browser cache and observing the number switch. Melissa Cusumano noted the same number (540-253-1668) appeared in both her normal and incognito sessions after the cache clear, suggesting the swap logic may be inconsistent.

Root Cause Assessment

The number-swapping behavior is consistent with a dynamic number insertion (DNI) script — the mechanism CallRail uses to swap a static phone number on a page with a tracking number based on traffic source or session. The likely failure modes are:

1. A CallRail tracking number was configured and injected via script, but the underlying pool or routing destination was never set up correctly or has since expired
2. A previous team member (possibly during the Chris Ron era) partially implemented CallRail without completing the routing configuration
3. The static number in the CMS (540-253-1668) is itself incorrect, and the DNI script is layering a second broken number on top of it

Temporary Fix Applied

During the call, Melissa Cusumano updated the homepage CMS to replace the static number with Mike Stebbins' direct number as a placeholder. This ensures at least one working number is visible to visitors while the CallRail configuration is investigated.

"Just, I hate to spend all this money on advertising and then have a phone number that doesn't work." — Wade Zirkle

Required Follow-Up

• Melissa / Mark Hope: Audit the CallRail account to identify which tracking numbers are assigned to the BluePoint property, verify routing destinations, and determine whether DNI is intentionally active
• Decision needed: Whether to keep CallRail DNI active (requires correct pool setup) or remove the script and use a single static number until a proper configuration is in place
• QA process: This issue highlights a gap in pre-launch QA. Future website edits should include cross-browser and incognito testing before client review, particularly for contact elements (phone numbers, forms, CTAs)

Related Context

• The garbled homepage copy ("The call us at ready to elevate your payment solutions with BluePoint ATM") was discovered in the same review session and fixed immediately by deleting the "The call us at" fragment — see ^[2]
• HubSpot lead sync issues discovered in the same meeting may compound the impact of missed calls — see ^[3]
• Mark Hope is the primary contact for CallRail configuration decisions at Asymmetric

Pattern Note

Misconfigured call-tracking DNI is a recurring risk when agency team members change mid-engagement. When a previous implementer sets up a tracking script without full documentation, the configuration becomes invisible to successors. Best practice: maintain a call-tracking configuration log per client documenting active tracking numbers, pool assignments, routing destinations, and the DNI script location in the CMS.