Insights for Sales Leaders

Federal and state holidays carry outbound calling restrictions. Your dialer should know when they are and adjust automatically.

This morning, we reminded Onyx Platform customers that Martin Luther King Jr. Day dialing restrictions are in effect. We communicate proactively, but no action is needed from customers. The platform automatically applies restrictions in the states that require them. Onyx Platform will continue this for holidays in 2026 and beyond.

For a dialer, that should be unremarkable. Our customers switching to Onyx Platform told us that it is not.

Manual Processes Create Risk and Fatigue

Too many agencies still depend on someone to toggle dialing restrictions before a holiday. Maybe it's a calendar reminder. Maybe it's an email chain the night before. Maybe it's an ops manager waking up early to flip a switch. Every manual step is a chance for something to go wrong. That’s not the agency's responsibility: their dialer should handle this automatically.

Automatic Restrictions Are Table Stakes

A modern dialer should handle holiday restrictions without intervention. It knows the federal calendar. It knows state-specific rules. It applies them automatically.

This isn't a premium feature. It's baseline functionality for any platform serving regulated industries. If your dialer requires a workaround every time a holiday approaches, that's a sign the platform wasn't built with ease-of-use as a default.

The Bottom Line

Holiday calling restrictions are predictable. The dates are published far in advance. There's no reason for your team to manage them manually.

We believe your team has more valuable things to do than babysit a dialer's calendar awareness. If your platform didn't proactively handle restrictions this morning, it's worth asking what else it isn't handling for you.

Talk to us about what a good dialer actually looks like.

A call center script is a structured guide that keeps agents consistent on required steps while leaving room to respond naturally. In insurance sales, scripts do two jobs: ensure compliance with disclosure and consent requirements, and move conversations towards a sale.

When a script fails, you see it in three places: (1) agents skip required steps and trigger compliance violations, (2) agents have nowhere to capture information as customers share it so data gets lost or entered late, or (3) agents miss sales process guidance and calls drag on without converting. The result is high average handle time, low conversion, and compliance risk. Most script failures happen because the script tries to do only one job well.

What a call center script contains

Every script has two layers: hard requirements and suggested language.

Hard requirements are steps an agent cannot skip. In Medicare sales, this includes agent identification, recording consent, and required plan disclosures. These must happen in order and word for word. Your script should make them unavoidable, not optional.

Suggested language covers everything else: how to open the call, ask qualifying questions, handle objections. This layer gives agents words that work without locking them into reading verbatim. In sales, agents who sound like they're reading lose trust fast.

Scripts also need branching logic. A prospect switching Medicare Advantage plans needs a different path than someone aging into Medicare. Without branches, agents improvise, which means they sound robotic or abandon the script entirely.

Why most call center scripts fail

The most common failure: scripts written with compliance as a priority but never tested with real calls.

These scripts front-load every required disclosure before the agent establishes rapport. The prospect hears 90 seconds of legal language before anyone asks what they need. By the time the conversation starts, they've hung up.

The second failure is no branching. Linear scripts assume every call follows the same path. When agents hit questions the script doesn't cover, they freeze or answer incorrectly.

The third failure is format. A script in a Word doc or PDF works for basic calls but breaks down fast. Agents lose their place, skip sections, and enter data separately after the call. The script lives outside the workflow, so it competes with the work instead of guiding it.

How to build call center scripts agents actually follow

Start with compliance requirements as hard gates. Identify every step that must happen and make those non-negotiable checkpoints. The agent cannot proceed until the step is complete.

We built a “Read For Me” feature for verbatim steps. The system reads required disclosures aloud so agents don't have to. No paraphrasing errors, and agents don't burn out repeating the same sentences hundreds of times a day.

Add branching for common paths: new-to-Medicare, switching plans, adding coverage, not interested. Each branch gets its own qualifying questions and talk tracks. You don't need to cover every scenario, just the paths that represent 80% of calls.

Keep suggested language short. A sentence or two that works, not a paragraph to memorize.

The real difference comes from embedding scripts in the workflow. In Onyx Platform, the script branches automatically based on agent input. If the prospect says they have Medicare Advantage, the next screen shows switching questions. Person details entered during the call save directly to the CRM record. Policy information flows automatically once captured at enrollment. Dispositions pass through without extra steps and call history shows up on a customer’s detail page.

