The GoHighLevel practice of Yotomations LLCAI development, custom software and websites at yotomations.com
New to GHL? Start here
Life insurance telesales case study

A multi-state GoHighLevel build for a life insurance telesales agency

A life insurance telesales agency inherited a GoHighLevel sub-account with broken Meta connections and no access to its old website, while its agents still dial every call by hand. The fix is a rebuilt account with one sub-account per licensed state, Voice AI, compliant texting and a path for selling leads to a downline.

Man in white button up shirt smiling

Watch the one-minute version

Multi-State Life Insurance Telesales Built in GoHighLevel

How a life insurance telesales agency rebuilt a broken GoHighLevel account into state-by-state sub-accounts with Voice AI, compliant texting, and downline lead sales.

Watch it on its own page, with the transcript.

How it fits together

State-by-state lead flowSTATE-BY-STATE LEAD FLOWMeta lead adsRe-authorized per stateLocation pagesNew site, one per stateInbound callsTracking number per stateState pipelineContact, tag, opportunityText-to-bookA2P registered, quiet hoursVoice AIAnswer, qualify, bookAgent call queueSmart list and tasksBooked appointmentReminders followDownline sub-accountLead sold via webhooknew leadform fillinboundfirst textbookscalendar linkcall tasklead for saleEach licensed state runs as its own sub-account built from one master snapshot.

At a glance

Client
A multi-state life insurance telesales agency in the US
Systems
GoHighLevel, Meta lead ads, Voice AI (inbound and outbound), SMS with A2P registration, Google Business Profiles, new website and domain, Stripe
Solution
One GoHighLevel sub-account per licensed state, each with its own location page, ad and Google connections, Voice AI, text-to-book workflows and a lead hand-off to downline agents
Services
Automation, AI agents, Integrations

The situation

The client sells life insurance by phone across several licensed states. The business is telesales, not storefront. In the owner's words, "We're more telesales." Their GoHighLevel sub-account was built and run by another agency, and it has since been transferred into the client's own agency account. The transfer moved the contacts and pipelines but not everything around them.

The Facebook and Meta ad connections did not survive the move, so lead forms no longer land in the CRM. The old domain and website are tied to logins the client cannot reach, which means there is no public site they control. Day to day, agents make outbound calls manually from lists. The owner said it plainly: "I don't know how to use the system."

They want a lot from the platform: inbound and outbound calling, Voice AI, mass texting, text-based appointment booking, and a way to sell leads to agents in their downline. They want it soon. "The sooner the better."

What made it hard

Four things stack on top of each other.

  • Lost connections. Meta lead forms and pages were authorized under the previous agency. Until the business owns the pages and the ad account connection in its own Business Manager, nothing flows into GoHighLevel.
  • No website or domain access. Location pages, tracking, A2P registration and review links all need a site the business controls. The old one is out of reach, so a new domain and site have to be built.
  • State-by-state rules. Licensing, contact types and calling rules differ by state. One flat account with one set of workflows would apply the wrong rules to some leads.
  • Compliance is not one thing. The client considers itself compliant already. A2P registration covers texting only. Outbound Voice AI and outbound calling need their own state-specific consent and calling-window handling, and that has to be built into the workflows rather than left to memory.

On top of that sits the people problem. A system nobody on the team understands becomes a rat's nest within months, which is how an account ends up in need of a cleanup. The build has to be simple enough for agents to use on day one.

The solution

The system is built as a structure first, then automation inside it.

One sub-account per licensed state

Each licensed state gets its own sub-account under the client's agency account. Each one holds that state's contacts, pipeline, calendars, phone numbers and workflows, so state rules live in one place instead of being checked by hand. A master snapshot carries the shared pipeline, custom fields and workflows, so adding a state means deploying the snapshot and changing the state-specific settings. The higher agency plan tier supports unlimited sub-accounts and users, and the client can upgrade within the agency account they already have. No new account is needed. The rollout is phased, starting with the highest-volume state.

Local presence on the web

Every sub-account gets its own location page on a new website, its own Facebook page and its own Google Business Profile. That supports local search and visibility in AI search answers, and it gives each state's ads and calls a clear home. The domain and DNS sit in the client's own registrar account this time, so access cannot be lost again. The site and text registration are the same work as our website and A2P 10DLC launch.

