Insights for Sales Leaders

There is a lot of "AI-powered" software in insurance right now, and a lot of it feels like the same pitch with different branding.

Add a chatbot. Add a note summary. Add a score. Add a copilot button. Add another tool. Hope your team uses it.

We think that is backwards.

If you run an agency or carrier operation in a regulated market, the question is not whether AI is exciting. The question is whether it helps your business work better on real days, with real agents, real members, real policies, and real compliance requirements on the line.

That starts with a simple truth: organizations do not adopt AI in the same way, and they do not all want software to work the same way either.

The right AI depends on how your team wants to work

Most of the industry puts agencies on a single spectrum from "getting started with AI" to "advanced AI team." That misses something important. A 500-seat call center with a sharp ops team might configure every routing rule, scoring threshold, and automation trigger on the platform, and never once talk to an AI. Under the single-spectrum model, they look like beginners. They are not. They just want AI to be invisible.

We think about AI in insurance and agency operations along two independent dimensions.

AI visibility: is AI invisible or fully interactive? On one end, AI works behind the scenes. It scores calls, ranks lead sources, flags compliance issues. Your team never interacts with it. On the other end, AI is something your team talks to. They ask questions, trigger actions, get answers.

Solution usage style: does your team take the defaults, or configure the system? Some teams want strong out-of-the-box experiences. Others want to design the rules, set the thresholds, and build workflows that match how their operation actually runs.

Those two dimensions create four identities.

The User does not think about AI. Compliance scoring runs automatically. Lead sources get ranked. Coaching flags show up. No settings page, just results. This is where most people inside an agency are: the agent making calls, the manager reviewing performance, the coordinator scheduling follow-ups. They do not need a relationship with AI. They need a platform that works.

The Navigator interacts with AI directly, but through served experiences. They ask the assistant about yesterday's call volume. They pull a report without building one. They get an answer from operational data without filing a ticket. The AI is visible and useful, but the Navigator is not configuring anything.

The Architect wants control over how AI operates. They design the scoring criteria, the routing logic, the coaching thresholds, the automation rules. Then they walk away and let the system execute. Platform power users, not AI power users.

The Builder wants full extensibility. They connect Claude, Manus, or custom tools to the platform via MCP and SDK. They build workflows that span multiple systems.

What matters is that these are not fixed labels.

Over time, nearly every agency will adopt AI in some form. What changes is how people want to use it. Some teams will start as Users and grow into Navigators or Architects. A smaller group will become Builders. And as the platform evolves, what requires a Builder today becomes accessible to a User tomorrow.

That pattern is not unique to AI. In enterprise software, there have always been teams that want strong defaults and teams that want more control. We expect the AI axis to move over time. We do not expect that core difference in usage style to disappear.

Our job is to be there for all styles today and support their journeys over the next few months and years.

AI only works if it sits on top of a real operating system

This is where a lot of AI products break down.

They can generate something interesting, but they are disconnected from the real operating system of the business. They do not understand the lead, the policy, the agent, the compliance workflow, or what happened on the last call. They are a layer, or a point solution, not a system.

That is not enough for insurance.

If AI is going to improve outcomes in a compliant and durable way, it has to sit on top of a platform that already understands the business. Every lead. Every policy. Every agent. Every call. Every compliance event. Every handoff.

That is how AI stops being a demo feature and starts becoming operational leverage.

A voice bot can only route well if it understands context and downstream ownership. A compliance reviewer is only useful if its output ties back to real workflows managers can act on. An SMS reviewer only matters if it is connected to the actual conversation history, permissions, and recordkeeping underneath it. An assistant only helps if it can answer questions from the real system your team runs on.

This is also why we think agencies and carriers should not have to choose between safe and useful. If the platform underneath is strong, you can have both.

AI should make the business better, not just make the product sound modern

We are building AI across that full spectrum. But the goal is not to shove AI into every corner of the product and hope customers adapt.

The goal is to help agencies and carriers get stronger in ways that actually matter. Better compliance. Faster decisions. Better coaching. Better use of agent time. Better follow-up. Better transfer logic. Better visibility.

