Pipeline

From the first dial to the issued policy

Leads, quotes, applications, and policies are records in Assurna, sitting in the same system as the calls that produced them. Not synced. Not exported nightly. The same system. That is the difference between a dialer with a notes field and a CRM that knows what a policy is, and it is why an agency running Assurna is replacing a stack rather than adding another window to it.

Book a demoSee pricing

The deals board: the floor's work by stage, from Quoted through Submitted and Approved to In-force, with the producer, the face amount, and the underwriting class on every card. Every surface on this page is drawn with sample data.

What changes on the floor

One record, and nothing to reconcile at the end of the week.

The pipeline is not a view bolted onto a dialer. It is the same records your agents dial, quote, and write business on, which is what makes the rest of it possible.

  • 01

    Stop re-keying the same prospect three times

    The lead your agent dialed is the lead they quote, the lead the application belongs to, and the lead the issued policy attaches to. Nobody retypes a prospect into a second system to move them forward, which is where the errors and the abandoned records come from.

  • 02

    Know what stage every deal is actually in

    The board shows the floor's work by stage, with the canonical stage labels the product uses rather than whatever an agent typed into a note. When a policy is in force, that is a state of the record, not a status someone remembered to update.

  • 03

    Get to a carrier fit without leaving the record

    Built-in multi-carrier comparison sits where the agent already is, on the lead, during or right after the conversation. The comparison is part of working the prospect rather than a detour into another tool while the prospect waits.

The objects

Insurance objects, not custom fields.

Most CRMs a telesales agency ends up on were built for a generic sales motion and then bent into shape with custom fields.

A policy becomes a text field. A carrier becomes a dropdown someone maintains. An application becomes a checkbox. It works until you need to report on it, at which point it does not.

  • Leads

    Worked in the same place they are dialed, carrying consent state, time zone, call history, recordings, and transcripts.

  • Quotes

    Produced from multi-carrier comparison and attached to the lead they were run for.

  • Applications

    Tracked as records with their own state, including the hand-off to the carrier.

  • Policies

    Including the issued and in-force states, tied back to the call that wrote the business.

Because these are real records, everything downstream is possible: reporting by producer, persistency that means something, and a chargeback you can trace to the conversation that produced it.

The lead is worked where it is dialed. The record carries the coverage requested, the source, the beneficiaries, the consent and calling-hours state, and the transcript of the call in progress, so nothing has to be retyped to move the prospect forward.

Quotes and applications

Quote inside Assurna. Apply at the carrier.

Two things happen between the conversation and the policy, and only one of them happens inside Assurna. We are going to be precise about which.

Multi-carrier quote comparison, built in.

Comparison across carriers is built into Assurna rather than being a tab your agent alt-tabs to. The agent works from the prospect's answers, sees options side by side, and stays on the record while they do it. The comparison, and the option the prospect chose, land on the lead.

No quoting vendor is named on this site. That is a deliberate policy across every surface, not an omission specific to this page: telephony, transcription, quoting, model, and e-application providers are all unnamed until a vendor grants written approval.

One record, first dial to issued policy

  1. Lead

    Worked in the same place it is dialed

  2. Dial

    Preview, power, or progressive

  3. Transcript

    Attached to the record, not to a vendor

  4. Quote

    Multi-carrier comparison, built in

  5. Application

    Handed off to the carrier's own application

  6. Policy

    Tied back to the call that wrote it

The application hands off to the carrier.

Assurna does not submit applications. When the agent and the prospect reach the application step, the process hands off to the carrier's own application. What Assurna does is keep the record: the application exists as a tracked state on the lead, the hand-off is a step in the lifecycle rather than a dead end, and when the policy issues it attaches back to the same lead and the same call.

Why say it that way rather than let it read as end-to-end submission: an agency owner will find out in week one, and a product that overstated its scope in the first week is a product they will not trust in month six. The value here is unbroken continuity of the record, not a claim to be the carrier's front end.

One system

The wedge, stated plainly.

Dialer vendors have no insurance objects. Agency management systems have no serious dialer. So agencies run both and pay for the seam.

The call sits in one system, the policy sits in the other, and a person in the middle keeps them agreeing. That person is a cost, and the reconciliation they do is the reason nobody trusts either report.

Assurna is one system from the first dial to the issued policy, which is why the compliance gate can sit in front of the dial, the transcript can hang off the conversation, and the persistency report can be built on the producer who made the call rather than on a spreadsheet reconciling two exports.

What the objects make measurable. Issued, in-force, persistency, NTO, and chargebacks are read off the same records the calls produced, which is the part an agency carrying advance commissions is actually buying.

Questions

What owners ask about the record.

If the answer you need is not here, bring the question to the demo call.

What does Assurna's pipeline actually track?
Leads, quotes, applications, and policies, as first-class records in the same system as the calls that produced them. Not as custom fields bolted onto a generic sales object, which is the arrangement most telesales agencies end up with and the reason their reporting never quite works.
Can agents quote inside Assurna?
Yes. Multi-carrier comparison is built in, so the agent runs it on the lead record without leaving the conversation, and the comparison and the selected option attach to the lead.
Can agents submit an application inside Assurna?
No, and we are not going to imply otherwise. The application step hands off to the carrier's own application. Assurna keeps the record: the application is a tracked state on the lead, and the issued policy attaches back to the same lead and the same call.
Which carriers are supported?
Carrier fit is scoped on the demo call, because it depends on your contracts and the lines you write. We do not publish a carrier list on this site, and we do not name the vendors behind any part of the product until they grant written approval.
Does Assurna replace my agency management system?
That is the intent. Dialer vendors have no insurance objects and agency management systems have no serious dialer, so agencies run both. Assurna is one system from the first dial to the issued policy, and it is built for final expense and term simplified-issue telesales specifically rather than for insurance in general.
Is this built for property and casualty?
No. Assurna is built for final expense and term simplified-issue telesales floors. If you write property and casualty, this is not your product and we will tell you that on the first call rather than the fourth.
Can I bring my existing leads and policies in?
Data migration is scoped on the demo call along with seats, lead sources, and calling rules, since what is possible depends on what you are coming from. Bring an export sample and we will look at it with you.
How do policies connect back to the calls that produced them?
Through the lead record, which is the spine of the whole thing. The call, the recording, the transcript, the quote, the application state, and the issued policy all hang off the same record, which is what makes producer-level persistency and chargeback reporting possible at all.
What does it cost?
Pricing is published rather than gated, which is unusual in this category. Individual agents have an entry price, agencies are priced per seat, and IMOs are scoped in a conversation. Telephony usage is metered and billed separately from the seat price. Modules including Compliance, Analytics, Contracting, and Training are configured and scoped in a conversation, and an agency can ask for one to be built.

Published pricing, including what is metered, is on the pricing page.

Related capabilities

Where this record comes from, and what it feeds.

The pipeline is the middle of the product rather than a corner of it, so each of these picks the argument up at a different point.

How many systems does one policy pass through at your agency?

Bring the stack you run now and the lines you write. We will show you the board on real screens and walk one lead from the dial to the hand-off.

Book a demo

Prefer to check the price first? See pricing.