Leads in, with no manual entry

Meta is re-authorized from the business's own Business Manager inside each sub-account, and lead forms are re-pointed at it. A new lead creates a contact, tags the state, drops into the pipeline at New lead and fires a workflow. That workflow texts the lead inside a minute with a calendar link. When the lead picks a slot, the pipeline moves the opportunity to Appointment booked and a reminder sequence starts. If the lead replies with a question instead, the conversation is assigned to an agent.

Calling and Voice AI

Inbound calls reach a tracking number per state. Voice AI answers, confirms the caller's state and what they are looking for, and either books the appointment or transfers to a live agent. For outbound, agents work from a smart list and a call task queue instead of dialing from a spreadsheet. Outbound Voice AI is gated: a workflow checks a state custom field, a consent field and a calling-window condition before any AI call is placed. If a check fails, the contact routes to a human task instead. Texting follows the same logic, with A2P registered, quiet hours enforced and opt-outs honored across every sub-account. The same pattern is what we package as the AI front desk, and the agent behavior itself is covered under our AI voice and chat agent work.

Selling leads to the downline

The client wants to sell leads to agents in their downline. A workflow marks a lead as available, matches it to a buyer by state and licensing, and sends it into the buyer's own sub-account through a webhook into an inbound webhook trigger. The buyer works the lead in their own pipeline. Billing for lead purchases can run through Stripe from the same workflow. Because this crosses sub-accounts, it is a custom integration rather than a stock GoHighLevel feature, and it needs a clear consent and disclosure step before a lead is shared.

Built for people who do not know the system

Agents see a trimmed view: a few smart lists, one pipeline, and a dashboard showing today's calls and appointments. Short recorded walkthroughs cover the handful of daily actions. Everything else stays out of sight.

A build of this shape typically takes around three weeks per phase. Anything involving third-party APIs adds time.

Why this pattern fits businesses like this

Telesales teams live on speed and call volume, and both suffer when leads sit waiting for someone to dial. Putting the first text and the first call-handling step into a workflow means the lead gets a response even when every agent is on the phone. You can estimate what that delay costs with the speed to lead calculator.

Splitting by state matches how a licensed business actually operates. Rules, contact types and leads differ by location, and a sub-account per state makes the differences visible in the structure rather than buried in tags. It also makes phased rollout natural, since each state is an independent unit. We used a similar start-with-the-CRM approach in a CRM-first launch for a contractor with no online presence. As a certified GoHighLevel partner, we build this kind of structure directly inside the client's own agency account, so the client owns it.

Where it goes from here

After the first state is live, the same snapshot rolls out to the remaining states one at a time, followed by outbound Voice AI where each state's rules allow it. Later additions include reactivation campaigns to older contacts and per-buyer reporting for downline lead sales. If you run a telesales team and want a similar build, book a 30-minute call.

Yaakov (Koby) Oranski

Yaakov (Koby) Oranski, Founder and CEO of Yotomations

Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.

Published

Questions about this engagement

Why one sub-account per state instead of one account with tags?

Rules, contact types and leads differ by state, and a single account makes it easy to text or call someone under the wrong rules. Separate sub-accounts keep calendars, numbers, workflows and consent settings state-specific, and they let each state have its own location page and business profiles.

Does A2P registration cover Voice AI calls?

No. A2P 10DLC registration covers text messaging only. Outbound Voice AI and outbound calling need their own consent and calling-window handling, which varies by state, so those checks are built into the workflow that places the call.

Can lost Meta connections be restored after a sub-account transfer?

Yes, as long as the business owns its pages and ad account in its own Business Manager. We re-authorize Facebook inside each sub-account and re-point the lead forms so new leads create contacts and start the follow-up workflow again.

Do we need a new agency account to add more sub-accounts?

No. Moving to the higher plan tier within your existing agency account allows unlimited sub-accounts and users, so the upgrade does not require starting over.

More work

Have a similar problem?

Book a 30-minute call. We will tell you what we would do first and what it would cost.

No pitch deck. We look at your current setup and tell you what we would do and what it would cost.

Need more than GoHighLevel? Yotomations, our parent company, also builds AI agents, custom software and websites.