Some customers want one strong default. Some want configurable systems. Some want to build with us. We are here for all of them, and for the teams that will move between them over time.

That is what "AI-powered" should mean: not more noise, not more disconnected features, but better business outcomes built on top of a platform that already knows how your operation works.

This is the reality of busy clients. They're picking up grandkids from school, getting to a physical therapy appointment, helping a neighbor with groceries, or finishing some garden work while the light's good. They still need coverage, and the coverage they need is often complicated: three specialists to keep, a drug list that has to line up, a spouse on a different plan. They're not avoiding the decision. They just have a whole life happening around it.

What they want is an agent they trust. Someone they can fire a quick text to with a question. Someone who texts back like a real person. Once they have that, they stay. That relationship is what turns a single enrollment into a client who renews year after year.

Phone-Only Loses the People Who Matter Most

The hard cases don't fit inside a single call, and a phone-only workflow turns them into phone tag. Your agent calls. Straight to voicemail. The member calls back while the agent is on another line. By the time they finally reconnect, the moment has passed, the kitchen table is covered in mail from competitors, and a member who would have been loyal for years drifts to whoever caught them at the right minute.

The agent didn't do anything wrong. The channel did. Phone calls are synchronous and life is not. Every missed connection is a round where the relationship isn't building, and on complex cases, that relationship is what decides whether the policy gets written and whether it sticks at next AEP.

What Texting Looks Like in a Real Case

Here's the same situation handled over text, between dials. The agent is on calls all afternoon. The member is out running errands. The thread might look like this:

Agent: Take your time. I'm waiting on a callback from Dr. Chen's office around 1pm to confirm she's in network. I already found her listed online but I want to double-check, I know how important she is to you.

Member: OK I'm out at the playground, I'll check my phone every 30 or 40 minutes. Just text me when you have an answer.

Agent: Hey, still working on it, should be soon. Sorry it's taking a bit, I'll text you the moment everything's confirmed.

Member: No rush, take the time you need. I really appreciate you checking.

Agent: All confirmed, she's in network. Want me to call you in the morning to walk through the plan and get you enrolled?

Member: Yes, 10am works. Thank you for being so kind.

Nothing dramatic happened. That's the point. The agent kept eight conversations like this alive in parallel between live dials, the member felt cared for instead of chased, and a complex case that would have died in voicemail closed the next morning.

The real payoff is what comes after. The number the member texted at enrollment is the same number they text when their drug gets dropped from formulary, when a confusing letter arrives from CMS, when a friend asks for a referral. The agent becomes their person. That's how a book of business compounds instead of churns.

How Onyx Texting Works

Onyx texting runs from an agent’s number tied to your agency, not their personal cell. Every message is logged against the member's record, so the relationship history is always there. Consent is captured live on the call through a built-in script before any text goes out, stored with a timestamp tied back to that call. If a member ever wants out, they reply STOP and Onyx handles the opt-out automatically. Your agents stay focused on the conversation. The compliance plumbing runs underneath.

The Bottom Line

Busy seniors with complicated needs are exactly the people who reward a trusted agent with years of loyalty. Give your agents a channel that fits the gaps in someone's day, and the retention builds itself.

Search for "best CRM for insurance agencies" and you'll find dozens of comparison articles. Most of them follow the same pattern: a CRM vendor publishes a ranked list and puts themselves at number one. The next vendor does the same thing. By the time you've read three of these, you've learned more about each company's marketing budget than about which insurance CRM software actually fits your agency.

Rankings don't help you make a decision. Questions do.

What to Actually Evaluate

The gap between a generic CRM and one built for insurance becomes obvious the moment you try to use it. Good insurance agency CRM software handles the full client journey from lead acquisition through enrollment and post-sale communication. It manages state licensing, records calls compliantly, and tracks policy data without forcing your team to copy information between systems. A generic CRM does contact management and pipeline tracking. Everything else requires add-ons, integrations, or workarounds.

When you're evaluating insurance CRM software, the questions that matter most are operational. Does the platform support compliant call recording and audit trails, or do you need a separate tool for that? Can it match agents to leads based on state licensing? Does it integrate with your dialer and lead sources, or does your team spend half the day switching between tabs? Is onboarding measured in days or months?