The setup is customizable by product and caller type. An inbound ACA call gets a different flow than an outbound Medicare prospecting call. But for agents, the experience stays consistent: structured guidance from initial needs discovery through enrollment, with every input captured as they go. No duplicate entry, no switching between systems, no lost data.

Scripts work when agents stop thinking about them

Call center scripts protect compliance and reduce ramp time for new agents. They work when they enforce required steps without forcing agents to read word-for-word. Build branching for common paths, keep language short, and embed the script in your workflow so data flows automatically. The best script is one your team follows without thinking about it.

If you want scripting with automatic branching, built-in data capture, and compliance features like “Read For Me” in one platform, reach out to Onyx for a walkthrough.

What does AHT mean in a call center? The AHT abbreviation stands for Average Handle Time: the average amount of time your team spends to complete a call from start to finish. It’s one of the most common call center operations metrics, but it’s only useful when you treat it like a diagnostic ratio—not a scorecard.

In insurance sales (such as Medicare, ACA/U65, and Life Insurance), AHT is especially easy to misread because one blended number often mixes revenue-producing sales conversations with non-sales work (wrong-fit leads, service calls, consent-only calls, etc.). This guide shows how to split AHT into the buckets that actually tell you what to fix.

What does AHT mean in a call center? AHT meaning + basic formula

The AHT meaning call center teams use is straightforward: it’s the total time agents spend handling calls divided by the number of calls they handled.

Common formula:

AHT = (Talk Time + Hold Time) ÷ (Total Calls Handled)

The most important thing for real-world comparisons:

Be explicit about what counts as “handle time.” Most teams include talk and hold time. Some companies also include after-call work. Including after-call work is useful to track the "complete time" it takes to handle a call. But we have found it more useful to exclude it from the AHT calculation as after-call processes are fundamentally different than what his happening while on a call with a consumer. We instead prefer to break out after-call work time separately and manage that metric separately. Decide what’s in scope and keep it consistent.

Quick example: if your agents spent 540 minutes on talk + hold across 90 handled calls, your AHT is 6 minutes.

AHT is a ratio, not a scorecard

Average Handle Time is best used as a signal of workflow efficiency. It helps you spot when agents are spending more (or less) time per call, and it points you toward where to investigate.

What AHT cannot tell you by itself:

• Whether calls were effective (conversion, appointment set rate, etc.)

• Whether calls were compliant (required disclosures, consent captured, etc.)

• Whether time spent was profitable (good long calls vs. bad long calls)

Once you can explain the AHT definition and formula, the next problem is interpretation: one blended number hides two very different businesses, so you need to separate them.

One blended AHT hides two different businesses: sales and non-sales

A single blended AHT often mixes conversations that deserve very different operational decisions.

Track these two AHTs separately by campaign and channel (e.g., inbound paid vs. outbound prospecting). If you use multiple call flows, also segment by script or intent (quotes vs. enrollments vs. service).

With the split visible, you can ask the operator-level question: are long calls producing value, or just absorbing licensed agent time?

Treat non-sales AHT as a capacity leak until proven otherwise

After isolating non-sales calls, decide which of that time is defensible by defining the outcomes that justify it.

• Desirable outcomes for non-sales calls: booked appointment, qualified transfer to enrollment, verified consent for future contact, corrected lead data that enables follow-up.

• Everything else is a capacity leak until you can show how it reliably leads to one of the outcomes above.

Common (fixable) causes of inflated non-sales AHT:

• Unclear intent from marketing creative or lead forms (the caller expected something else).

• Missing or inconsistent data at connect that forces repeated identity/consent steps.

• Agents trying to “rescue” bad-fit leads instead of dispositioning quickly.

• Repetitive verification because systems don’t share a single person record.

A clear plan to handle non-sales calls that is shared with agents can help reduce AHT. An effective strategy for a non-sale call can include:

1. Agent summarizes and sets the next action (transfer to service, schedule a callback, or end the call).

2. Agent applies a disposition that triggers follow-up actions like putting leads on do-not-contact lists, different campaigns, or e-mail journeys.

3. System routes salvageable cases away from licensed sellers (e.g., to a service queue or specialist) so licensed capacity stays focused on sales.

Lead intake and routing are usually the fastest way to reduce non-sales AHT. If you want to see how this is commonly automated, review Onyx Platform’s lead management features.

Shorter sales AHT comes from fewer repeats, not faster talking

