Screens fail in the report before they fail on the phone. AI call disposition insurance teams can trust uses five values and refuses to invent a sixth in the margin. Qualified means the rules you wrote all passed. Not qualified means a named rule failed. Incomplete means a required field never arrived because the caller hung up or refused. Callback booked means a calendar hold exists. Voicemail means an outbound attempt reached a recording, if you allow outbound at all. Those words are not a conversion rate and not an enrollment. They are how a supervisor tells a routing problem from a script problem. If two campaigns define qualified differently, do not add their counts together.
The disposition set and what each value is not
AI call disposition insurance values worth storing
Pick the five values and ban synonyms. AI call disposition insurance reporting breaks when one queue says qualified, another says transfer, and a third says good lead for the same event. Map every successful rule pass that is ready for a licensed agent to qualified. Map every rule failure to not qualified and require the rule name: wrong state, product not sold, caller not interested, outside the hours you will transfer, or whatever your compliance lead actually configured. Do not use not qualified for a hang-up. A hang-up before the rules could finish is incomplete. The distinction matters because a high incomplete count is a script or a length problem, while a high not-qualified count may be a media problem or a rule you wrote too tight.
Callback booked is not a soft qualified and not a loss. It means the caller still needs a licensed person and the calendar holds a time. Voicemail is only for an outbound attempt that reached a recording. Do not dispose an inbound caller who says they will call back as voicemail. That inbound promise is either a booked callback, if you took a time, or incomplete, if you did not. Mixing those labels makes the report praise a dialer setting when the real event was a shopper who refused a time. Write the definitions on the wall beside the monitor. New supervisors should be able to code a call from the transcript without asking what you meant in the kickoff.
- Qualified. Required rules passed and a licensed handoff is allowed.
- Not qualified. A named rule failed. Store the rule.
- Incomplete. The screen ended before required fields existed.
- Callback booked. A real calendar hold, not a vague promise to call later.
- Voicemail. Outbound only, and only when a recording was reached.
Qualified and not qualified need a reason, not a vibe
Qualified should be boring. The state is one you sell, the product matches the campaign, required fields are filled, and the caller agreed to a licensed next step. If any of those is missing, it is not qualified, even if the caller was friendly. Friendly is not a rule. Attach the field list to the disposition so the report can show which rule fired, not just the label. A qualified call that reaches an agent who immediately says we cannot help this state means the rule and the queue disagree. Fix the rule or the route. Do not add a disposition called qualified but wrong. That label becomes a junk drawer. The agent can correct the record, and QA can flag the AI, without a sixth bucket.
Not qualified should name the rule in a short code your report can group. Wrong state, no interest, existing client needing service, product mismatch, and caller asked for something you do not do are enough for most agencies. Do not encode a medical conclusion, a subsidy conclusion, or a best-plan conclusion as a disposition. The AI is not allowed to reach those conclusions, so the disposition must not pretend it did. A code called bad lead is useless because nobody can change the media or the script from that word. A code called ZIP outside footprint tells marketing to stop buying that ZIP and tells operations the rule worked. Store the code on the contact so a supervisor can filter one reason without a junk drawer.
Incomplete, callback booked, and voicemail are different events
Incomplete means you do not know whether the rules would have passed. The caller disconnected, refused a required field, or the audio failed before the profile finished. Report incomplete separately from not qualified so you do not train the team to tighten rules that never ran. If incomplete clusters on one question, that question is too long, too personal for the channel, or placed before the caller trusts the call. Shorten it or move it to the licensed agent. Do not keep asking it because a vendor wanted the field. A required field the AI cannot reliably collect is a design error. Marking those calls not qualified hides the error inside a rejection rate and invites the wrong fix.
Callback booked requires a timestamp on a calendar a human will honor. If the voice agent only says someone will call you, you do not have a booking. You have a promise with no owner, and the disposition should stay incomplete or a message outcome you track outside these five. Voicemail, when you use outbound, should record whether a message was left, under a script your compliance lead approved, and should never be counted as a conversation. Do not leave a message that quotes a premium or says the person is qualified for a plan. A voicemail is still your voice. If you are not running outbound, remove voicemail from the visible set so agents do not pick it by habit. Empty dispositions get clicked. Unused ones get misused.
How the five values make the daily report readable
A useful daily report is five counts by campaign, plus the top not-qualified reasons and the top missing fields on incomplete calls. That is enough to run a Tuesday. You do not need a blended quality score that averages a booking with a voicemail. You do not need a conversion rate the AI did not earn, because the AI did not sell. If leadership wants close rate, measure it on the licensed leg after a qualified disposition, and keep it off the AI row. Mixing them lets a good sales day excuse a screen that is transferring the wrong states. Publish the AI row as operations: qualified, not qualified, incomplete, booked, voicemail. Publish the sales row separately. The handoff between them is the warm transfer, not a shared vanity metric.
Outbound voicemail and outbound screening calls that use an artificial voice are not just rows on this report. They sit under the FCC guide to robocalls and robotexts guide and 47 U.S.C. § 227, with statutory damages of $500 per violation and up to $1,500 if a court finds the violation willful or knowing. A clean disposition file does not make those calls compliant, and this article will not pretend it does. Use the voicemail count to see volume. Use counsel and your consent process to decide whether that volume should exist. Inbound incomplete calls are a script problem. Outbound voicemail is a legal design problem. The same five words should not lull anyone into treating them as the same kind of work.
How AgentTech stores an AI call disposition insurance teams can filter
Qualification rules inside AI lead qualification write qualified or not qualified from the rules you configured, and they can book on the calendar when the outcome is a callback. AI receptionist uses the same idea on an inbound door: transfer, book, message, or end, mapped into this set so the report does not grow a second vocabulary. The contact keeps the reason code next to the transcript.
compliance scoring scores the call without replacing the disposition. A high score and a wrong-state code can both be true, and supervisors need both. AI voice agents passes the disposition to the agent screen on a warm transfer so the human sees why the call was marked qualified. The platform does not enroll, quote, or bind, and it does not turn these five labels into a compliance certificate. The $50 seat unlocks the voice. Minutes bill from the wallet.
Frequently Asked Questions
Can we add a disposition called sold?
Not on the AI screen. The AI does not enroll or bind. Sold, if you use it, belongs on the licensed agent leg after a real sale, in a separate report.
Is a hang-up the same as not qualified?
No. A hang-up before required fields are in is incomplete. Not qualified means a named rule failed. Mixing them hides a broken question inside a rejection count.
Does voicemail mean we left a compliant message?
No. Voicemail means a recording was reached on an outbound attempt. Message content, consent, and calling windows are a separate review under the FCC guide to robocalls and robotexts guide and 47 U.S.C. § 227. The disposition is not a legal pass.
Key Takeaways for Agency Operators
- Use five AI call disposition insurance values. Qualified, not qualified, incomplete, callback booked, voicemail.
- Store the rule on a rejection. A reason code is the point of not qualified.
- Do not call a hang-up a rejection. Incomplete means the rules never finished.
- A booking needs a calendar hold. A vague callback promise is not that disposition.
- Keep close rate off the AI row. The screen did not sell the policy.
Review how those labels show up in supervision of the AI calls themselves, and feed the qualified count into the screening cost worksheet only after the definition has sat still for a month. A moving definition makes both the QA and the math lie.
