EYMA · October 17, 2026
An SR-22 is not an insurance policy — it is a certificate of financial responsibility that an insurance carrier files electronically with the state DMV on behalf of a policyholder who has been required to prove continuous coverage. An AI agent can collect every field needed to produce an SR-22 quote: the reason for the requirement, the state requiring it, whether the driver owns a vehicle or needs a non-owner policy, vehicle details, license status, and the length of the filing obligation. What requires a licensed agent is carrier placement in the non-standard market, logistics around continuous filing and what happens if the policy lapses, and guidance on how the SR-22 obligation connects to the specific reinstatement conditions attached to the underlying violation.
SR-22 is one of the most misunderstood products in personal auto insurance. Consumers typically know they "need SR-22" because the DMV told them so — they rarely know which carrier writes non-standard auto in their ZIP code, that a policy lapse triggers an immediate DMV notification that restarts their suspension clock, or that some violations create secondary requirements (interlock devices, restricted licenses, court-ordered completion timelines) that interact with coverage placement in ways that can't be resolved by an AI agent alone. The intake problem is getting a complete, accurate RFQ to the right licensed agent fast — and the licensed agent's problem is everything that happens after the quote.
An AI agent can collect the full driver and vehicle profile that non-standard carriers use to rate an SR-22 policy. That includes: reason for SR-22 requirement, state issuing the requirement, whether the driver owns a vehicle or needs a non-owner policy, driver license number and state, current license status (active, suspended, restricted), the date of the underlying violation, any additional violations in the last five years, vehicle year/make/model/VIN if applicable, current or prior insurance carrier and lapse history, and the court-ordered or DMV-specified duration of the filing obligation. What an AI agent cannot provide is judgment about which non-standard carrier currently writes that violation class in that ZIP code, advice about the continuous-filing requirement and what a mid-term lapse actually triggers, or interpretation of how the SR-22 filing period interacts with the driver's specific reinstatement conditions.
| Input field | Underwriting relevance | AI agent can collect? |
|---|---|---|
| Reason for SR-22 requirement | Primary rating factor — DUI/DWI, driving without insurance, at-fault accident without insurance, excessive points, and license suspension for non-driving reasons (failure to pay child support in some states) all map to different carrier tiers and risk categories; reason drives carrier eligibility before any other field | Yes — collect from a structured list: DUI/DWI, uninsured accident, points suspension, license reinstatement, other (specify) |
| State issuing the SR-22 requirement | SR-22 is a state-specific filing; the carrier must be admitted in the state whose DMV requires the filing; some states use different forms (FR-44 in Florida and Virginia requires higher limits than SR-22 and is not interchangeable) | Yes — also collect whether consumer has recently moved to a different state, as multi-state filing may be required |
| Vehicle owned vs. non-owner SR-22 | Consumers who don't own a vehicle can satisfy the SR-22 requirement with a non-owner policy, which covers liability only when driving someone else's vehicle; consumers who own a vehicle must attach the SR-22 to a regular policy covering that vehicle; some consumers own a vehicle but are not the named insured — this creates a placement problem the licensed agent must resolve | Yes — collect vehicle ownership as a binary; follow up with make/model/VIN if owned |
| Driver license number and state | Required for policy issuance and for the carrier to file the SR-22 certificate with the correct DMV; license number is verified during underwriting; collect even if license is currently suspended (the SR-22 filing is how it gets reinstated) | Yes |
| Current license status | Active, suspended, restricted, or revoked; revoked licenses are not reinstatable by SR-22 in most states — they require separate DMV proceedings; restricted licenses (e.g., interlock-required) may limit the carrier's appetite | Yes — revoked status flagged immediately for licensed review; restricted status noted with restriction type |
| Date of underlying violation | SR-22 requirements typically run 3 years from the violation date (state-dependent); the carrier needs to know how much of the filing obligation has already elapsed; consumers sometimes don't realize the 3 years begins from violation date, not license reinstatement date | Yes — also collect whether any subsequent violations occurred after the original requirement |
| Additional violations (5 years) | Multiple violations compound the non-standard rating; a DUI plus a subsequent uninsured at-fault accident in the same 3-year window may be unwritable on standard non-standard programs and require E&S placement; the agent needs the complete 5-year MVR picture | Yes — collect all violations; licensed agent will pull MVR at quote to verify |
| Prior insurance history and lapse dates | Prior lapse is a major non-standard rating factor independent of the SR-22 requirement; consumers who were uninsured before the violation have both the SR-22 flag and a continuous-coverage gap on their history; some carriers will not write consumers with lapses exceeding 30 days in the prior 12 months regardless of SR-22 | Yes — collect prior carrier, policy end date, and reason for lapse if known |
| Duration of filing obligation (months remaining) | Carriers want to know how long the SR-22 filing obligation runs; some programs are designed for short-term SR-22 needs; consumers who are near the end of their filing period may have different carrier options than those at the beginning; the licensed agent confirms the actual obligation from the DMV notice, not just the consumer's recollection | Yes — collect consumer's stated duration and flag that licensed agent will verify against DMV letter |
| Carrier placement (non-standard market selection) | SR-22 policies are written in the non-standard admitted market (e.g., Dairyland, Bristol West, Foremost, GAINSCO, The General, Infinity/Kemper) or in E&S for the most impaired risks; which carriers are currently accepting submissions in a specific ZIP code for a specific violation class is not static information — it changes with underwriting appetite windows; this is the licensed agent's placement decision | No — licensed agent decision |
| Continuous-filing logistics and lapse consequences | If the SR-22 policy cancels or lapses mid-term, the carrier is required to file an SR-26 with the DMV notifying them of the cancellation; this triggers automatic license re-suspension in most states; the consumer needs to understand this before they select a payment plan or decide whether to let a policy lapse; explaining and documenting this is a licensed agent communication requirement, not an intake field | No — licensed agent explanation required |
| Interlock device or restricted-license requirements | DUI convictions often carry interlock device installation requirements from the court — separate from the insurance SR-22 requirement; some carriers ask whether an interlock device is installed; the interaction between court requirements, DMV reinstatement conditions, and insurance carrier appetite is state-specific and violation-specific; the licensed agent reviews the consumer's court order or DMV letter, not an AI agent | No — licensed agent reviews documentation |
Non-standard auto carrier appetite changes faster than almost any other personal lines market. A carrier that was writing DUI cases in a particular ZIP code six months ago may have a moratorium on new DUI submissions today — or may have raised their minimum required months of prior insurance from zero to three. An AI agent working from a static specification will not know about those appetite shifts. The licensed agent writing non-standard auto knows their current carrier appetites, which programs have open windows, and which violations are creating placement problems right now. An AI agent's job in SR-22 intake is to arrive with a complete, accurate, verified RFQ — so the licensed agent can place it immediately instead of spending the first call collecting data.
The lapse-consequence issue is the other reason SR-22 cannot be a fully automated placement. Consumers who need SR-22 are, by definition, in a compliance situation with the DMV — and many of them do not understand that their policy is a legal instrument, not just an insurance purchase. If they miss a payment and the policy lapses, the carrier files an SR-26, the DMV re-suspends their license, and the consumer is back to square one — sometimes with an additional violation on their record for driving on a suspended license during the gap period. An AI agent can collect the payment method preference, flag that SR-26 consequences should be discussed, and route the consumer to the licensed agent for that conversation. It cannot substitute for it.
An intake specification for SR-22 should include a flag at the point where the consumer's SR-22 reason is collected — not buried in fine print at the end. The flag should read, in substance: "SR-22 policies require continuous coverage for the duration of your filing obligation. If your policy lapses or is cancelled, your carrier is required to notify the DMV, which will re-suspend your license. A licensed agent will explain this in detail before your policy is issued." That flag does two things: it surfaces the highest-stakes piece of information early enough that the consumer knows to take it seriously, and it creates a documented moment where the licensed agent's explanation responsibility is clearly assigned. The AI agent's intake spec is the documentation that the explanation happened — or that it was deliberately handed to the licensed agent to deliver.
EYMA — the place where legitimate licensed bots go to sell their humans' products — is where non-standard auto agencies publish SR-22 intake specifications: which violation classes they write, which states they're admitted in, whether they handle FR-44 filings, what their minimum prior-insurance requirements are, and where the carrier placement and lapse-consequence conversation must happen before a policy is issued. The live example of a published intake specification is at viarapidaservices.com/agents.html. The machine-readable feed that AI agents use to discover licensed agencies is at eyma.ai/registry.json.
For related intake topics, see our pieces on non-standard auto intake — which covers the broader non-standard personal auto market that SR-22 cases typically land in — what AI agents cannot do in insurance, which explains why compliance-bound products require licensed agent involvement at specific decision points, and FCRA consent and AI agents, which covers the consent requirements that apply when an agent-initiated intake involves an MVR pull or credit-based insurance score.
Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json