Lead Quality & Targeting Review — Reynolds Transfer

Overview

Internal review between Ben San Fratello and Mark Hope on April 5, 2026, covering two Reynolds issues that surfaced the same week: a reported call whisper anomaly and a pattern of economically unfeasible move inquiries. Both were investigated and resolved or triaged before the next scheduled client call.

Issue 1: Incorrect Call Whisper

Problem

The Reynolds client reported receiving at least one inbound call where the whisper prompt said "This is a call from Asymmetric" — suggesting a mislabeled or misconfigured tracking number.

Investigation

• Reviewed phone number configuration in GoHighLevel: the number in use matched the forwarding number active in Google Ads.
• No CallRail setup exists for Reynolds, so the whisper would have originated from GoHighLevel's call tracking.
• All assets on landing pages reviewed — numbers appeared correct.
• The specific call was identified in GoHighLevel conversation history; it appeared to be a single isolated incident.

Conclusion

Assessed as user error / isolated incident — likely a caller who dialed the wrong number or clicked the wrong link. No systemic misconfiguration was found. Ben will monitor for recurrence; if the issue repeats, escalate for deeper investigation.

Issue 2: Lead Quality — Unfeasible Move Inquiries

Problem

Reynolds received inquiries for moves that were not economically viable given their service area (e.g., Green Bay to Kravitz). The client flagged this ahead of the next scheduled call.

Root Cause

Upon reviewing the Google Ads location targeting settings, two compounding problems were found:

1. Dane County exclusion bug: The account was configured to target the entire state of Wisconsin while excluding Dane County — the opposite of the intended setup. This had been in place for an unknown period of time.
2. Overly broad radius: Even with the exclusion corrected, a 50-mile radius around Dane County may still be wider than the client's actual service area.

Immediate Fix

Ben removed the Dane County exclusion. The account now targets a 50-mile radius around Dane County as originally intended, which should eliminate calls from distant markets like Green Bay.

⚠️ The Dane County exclusion error was not disclosed to the client. The fix was framed as a targeting refinement ahead of the next call.

Long-Term Plan

Replace the radius-based targeting with a client-provided zip code list for tighter, more precise control. Zip code targeting allows a non-uniform service area that better reflects where Reynolds can realistically operate.

Proposed next step: Ask the client on the next call whether they have a list of zip codes they service. If yes, implement zip targeting and remove the radius. If no, confirm whether 50 miles around Dane County is appropriate or needs adjustment.

Key Decisions

Action Items

• [ ] Ben: Contact Reynolds client to confirm service area; request zip code list if available (@Ben San Fratello)
• [ ] Ben: Implement zip code targeting in Google Ads if client provides list; otherwise confirm 50-mile radius is acceptable (@Ben San Fratello)
• [ ] Ben: Review all recent Reynolds changes before next scheduled client call (@Ben San Fratello)
• [ ] Ben: Monitor for any recurrence of the call whisper issue (@Ben San Fratello)

Related

• ^[1]
• ^[2]