Automotive Lead Parser for the Leads Your CRM Never Sees

At 9:40 on a Sunday night a buyer asks whether the silver Tacoma is still on the lot. The message comes through Facebook Marketplace, so your CRM never hears about it. Monday at 10:15 somebody reads it, retypes the name and the number, and dials. He has already sat in two other trucks.

That is not a slow response. That is a lead nobody was told about.

An automotive lead parser reads that message the second it lands and writes the buyer, his number and the truck he asked about into your CRM as a structured record. Nobody retypes anything, and nothing sits in an inbox over a weekend.

Key Takeaways

  • An automotive lead parser reads buyer name, phone, email and vehicle of interest out of lead emails and delivers them to your CRM or spreadsheet as structured records, with no manual entry.
  • If every lead you get already arrives as clean ADF XML, your CRM is doing this job and you do not need a parser.
  • The gap is Facebook Marketplace, Craigslist, your own website form, and provider XML that turns up half empty. Foureyes found 14.1% of new sales leads never get logged in a dealer CRM at all.
  • There is no template to build for any of it. The AI reads what a message means instead of where the text sits, so a provider redesigning its notification email breaks nothing. Leads land in your CRM, Google Sheets or any app through Zapier, Make or a webhook.
  • Free plan, 20 pages a month, no card.
  • Parseur does not replace your CRM. It fills it, while the buyer is still looking at the listing.

What ADF Already Handles, and Where It Stops

ADF (Auto-lead Data Format) is the XML standard US dealer CRMs use to ingest internet leads. Cars.com, Autotrader, CarGurus, Dealer.com and TrueCar all send leads to your CRM's ADF intake address in that format, and VinSolutions, DealerSocket, eLead, CDK and Reynolds all read it. If that describes every lead you get, the job is done and you are already paying for it. Nobody needs to sell you a parser.

ADF only ever covered the tidy half of the lead inbox. Five gaps it leaves open:

  1. Sources that never send ADF. Facebook Marketplace, Craigslist replies, the cheap chat widget, the contact form somebody's nephew built, a forwarded Instagram message. It all arrives as ordinary email written in ordinary English. Text-in leads count too, as long as your texting platform emails you a copy.
  2. Stores with no ADF intake at all. Plenty of independent lots run a spreadsheet, or a general-purpose CRM with no lead capture address to hand a provider in the first place.
  3. ADF that shows up broken or half empty. Smaller providers emit malformed XML, or drop the vehicle of interest, the trade-in and the financing note into a free-text comments block where no CRM field ever picks them up. The lead reaches the CRM. The useful part of it does not.
  4. Everything downstream. ADF puts a lead into one system and stops. Not the GM's Google Sheet, not the Slack channel your BDC watches after hours, not the attribution report nobody trusts.
  5. Dealership email nobody ever standardized. Floorplan notices, auction results, trade appraisal requests, title and registration paperwork, wholesale offers. Same retyping, no standard, and no CRM vendor with the slightest interest in fixing it.

That is the half of the lead inbox Parseur is built for, which is the half your CRM was never going to catch on its own.

Every Field Parseur Pulls Out of a Car Lead Email

Whatever the source puts in the message, Parseur pulls out of it. These are the fields dealers map first.

Field Example value Where it usually hides Typical CRM field
Buyer name Marcus Webb Subject line, or the opening line Contact name
Phone number (614) 555 0182 Signature, or typed into the body Primary phone
Email address [email protected] Reply-to header or contact block Email
Vehicle of interest 2021 Toyota Tacoma SR5 Listing title, or the buyer's words Vehicle of interest
VIN 3TMCZ5AN4MM123456 Listing footer VIN
Stock number U24187 Listing reference line Stock number
Listing price $34,995 Listing block Asking price
Trade-in mentioned 2014 Civic, 118k miles Free text, mid message Trade notes
Financing question Asking about approval Free text, mid message Lead comments
Lead source Facebook Marketplace Sender domain or footer Lead source
Received time 2026-09-06 21:40 Email header Received date

A screen capture of automotive parsed data
Your automotive lead data has been extracted!

Where the Lead Data Lands

Structured lead data is only worth something once it is somewhere else.

Destination What Parseur delivers How
Your CRM, dealer or general purpose Buyer and vehicle fields, under your own field names Webhook, or the automation platform your store already runs
Salesforce A lead or contact object Direct integration
HubSpot A contact with lead source set Direct integration
Google Sheets One row per buyer Direct integration
Excel, CSV or JSON A file of the whole batch Download
Any other app Custom payload Zapier, Make, Power Automate, or the REST API

