This guide is for sellers who want fewer rejected posts and fewer returns on their car insurance leads. It covers the fields buyers commonly ask for, how buyers test the answers, validation, consent records and duplicates. Summit currently works with web leads (form fills), not calls or live transfers.
Key points
- Buyers judge quality by results per source: contact rateContact rateThe share of leads a buyer or its client actually reaches by phone, text or email. Glossary, quote rate and policies written.
- Answers must agree with each other. A driver age that does not fit a licensed driver is a red flag.
- Validate phone, email and address before the post, and keep a consent certificateConsent certificateA record, often produced by a third-party consent certificate provider, that shows how and when a consumer gave consent on a web form. Glossary for every lead.
- Remove repeat submissions from the same driver before you post them.
How buyers measure auto insurance lead quality
An auto buyer does not grade a lead when it arrives. It grades your source after it has worked a batch of your leads. Most buyers track four numbers for each source: how many drivers they reached, how many they quoted, how many policies they wrote, and how many leads they returned.
Each of those numbers ties back to something on your side. Wrong numbers lower the contact rate. Missing or wrong answers lower the quote rate. Drivers who never asked for a quote lower everything. When a source falls behind a buyer's other sources, the buyer lowers its bid or stops buying from it.
Fields buyers commonly ask for
The fields below are industry information: what auto buyers commonly ask sellers to collect. They are not a fixed list. Each buyer sets its own required fields and filters.
| Field | What the buyer does with it | Common problem |
|---|---|---|
| ZIP code and street address | Sets the state, the rating territory and the carriers the agent can quote. | A ZIP that does not match the city or state. |
| Vehicles: year, make, model | Each vehicle is rated on its own. | Free-text entries such as "car" or a model year in the future. |
| Drivers and birth dates or age ranges | Driver age is a main rating factor. | An age too young for a license, or the same date for every driver. |
| Currently insured, current carrier, months insured | Prior coverage affects price and which carriers accept the driver. | Left on a default answer the driver never chose. |
| Policy expiration date | Tells the agent when the driver is free to switch. | A date in the past, or a date years away. |
| Accidents, tickets, DUI, SR-22 need | Separates standard from non-standard drivers. | Question skipped, so every driver looks standard. |
| Homeowner or renter | Flags bundling prospects for agencies that write home and auto. | Asked in a way that confuses owning the home with owning the car. |
Which fields and filters apply to your leads is agreed with each buyer. When you sell through Summit, it is agreed during onboarding.
Answers that agree with each other
Buyers look for answers that contradict each other, because contradictions point to careless entry, bots or incentivized form fills. Run the same checks on your side before you post:
- Every driver age fits a person who can hold a license.
- Vehicle years fall inside a real range, and make and model come from a list, not free text.
- A driver marked "not currently insuredCurrently insuredA lead field that records whether the consumer has an active policy for the line they are shopping, sometimes with how long it has been in force. Glossary" has no current carrier filled in.
- The policy expiration date is in the future and within a policy term.
- The ZIP code, city and state match, and the IP location is plausible for that ZIP.
Do not pre-select answers. A form that defaults to "currently insured: yes" or "no accidents" produces leads that look standard until the agent calls. Those leads come back as returns.
Validation before you post
Validation checks that the contact data is real and the lead came from a person. Run it between the form and the post, so a bad lead is stopped before a buyer pays for it.
Phone
Check the format, whether the number is in service, and the line type. Some buyers filterFilterA rule that decides which leads a buyer is offered, based on fields such as vertical, sub-type, state, ZIP code, homeownership or accident details. Glossary on mobile or landline.
Email
Check the format and that the domain accepts mail.
Name and address
Reject placeholder names and standardize the address so it matches postal records.
Behavior
Flag forms completed faster than a person can read them, repeated submissions from one device, and traffic from hosting networks.
See lead validation for how these checks work, and fake leads and lead fraud for the patterns buyers watch for.
Consent records
Auto buyers call and text drivers, often with dialing software. The federal Telephone Consumer Protection Act (47 U.S.C. 227) and the FCC's rules (47 CFR 64.1200) set consent requirements for many of those calls and texts. A buyer will not use a lead it cannot tie to a consent record.
Show the consent language next to the submit button. It should say who may contact the driver, about what, and by which channels. Store a certificate for each lead with the exact language shown, the timestamp, the IP address and the page URL, and send the certificate reference with the post.
The FCC one-to-one consentOne-to-one consentAn FCC rule adopted in 2023 that would have limited each prior express written consent to a single seller. Glossary rule was vacated by the Eleventh Circuit on January 24, 2025 (Insurance Marketing Coalition v. FCC) before it took effect, and the FCC removed it from its rules in August 2025. Buyers may still set their own requirements for how consent names them. See prior express written consent, TCPA consent record-keeping and insurance lead consent and documentation. This page is not legal advice; have counsel review your consent language.
Duplicates
A duplicate is a driver a buyer has already received. Auto shoppers often submit a form twice: once on a phone and again on a laptop, or again the next day to change an answer. If you post both, the buyer pays twice for one driver.
- Repeat submissions on your forms. Match on phone number and email over a lookback window, and post only the first lead or the corrected one.
- The same driver from two of your sources. Deduplicate across all your forms, not form by form.
- A driver the buyer already bought elsewhere. You cannot see other sellers' leads, but buyers may reject these under their terms. Ask each buyer how its duplicate rule works.
Buyers set their own lookback windows. For why duplicates happen and how to prevent them, see duplicate leads.
Track quality by traffic source
Tag every lead with its traffic source and sub ID, and keep that tag with the lead's sold status and any return. When one source produces most of the returns, fix or stop that source instead of lowering the quality of your whole feed. Buyers notice when a seller can show results by source.
Common mistakes
- Optimizing for form completions alone. Removing questions to raise completions lowers the number of buyers each lead can match.
- Defaulted answers. Pre-selected "currently insured" or "no violations" answers create returns.
- Consent text that changes without a record. Keep every version of your consent language with the dates it was live.
- Validating after the post. A bad lead stopped at your form costs nothing. The same lead returned by a buyer costs you a return and lowers your bids.
- Treating crash victims as quote leads. A driver asking about an injury claim belongs on an MVA form. See what are MVA leads and MVA leads vs auto insurance leads.
Frequently asked questions
Should a car insurance quote form pre-select answers?
No. Defaults such as "currently insured: yes" record answers the driver never gave, and buyers return the leads when the call shows otherwise.
Is a driver who submits two auto quote forms in one day a duplicate?
Usually, yes. Post one lead per driver within your lookback window, and keep the most complete version.
What should an auto insurance consent certificate include?
The exact consent language shown, the timestamp, the IP address and the page URL, stored so you can retrieve it by lead.
How do auto buyers spot incentivized or bot form fills?
They look for answers that contradict each other, forms completed too fast, repeated devices and low contact rates from one source.
Related guides
Sources
- 47 U.S.C. 227, Restrictions on use of telephone equipment, Legal Information Institute, Cornell Law Schoollaw.cornell.edu
- 47 CFR 64.1200, Delivery restrictions, Electronic Code of Federal Regulationsecfr.gov
Generating insurance leads?
Email us your insurance lines, traffic sources, how consent is captured, and daily volume. Summit currently works with web leads (form fills), not calls or live transfers.
Or write to team@summitleads.ai. We reply by email.
What happens next
- Step 1: You email us.
- Step 2: We reply by email.
Buying insurance leads instead? See insurance leads for agents.