Phone Number Visibility Redesign — BluepointATM

Overview

During the January 14, 2026 strategy call, BluePoint ATM and Asymmetric identified that phone numbers were not consistently visible across the BluePoint website. Users who prefer to call rather than fill out a form had to hunt for contact information, creating friction in the lead generation flow. The agreed solution is to replicate the homepage "pool" phone number bar as a reusable template across all interior pages, while maintaining a clear hierarchy between local CallRail numbers and the generic 800 number.

Related meeting: ^[1]

Problem

• The homepage displays a prominent "pool" phone number bar (rotating through 4–5 tracked numbers) plus a number in the footer — two visible touchpoints.
• Interior pages (industry verticals, state pages, etc.) only show a phone number in the small-print footer, with no mid-page visibility.
• State pages are an exception: they feature a local CallRail number prominently in the hero image, but the generic 800 number also appears in the footer, creating potential confusion about which number to call.
• Users who are impatient with forms, or who distrust form submissions going to spam, have no easy path to call.

Agreed Solution

1. Replicate the Homepage Phone Bar Across All Pages

• The existing homepage "pool" bar is a self-contained container element.
• The developer (Ishak) will duplicate this container and apply it as a template across all interior pages.
• Default behavior: The bar uses the same pool of numbers as the homepage, requiring no per-page configuration.
• Optional customization: The copy inside the bar can be overridden per page (e.g., "Ready to elevate your Hospitality Solutions?") without breaking the shared template. This allows industry-specific messaging if BluePoint chooses to pursue it later.
• Mike Stebbins' preference: keep the bar generic unless there is a clear SEO or conversion reason to customize per page.

2. Phone Number Hierarchy on State Pages

State pages have a more nuanced requirement because they are designed to feel locally relevant:

• The generic 800 number should be moved to the footer only on state pages, so it does not compete with or confuse visitors who see the local number in the hero.
• Karly's recommendation: having the 800 number in the footer of a state page is harmless — visitors who scroll that far have already seen the local number at the top.

Implementation Notes

• Template approach: Build the bar as a global container so copy/image changes propagate to all pages simultaneously, rather than requiring edits to each page individually.
• State pages need 8 new CallRail numbers: Virginia and Colorado already have dedicated numbers. The remaining 8 states in the first build (New York, Pennsylvania, Illinois, Michigan, New Jersey, Washington, California, Florida) each need a CallRail number created before their pages go live. This is assigned to Melissa Cusumano.
• Contact Us page gap: The Contact Us page was noted as missing a phone number entirely. Mike Stebbins is responsible for adding it.
• Timing: Changes were flagged as easy to implement and appropriate to make during the current development sprint while state pages are actively being built.

Action Items

• [ ] Melissa Cusumano — Create 8 new CallRail numbers for NY, PA, IL, MI, NJ, WA, CA, FL and provide to developer
• [ ] Mike Stebbins — Add phone number to the Contact Us page
• [ ] Mike Stebbins / Wade Zirkle — Decide on final phone bar implementation (generic vs. page-specific copy) and communicate to Asymmetric
• [ ] Asymmetric dev (Ishak) — Duplicate homepage phone bar container and apply as template across all interior pages; move 800 number to footer-only on state pages

Related

• ^[2]
• ^[1]
• ^[3]
• ^[4]