Fields get mapped once. Every lead after that arrives already mapped and stamped with its source, which is what finally lets you answer whether Marketplace or the website form is worth the money you put into it.

A screen capture of exporting automotive data
Export your parsed automotive data to any application of your choice!

Sign up to Parseur for Free
Try out our powerful document processing tool for free.

The First Five Minutes Go On Retyping

A car lead contacted inside five minutes is 21 times more likely to enter the sales cycle than one contacted after thirty, according to AutoAlert. Three of those five minutes usually go on reading an email and keying it into a CRM.

Web forms are where the weight of it sits. Giosg found 81% of dealerships rely on web forms as a primary lead source, and a form notification lands as prose, not as ADF, so every single one is a small transcription job with a stopwatch running on it.

Then there is the lead nobody ever gets to at all. The 2025 Automotive Dealer Benchmarks Report by Foureyes found 14.1% of new sales leads never make it into dealer CRMs, a share that has grown year over year. One in seven ups, bought and paid for, disappearing into an inbox nobody owns. On a two-salesperson store nobody catches it either, because a lead you never saw never shows up in a report.

How It Works

Parseur is an AI email parser. There is no template to build and no rule to write, because the AI reads what a message means rather than where the words sit on the page. Adding a lead source is a forwarding rule, not a project.

1. Create a Parseur mailbox

You get a dedicated address, something along the lines of [email protected]. Point your lead notifications at it: Craigslist replies, website form emails, the after-hours mailbox your BDC works through on Monday morning. Here is how to set up auto-forwarding. Set that rule on the mail server rather than in a desktop client, which rewrites messages on the way out.

Facebook Marketplace takes one extra step, and anyone who tells you otherwise has not tried it. Inquiries arrive in Messenger rather than your inbox, so you forward the Marketplace notification emails, or route the conversation into a shared mailbox your team already watches. A raw Messenger thread with nothing forwarded out of it cannot be parsed by anything, Parseur included.

2. Name the fields you want

In plain English, once. Buyer name, phone, vehicle of interest, stock number, whatever your CRM expects to receive. Then forward the ugliest lead email in your inbox, not the tidiest. That is the one that tells you whether this works for your store.

3. Read the first week with your own eyes

Parsed leads appear in the results view within seconds of the email arriving, each record shown beside the message it came from, so checking a phone number means reading what the buyer actually typed instead of somebody's copy of it. When a field is genuinely missing from an email it comes back empty rather than as a plausible wrong value, which is the failure you want out of a machine handling buyer contact details. Validation is optional, holds each lead for a person to approve before it exports, and is there for exactly this week.

4. Send each lead where it needs to go

Your CRM and the sales manager's Google Sheet at the same time, if that is what the store runs on. From there it is the export and integration step, and it runs untouched from then on.

Rooftops that also handle the paperwork side, such as vehicle job cards and service records, push those through the same mailbox. The wider picture is on the automotive document processing page.

What It Costs and Who Holds the Data

The free plan is 20 pages a month with no credit card, which is enough to put a weekend of real Marketplace and web form leads through it and see what comes out the other end. Paid plans are priced on the number of pages you process in a month, not per user and not per rooftop, so a two-person store pays for a two-person store's volume.

On the data itself, Parseur is SOC 2 Type II compliant, with the report available on request if your insurer or your lender ever asks, and GDPR compliant. Lead emails are encrypted in transit and at rest, you set a retention window so buyer records delete themselves rather than piling up in a third system, and your data is never used to train AI models and never sold.

What Dealers Say

Cawdor Cars runs lead email from several sources into a single sheet, with nobody keying anything.

Data entry is quicker (instant!) and much more reliable. It's helped us coordinate information from different email sources into one spreadsheet with zero manual input from us.

  • Cawdor Cars

More from the dealers using Parseur.

Nobody ever sold a car by typing a phone number into a CRM. The leads your providers deliver in clean ADF are already handled. The one that came in at 9:40 on a Sunday night about a silver Tacoma is still sitting there.

Last updated on

Get started

Ready to automate your
document data extraction?

Start free in minutes and see how Parseur fits into your workflow.

No model training required
Automates data entry from any document
Scales from point-and-click to API

Frequently Asked Questions

What dealers ask before they let software near the lead inbox: whether they need it at all given ADF, what happens to the sources ADF never covers, where the data lands, and whether buyer contact details are safe in it.

