Fresh leads move from first dial to qualified human handoff, with each call result written back to the CRM.

Linda's Care did not need another place to store leads. It needed a dependable route from a new enquiry to a qualified conversation - without asking a growing calling team to absorb every first dial, retry and CRM update.

Evidence at publication: 60-70 leads could arrive over a weekend; the client reported an $800 deal in the first week of use; the production bridge and its supporting services were verified live on 30 May 2026.

The company

Haroon Kamal runs Linda's Care, a Pennsylvania home-care agency. Its paid-media funnel was already producing demand, with Meta advertising reported at roughly $200-$300 per day and new enquiries landing in GoHighLevel.

The operating challenge sat between acquisition and sales. Caregiver prospects needed a quick first conversation about working hours, pay, insurance, benefits and readiness to transfer. A human closer remained valuable when a prospect was qualified. The repeated work required to find that qualified prospect was consuming the team's capacity.

The constraint

A weekend could produce 60-70 new leads, while hundreds of older leads had been contacted only once. Manual callers first had to work through bad numbers, no-answers and voicemail before reaching someone ready to talk. The process was repetitive, but its timing mattered: local competitors were following up with the same pool of caregivers.

The cost was not simply call volume. It was the combination of delayed response, inconsistent retries, qualification notes spread across calls and a CRM record that still depended on a person completing every step correctly.

Why existing tools were not enough

GoHighLevel held the lead. Telnyx could carry a call. ElevenLabs could conduct a conversation. None of those tools, by itself, defined Linda's Care's operating policy.

The missing layer had to decide which leads were eligible, respect business hours and per-phone time zones, follow accepted and disqualified insurance logic, collect structured answers, recover stale calls, stop retrying after terminal outcomes, preserve recordings and transcripts, and transfer a qualified person to the right human number. That is workflow design, not another software subscription.

Transformation map

Before

Meta lead -> GoHighLevel -> manual list review -> manual dial -> handwritten or inconsistent notes -> manual retry -> human closer

The information existed, but a person carried it across each boundary.

After

Eligible GHL lead -> governed queue -> AI call -> structured disposition -> GHL fields and transcript -> retry or qualified transfer -> human closer

The human decision point is preserved. The system prepares and routes the conversation; it does not pretend that a consequential care-services sale should close without a person.

One workflow, end to end

1. Input: An eligible lead enters GoHighLevel. The bridge filters the record before it reaches the calling queue.
2. Queue control: Business hours, phone time zone, priority, previous attempts and stop conditions are checked before a dial starts.
3. Conversation: ElevenLabs runs Linda's Care's approved qualification script while Telnyx provides the local calling route.
4. Structured result: The system captures qualification score, hours, pay rate, insurance, benefits, disposition and summary rather than leaving the outcome in an unstructured call recording.
5. Human gate: A qualified conversation is transferred sequentially to Haroon's phones. The human closer owns the sales conversation and exceptions.
6. Recovery path: No-answer and voicemail outcomes enter governed retry logic; terminal outcomes stop further attempts.
7. Record: Signed post-call webhooks write the transcript note, recording URL, called-at field and transfer status into GoHighLevel.

What changed

• Built: A dedicated Node/TypeScript voice bridge, retry queue, transfer handoff tracking, recording proxy, dashboard surfaces and reconciliation controls.
• Connected: ElevenLabs Conversational AI, Telnyx SIP, GoHighLevel and a local 610 caller ID.
• Tested: Webhook signatures, service health, queue state, CRM field writes, recording handling, retry controls and transfer routes were inspected in the production environment.
• Verified live: On 30 May 2026, the haroon-ai-bridge service and Caddy were active, the local health endpoint returned OK and production environment wiring was present.
• Actively used: The client reported a closed deal during the first week of use.
• Provider or client dependency remaining: No unresolved dependency is asserted in the retained source. Configuration and deployment state remain subject to the quarterly revalidation applied to every featured case.
• Financial result reported by client: Haroon reported closing an $800 deal in the first week. This is a client-reported result, not an independently audited revenue claim or a promise of future performance.

Proof

• Operating volume: 60-70 leads could arrive over a weekend.
• Deployment receipt: Production service, HTTPS layer, health route and environment wiring verified on 30 May 2026.
• System receipt: The live bridge exposed call launch, webhook, recording, transfer, queue, retry, reconciliation and dashboard functions.
• Client-reported outcome: One $800 deal closed in the first week of use.

Technology - revealed last

The production stack uses ElevenLabs Conversational AI, Telnyx SIP trunking, GoHighLevel, a Hetzner-hosted Node/TypeScript bridge, Caddy HTTPS and systemd supervision. HMAC-secured webhooks and a signed recording proxy protect call records. State for the queue, GHL polling and transfer handoffs persists on the server. The design keeps qualification logic, retry policy and CRM records in a controlled operating layer rather than scattering them across provider dashboards.

Client quote

No source-backed verbatim client quote is published for this case. The evidence retained for publication is the verified deployment record and the explicitly attributed first-week result; RECAST does not turn a paraphrase into quotation marks.

Next transformation

See how Care Networks separated live recruitment operations from a staged voice-automation lane. It addresses a related coordination problem in healthcare recruitment while preserving different data, approval and outreach rules.

Get your AI blueprint

If lead response is consuming skilled sales capacity, the right first step is to map the qualification rules, human handoff and evidence trail before choosing a voice provider. Book a free AI audit and leave with a verbal plan followed by a written blueprint.

Source record

• OPENCLAW-DEEP-CLIENT-CASE-STUDIES.pdf, page 4.
• RECAST_CASE_STUDIES_2026_UPDATED.pdf, page 2, document RA-CASES-001, version 2.0.
• RECAST_WEBSITE_MASTER_BLUEPRINT.md, sections 10.4, 11 and 58.