Decide what the test needs to answer
An insurance call test should answer a specific buying question: can your team turn this source, in these states and hours, into customers at an acquisition cost your business can support? A billable call, an application and a retained customer are different outcomes. Counting them separately makes a small test more useful.
Before starting, write down the insurance product, source, agreed call model, participating agents, approved states, answering hours and maximum spend. Use the applicable dated offer for rates and billability. A 90-second threshold is a billing condition; it does not prove consumer eligibility, a sale or profitability.
Keep a simple call-level scorecard
Download the free call-test scorecard (CSV). It opens in common spreadsheet tools. Keep your completed copy private. Use a non-identifying reference to reconcile each row with your authorized call records; do not put consumer names, phone numbers, health information or recording links in a shared worksheet.
| Stage | What to record | What it tells you |
|---|---|---|
| Delivered | A call offered to your configured destination in the authoritative log | Delivery volume; it is not proof of a live answer |
| Answered | A verified live agent answer, separately from voicemail or a failed connection | Whether the team could serve the opportunity |
| Billable | The agreement-specific billing decision and any adjustment | What you owe under that agreement |
| Application | A submitted application in your authorized records | An intermediate sales outcome |
| Issued and placed | Each stage separately, using your carrier or agency definitions | Progress beyond application, subject to later changes |
| Collected and retained | Commission actually received, with reversals and chargebacks reconciled later | The observed financial outcome for that cohort |
Calculate the rates with consistent denominators
Net call spend means confirmed billable call charges less confirmed credits or adjustments. It is not the number of delivered calls multiplied by an assumed rate. Keep prepaid funds that have not been consumed separate from the cost of calls in the cohort.
- Billable rate per delivered call: confirmed billable calls divided by delivered calls. Compare delivered, live-answered and billable counts side by side. Flag calls billed without a verified live answer for agreement-specific review; an anomaly alone does not establish a credit owed.
- Live-answer rate: verified live answers divided by delivered calls.
- Application rate per live answer: submitted applications divided by verified live answers.
- Cost per placed policy: net call spend divided by placed policies. Also show a fully loaded figure including attributable labor and other acquisition costs.
- Observed contribution: collected commission, less reversals, net call spend and attributable variable costs. This excludes fixed overhead unless you explicitly include it.
If a denominator is zero, mark the rate as not available. If a cost or outcome is missing, mark it unknown instead of entering zero. Keep the original call cohort together: do not divide this week's applications by a different week's calls.
For a purely illustrative example, a test with 30 delivered calls and 24 verified live answers has an 80% live-answer rate. These are hypothetical counts, not RingFunnel results or a suggested test size. Answering rate alone says nothing about profitability.
Review operations before judging the source
If live answers are low, review destination settings, staffed hours, simultaneous-call capacity, voicemail and pause confirmations. Separate a call that never reached the intended destination from one that reached a live agent but did not produce an application. Keep supporting evidence and submit any review within the agreement's window.
If live answers are healthy but applications are low, review fit, agent handling and the original source or handoff. Do not infer a cause from one call. Where possible, keep states, hours and agent assignment comparable when testing a change. A small uncontrolled comparison can suggest the next question; it rarely proves one vendor is better.
Set review and stop rules before spending
Choose an operational checkpoint and a later financial checkpoint. At the first, confirm delivery and answering work and reconcile billing. At the later checkpoint, allow time for policy status and commission records to mature. The right timing depends on your product and records; there is no universal number of days that makes the result final.
Write down when to pause for a routing failure, when to ask for a billing review, and what evidence would justify another capped test. Do not keep increasing spend simply to make an unfavorable sample look better. A positive early result still needs confirmation as more outcomes mature.
Make the next decision specific
End the review with one decision, an owner and a date: repair an answering issue, clarify a disputed definition, test one source change, repeat under comparable conditions, or stop. Your scorecard supports a review; it does not rewrite your agreement.
For preparation, use our call-vendor evaluation guide, compare inbound calls and live transfers, and review pricing and billability questions. When you are ready to discuss program fit, book a conversation with RingFunnel. Availability and commercial terms require confirmation.