ADF (Auto-lead Data Format) is the XML standard US dealer CRMs use to ingest internet leads, and the major providers already send leads to your CRM's ADF inbox in that format. If every lead you get arrives as clean ADF, your CRM is doing this job and you do not need a parser for it. A parser earns its place on the leads ADF never carries: Facebook Marketplace, Craigslist, text-in leads, your own website form, and any provider whose XML shows up malformed or half empty.

Parseur has a free plan of 20 pages a month with no credit card, which is enough to run a weekend of real lead emails through it before you commit to anything. Paid plans are priced on the number of pages you process in a month rather than per user or per rooftop, so a small independent lot pays for a small independent lot's volume. Adding another lead source does not change the price, only the volume going through it.

Buyer name, email address and phone number, the vehicle they asked about down to year, make, model and trim, plus VIN, stock number and listing price. Anything the source put in the message can be pulled out of it, including a trade-in mentioned halfway through a sentence or a question about financing. The AI locates each field wherever it happens to sit, so nothing depends on the layout staying still.

Yes, though these are usually the sources you need it least for, because the big providers send ADF straight to your CRM. Parseur reads their emails like any other, which is useful when you want the same lead in a spreadsheet or a warehouse as well as the CRM, or when your store has no ADF intake set up. Because the AI reads any layout, there is no separate setup per platform.

No. Parseur's AI extracts the fields you asked for from any layout, so there is no per-format or per-platform template to maintain and nothing to rebuild when a provider redesigns its notification. Adding a new lead source costs one forwarding rule.

Pick the destinations once in the Export tab. Leads can go straight to Google Sheets, out to a CRM or marketing tool through Zapier, Microsoft Power Automate or Make, or to any endpoint you run by webhook and REST API. You can also download a batch as Excel, CSV or JSON when someone wants the month in a file.

Yes. You name the fields in plain English and Parseur returns them, so a store that tracks preferred contact time, co-buyer details, a referring salesperson or a specific campaign code gets those alongside the standard name, contact, vehicle, VIN and stock number. No coding, and no separate setup per lead source.

Parseur is SOC 2 Type II compliant, with the report available on request for a vendor review, and GDPR compliant. Lead emails are encrypted in transit and at rest, and you set a retention window so buyer records delete themselves instead of piling up in a third system. Your data is never used to train AI models and is never sold.

Not as a built-in export today, and it is worth being straight about what that means for you. Parseur extracts the fields and delivers them as structured data through a webhook, Zapier, Make or Power Automate, which is how most teams get leads into a CRM. If your CRM will only accept leads at an ADF intake address, somebody has to assemble the ADF document in that automation step, and that is a one-time build, not a forwarding rule. Most stores come to us for the opposite problem, the sources that never produce ADF in the first place.

Marketplace inquiries arrive in Messenger rather than in your inbox, so the first step is getting them to an email address: forward the notification emails, or route the conversation into a shared mailbox your team already watches. From there Parseur reads each message, pulls the buyer name, contact details and the vehicle they asked about, and pushes the record to your CRM or spreadsheet. Raw Messenger threads with nothing forwarded cannot be parsed.

That is the common failure of partial ADF: the lead reaches the CRM, but the vehicle, the trade-in and the financing notes sit inside a free-text comments block where no field ever picks them up. Parseur reads meaning rather than position, so it pulls the year, make, model and stock number out of that prose and delivers them as their own fields.

Yes, and that is where it fits best. Independent lots take most of their traffic from Marketplace and Craigslist, the two sources that never send ADF, and often run a spreadsheet or a general-purpose CRM with no lead intake address. Parseur reads those emails and writes one clean row per buyer wherever you want it, no dealer CRM required.

Yes, and most teams do. The same extracted lead can go to your CRM through Zapier or a webhook and to a Google Sheet at the same time, which gives the sales manager a source list the CRM cannot lock away and a fallback record if the CRM rejects a lead.

Yes. Parseur processes an email within seconds of it arriving and exports the structured record immediately, so the lead exists in your pipeline before a salesperson would have finished reading it. In automotive retail that gap is the whole game, because a buyer contacted within five minutes is far more likely to enter the sales cycle than one reached half an hour later.

Every parsed lead is shown next to the original email, so checking a phone number means looking at the message the buyer sent rather than somebody's retyped copy of it. Optional validation holds each record for a person to approve before it exports, which is worth leaving on for a new lead source and worth switching off once that source has earned it. When a field is genuinely missing from the email it arrives empty rather than as a plausible wrong value.