These aren't hypothetical concerns. They're the difference between a system your agents actually use and one they route around. We put together a full checklist of what to ask every technology vendor before you sign that covers integration, compliance, data ownership, and pricing transparency.

Why We Built Onyx Platform

We built Onyx Platform because we ran a large insurance agency ourselves and couldn't find an insurance broker CRM that worked without stitching together five or six tools. The deeper story of what we found and why we built Onyx Platform comes down to a simple observation: the best CRM for insurance agencies is one that was built by people who've actually run an insurance agency.

Skip the rankings. Start with the right questions, and the right answer becomes clear.

A prospect responds to a Facebook ad, gets transferred to your sales queue, and connects with an agent. The agent runs through disclaimer and qualifying questions, pulls up plan options, and starts building towards an enrollment. Ten minutes in, the prospect mentions they already have a policy. With your agency. Maybe they wanted to adjust coverage. Maybe they were just curious about a better rate. Either way, your sales agent just spent ten minutes on a call that should have gone to your service team.

This happens more often than most agencies realize, especially with lead vendors in the mix. A vendor buys a lead, matches it to your campaign, and passes a phone number through as an inbound transfer. Your system treats it like any other prospect call. But that phone number might already be in your CRM, attached to an active policy your agency wrote six months ago.

When that call goes through to a sales agent, a few things can happen, and none of them are good. The agent might enroll the policyholder into a new plan, churning a policy your agency already holds. That's not just a wasted sale. It damages your carrier metrics, costs valuable agent time, disrupts the customer's coverage, and costs the customer the continuity they had with their existing plan. Even when it doesn't end in a duplicate enrollment, the experience is bad and the agent leaves that conversation frustrated. A policyholder who calls in looking for help and gets a sales pitch instead feels like your agency doesn't know who they are. That's how you lose a customer to a competitor who will.

But there's a signal buried in this problem. If your policyholder is responding to marketing, they're shopping. They're looking at other options, wondering if they could do better. That's not a call to deflect. That's a call to act on.

Policyholder Detection That Works Before the Call Connects

The fix starts with data your CRM already has. When an inbound call arrives, the system performs a lookup across your lead records, person records, and alternative phone numbers. It's checking one question: does this caller have an active policy?

That lookup includes validation. A policy might be canceled, expired, or terminated. The system checks status, cancellation dates, and effective dates to confirm the caller is genuinely a current policyholder. The whole process completes in under 100 milliseconds, well before the call reaches an agent.

Once a policyholder is identified, you get three options depending on how you want to handle the call. You can redirect them to a dedicated service queue, keeping the relationship intact. You can reject the call, useful on high-volume acquisition campaigns where agent time is at a premium. Or you can accept the call normally but flag it, so the agent knows they're talking to an existing customer and managers get visibility into policyholder call volume on that campaign.

A Policyholder Shopping Around Is a Signal, Not a Problem

When a policyholder responds to marketing, they're telling you they're open to change. The question is whether your agency acts on that signal or lets it slip through to a sales queue where it becomes a churn risk.

A service team that receives the call with full context can ask the right questions. What prompted them to look? Is there a gap in their current coverage? Did their situation change? The conversation shifts from selling a new plan to protecting the relationship and adjusting what they already have. The customer gets the help they were actually looking for, your agency keeps the policy, and you avoid losing someone who was yours to begin with.

The configuration is flexible at the campaign level. Acquisition campaigns can filter strictly, keeping agents focused on new prospects. Service campaigns can route policyholders warmly. Mixed campaigns can flag and let agents decide. And the tracking data from every routing decision shows you which lead sources generate the most policyholder overlap, so you can tighten your targeting and stop paying for leads you can't convert.

Every Policyholder Call Is a Decision Point

Your CRM already knows who your policyholders are. The question is whether your call routing uses that data before the call connects. Every policyholder who lands in a sales queue is a retention risk, a wasted call, and a missed chance to strengthen a relationship that's already yours. If you want to see how policyholder routing works inside the Onyx Platform, reach out for a walkthrough.