With non-sales waste reduced, focus on sales calls that must convert. In practice, shorter successful sales calls come from removing repetition and decision friction—not from asking agents to talk faster or skip required disclosures.

Sales calls usually bloat for operational reasons:

• Repeated data entry across separate systems.

• Re-asking questions because information didn’t persist between screens or calls.

• Plan comparisons too early (benefits talk before basic qualification is finished).

• Long holds while agents search for plan details, provider/network info, or prior call notes.

A tight structure reduces pauses and repeats. A simple sequence:

1. Qualification first. Confirm eligibility and core needs in 2–3 targeted questions.

2. Product fit second. Match one likely product/category to the need rather than comparing everything immediately.

3. Enrollment steps last. Gather remaining data and complete consent/signature steps with a single, repeatable flow.

Use call reviews to coach micro-skills. Don’t coach “reduce AHT”; coach the exact step where calls stall (medication capture, provider lookup, SOA/consent timing, etc.). Then make one targeted change: a script tweak plus a focused drill.

When training closes those micro-gaps, AHT falls because agents repeat fewer actions and spend less time searching for missing information. The next bottleneck is usually the underlying workflow that forces agents to hunt across tools.

AHT improves when your workflow removes lookup work and dead-end calls

Durable AHT improvement typically comes from workflow alignment: the right information is available at the right time, and the call flow keeps agents out of dead ends.

Concrete levers you can pull:

• Contextual record display. Surface prior interactions, key data, and dispositions at connect so agents don’t restart the conversation. A unified person record is the foundation—see CRM capabilities.

• Script and disclosure alignment. Match script steps to data fields and compliance checks so required items happen in a predictable order. For regulated lines, call recording and monitoring should be built into the flow—see compliance tools.

• Routing and pre-qualification rules. Route by state license, product eligibility, and intent; send service/renewals to non-licensed queues; block leads missing consent or critical fields.

• Reduce avoidable holds. The faster agents can access the right queue, script, and caller context, the less time they spend placing callers on hold. Dialing operations (including inbound/outbound controls) also affect this—see dialer features.

Marketing also affects handle time. When ad messaging matches the script—and the lead form captures what you need—calls start in a qualified state and avoid long “orientation” segments.

Fixing workflow reduces lookup time and shrinks the number of dead-end conversations that pull licensed agents away from revenue-generating work. That sets up a measurement approach that protects conversion and compliance as you optimize AHT.

Use a simple measurement loop that protects conversion and compliance

Adopt a minimal cadence that prevents “chasing AHT” at the expense of outcomes or regulatory risk.

Track four numbers for sales and non-sales separately:

• AHT for the bucket.

• % of calls reaching a desirable outcome (booked appointment, verified consent, qualified transfer, etc.).

• Progression rate (transfer rate, appointment set rate, or enrollment initiation rate—whatever represents the next revenue-producing step for your model).

• Top dispositions by volume and by total minutes (volume × AHT) so you know which categories contain the most time.

If you need a place to operationalize those views, use reporting that can segment by campaign, script/intent, and disposition (see reporting and analytics).

Run a weekly 30-minute review with this agenda:

1. Pick the single disposition bucket with the highest total minutes (not just the highest AHT).

2. Listen to five representative calls and timestamp stall points (hold segments, repeated questions, long explanations, repeated verification).

3. Agree on one change: a script tweak, a routing rule, or a two-minute coaching action.

4. Monitor impact the following week and repeat with the next bucket.

Add guardrails:

• If AHT falls but desirable outcomes fall too, revert and test a more conservative change.

• If outcomes hold but compliance flags increase, freeze the change and run focused training on the steps involved.

These checks keep AHT improvements honest and ensure you’re not simply making calls shorter at the cost of revenue or regulatory exposure.

Conclusion

Average Handle Time is useful when you treat it as a diagnostic ratio rather than a scoreboard. Split AHT into sales and non-sales, stop non-sales capacity leaks, shorten sales calls by removing repeats, and remove lookup work with aligned workflow and routing.

Measure four focused metrics by bucket, run a weekly 30-minute review, and keep guardrails that protect conversion and compliance. Those steps turn AHT from a vanity number into an operational control you can actually change.

If you want help setting up AHT reporting by campaign and disposition—or aligning scripts, routing, and compliance checks so AHT drops without hurting conversion—contact Onyx Platform for a walkthrough: request a demo.

