RC Inbound Lead Tracking.

Five intake channels, two CRMs, one human bottleneck.

RC was capturing leads from five places: the WordPress site, GHL inline forms on landing pages, Meta Lead Ads, a JF Acquisitions feed, and Fixr’s partner network. Sales lived in GHL; production lived in JobTread. The setter was the human router between everything — including the calls.

By 5pm a lead that came in at 11am was cold. The closers (Closer A (PA), Closer B (NJ)) were showing up to estimate appointments without context. Nobody could answer “which source converts.”

Five sources. Two systems. Zero shared shape.

• Five intake channels writing to four different schemas — no normalized view of “what is a lead.”
• GHL and JobTread weren’t talking. Anything that didn’t mirror between them showed up as a missed handoff a week later.
• First-touch was capped at the setter’s availability. After hours, weekends, lunch — leads aged.
• Compliance: A10DLC SMS rules, opt-out handling, do-not-contact propagation — all manual, all fragile.
• No funnel reporting. “Where do leads die?” had no real answer.

One contact shape. Voice AI as the front door. Ten automations behind it.

Every intake channel normalizes into a single GHL contact shape with source tagging. A Voice AI agent calls within five minutes, qualifies, and either books on Closer A or B’s calendar or hands the lead to a second Voice AI agent for the Day 2 / Day 4 / Day 7 follow-up rhythm. Behind that front door, nine more automations handle reminders, opt-outs, team notifications, and the bi-directional JobTread mirror.

System map

Ten production automations

Rendered as they appear in the GHL automation builder. Trigger sits at the top (dark), actions cascade below.

Stack

Key decisions

• One canonical contact shape, set at capture. Every channel — web form, Meta lead, JFA webhook, Fixr feed, inbound call — normalizes into the same custom-field set with a source tag before anything else fires. Every downstream automation assumes that shape, so each new integration is half a day instead of a week.
• Voice AI as the front door, not a fallback. Considered “page the setter first, AI on no-answer” — rejected. Setter availability was the bottleneck; making the AI the default opens the calendar to 24/7 lead arrival and frees the human team to close, not dial.
• Two Voice AI agents, two personalities. Agent A (Day 1) is energetic and book-or-die. Agent B (Days 2/4/7) is empathetic, respects contact fatigue, and routes to long-term nurture instead of pushing a third call. Two agents = clean handoff = no awkward “hi again, hi again, hi again.”
• JT mirror on qualify, not on creation. Only qualified leads create a JT job. Keeps JobTread from clogging with cold leads and keeps production looking at a list that’s 100% actionable.
• Disjoint stage ownership across the GHL ⇄ JT sync. Sales stages live in GHL, fulfillment stages live in JT, the sync writes one direction per stage. No loops, no fight-over-truth at 2am.
• Opt-out is one funnel, not one toggle per channel. “STOP” via SMS, “remove me” via Voice AI, manual DND in GHL — all collapse to the same Do-Not-Contact tag and the same campaign-removal action. A10DLC compliance becomes a property of the contact shape, not a per-workflow decision.
• Round-robin lives in Google Calendar. Closer A and B already kept their calendars there; the Voice AI checks both for availability and books the first open slot. No new tool for the closers to log into.
• Read-only scopes wherever possible. The note-sync cron and the funnel event log use read-only GHL scopes; only the automations that need to write hold write tokens. Smaller blast radius if a token leaks.

Four screens. One lead, end to end.

The Inbox (above) is where the lead lands and the auto-touches fire. From there it moves through four more screens — appointments out to the closers, the sales pipeline, production once it’s qualified into JobTread, and finally the value rollup that answers “which source actually converts.”

Under a minute to first message. The setter never sleeps.

Multipliers come from the sibling GHL Automation Scorecard project: self-booked appointment = 12 min, auto-reply = 3 min, contact captured via form = 3 min, follow-up step = 2 min. Stacked across RC’s monthly volume the system clears a meaningful chunk of setter time — the real unlock, though, is that Closer A and B now show up to estimate appointments with full context, and the team can finally answer “which source converts.”

What I’d do the same. What I’d do differently.

Keep: Centralize on one contact shape with a source tag before wiring anything downstream. Cheapest decision in the project; pays for itself the first time you add a new intake source (Fixr was a 90-minute integration).

Keep: Two Voice AI agents with distinct tones. Trying to do energetic-and-empathetic in one agent meant neither read true. Splitting them was a one-day refactor that doubled the callback rate.

Keep: Disjoint stage ownership across the JT sync. The boring version of bi-directional sync that doesn’t loop.

Change: Build the email + phone dedupe rule before launch. Two early leads created two JT jobs because the contact lookup was email-only and the lead used a different inbox on mobile.

Change: Write SMS copy like a person from day one. The first Day-1 auto-reply read like a workflow because it was a workflow.