Compliance “by design” means building compliance checks into your daily call workflow. This allows you to catch issues early, document outcomes automatically, and prove what happened when a carrier or regulator asks. In this guide, you’ll learn a practical, four-step process for using AI to scale call reviews, reduce risk, and keep humans in control of final judgment.

At Onyx Platform, we’ve seen agencies improve speed and consistency by combining experienced compliance leadership with AI-assisted review. Our Compliance Suite is designed to support Compliance Officers and QA teams by automatically reviewing calls against an agency-defined scorecard, surfacing key moments with timestamps, and summarizing the evidence that supports each score—across thousands of sales calls.

Guiding principle: AI doesn’t remove judgment—it changes where you spend your time

Used well, AI doesn’t replace your compliance lead. It shifts their time from listening to hours of calls and assembling documentation to higher-value work such as:

• reviewing calls flagged by AI and jumping directly to the most relevant snippets,

• finding patterns across agents, campaigns, and scorecards (not just one-off misses), and

• coaching the behaviors that cause repeat failures to improve compliance performance.

This shift matters most during peak volume periods, when manual review often collapses into sampling and your risk concentrates in the calls nobody had time to fully review.

The 4-step process for “compliance by design” with AI

Step 1: Define (and maintain) your compliance scorecard

Whether your reviewer is human or AI, you need structured guidelines. Most agencies already have some version of this in scripts, SOPs, carrier requirements, or regulatory guidance. Turning those requirements into a clear scorecard is what makes consistent review possible. A strong scorecard is:

• unambiguous (pass/fail criteria are clear),

• auditable (each item can be supported by call evidence), and

• actionable (coaching and process updates naturally follow from results).

Example requirements many agencies include: stating the agent’s full name, confirming licensure in the caller’s state, and disclosing that the call is being recorded early in the conversation (timing and exact language depend on your rules).

Step 2: Automatically record and transcribe calls

Once your scorecard exists, you need reliable documentation. That typically means call recordings plus accurate transcriptions so reviewers can search, quote, and verify what occurred.

Storage and retention requirements vary by industry and carrier. In regulated programs (for example, Medicare-related sales), recordings often need to be retained for multiple years and be retrievable quickly. Onyx Platform automates recording and transcription as part of the workflow so teams aren’t stuck managing files manually.

If you’re evaluating tooling, start with the fundamentals—consistent capture, secure storage, and easy retrieval. Learn more about the platform’s capabilities on our dialer and compliance features pages.

Step 3: Have AI review, score, and cite evidence

AI review works best when it does more than output a number. The goal is to produce a score and the supporting trail: what was said, when it was said, and which scorecard item it maps to. In practice, an effective AI scoring workflow should provide:

• a score against each scorecard requirement,

• clear reasoning (why it passed/failed), and

• timestamp-backed references so a reviewer can jump straight to the relevant moment in the call.

This approach speeds review while improving defensibility—because you’re not just claiming compliance; you’re tying it to the specific evidence in the recording and transcript.

Step 4: Review exceptions, override when needed, and coach for prevention

At Onyx Platform we believe that humans should remain in control of outcomes. Your compliance team reviews the AI results, adds notes, and applies overrides when context requires it. The real operational win is what happens next: pattern-based coaching and process changes that prevent repeat issues.

With an exception-first workflow, compliance leaders spend less time on end-to-end listening and more time on:

• coaching agents on recurring misses,

• updating scorecards and playbooks when requirements shift, and

• responding to carrier or complaint requests with a fast, timestamped evidence packet.

Why compliance by design works for small and midsize agencies

Small and midsize agencies don’t have unlimited QA headcount—and they can’t pause production every time requirements change. When call volume spikes, manual review becomes a throughput problem: reviewers either fall behind or narrow their sampling.

An AI-powered first pass reduces the number of calls that require a full listen-through, so your compliance lead can focus on work that actually lowers risk over time.

Next step: see how it fits your workflow

If you want a concrete example of what this looks like inside a call workflow, explore our Compliance Suite. To connect compliance outcomes to operational visibility (who is failing what, in which campaign, and whether it’s improving), review our reporting and analytics.

If you’d like to map your current process to an AI-assisted review workflow (including scorecard design, recording/transcription, exception handling, and reporting), contact our team for a walkthrough: request a demo.