Required CRM Fields for Internet Leads and Why

Open a new internet lead in most CRMs and you will see a form built for a credit application, not for a first Marketplace message. Phone, work phone, email, address, employer, trade year, desired payment, how they heard about us, spouse name, best time to call, and a dozen more boxes that a rep will skip because the buyer only asked if the truck is still on the lot.

The counterintuitive move is to require less, not more. Required CRM fields for internet leads should be the smallest set that lets anyone on the floor work the file, attribute the source, and measure the funnel. Everything else is optional until the conversation earns it. A long form that nobody completes is not a data strategy. It is a trained habit of typing "n/a."

This article is for internet directors and used-car managers who already have a CRM and still cannot filter a clean list of Marketplace appointments, sold units by source, or leads missing a next-step date. It explains which fields to lock, why each one exists, how to stage optional fields, and how to audit skips without turning intake into a punishment.

Why Required CRM Fields for Internet Leads Get Ignored

The form was designed for a different lead type

Portal leads often arrive with name, email, phone, comments and a vehicle. Marketplace and many website chats arrive with a first name and a question. If the required set assumes a complete ADF packet, reps will invent values to save the record. Fake emails and placeholder phone numbers then poison every downstream report.

Required and important are not the same

A field can be important later and still be wrong to require at create. Employer and housing status matter at desking. They do not matter at "is this still available?" Require them at create and you either delay the first reply or collect fiction.

Nobody explained the why

Reps skip fields they believe are for "the office." If they do not see how the field changes their own day — who covers the lead, which unit to pull, whether the source report is honest — they will treat it as clerical work. Every required field needs a one-sentence reason you can say on the floor.

The Core Required Set (Keep It Short)

Lock these at lead create. If your CRM cannot make a field required, make it a written rule and fail the weekly sample when it is blank. Do not add to this list until these are clean.

Identity and reach

• Full name or the name they used, even if it is only a first name plus a note that last name is unconfirmed.
• At least one working contact method. Phone or email, whichever they actually used. Do not require both on a Messenger-only lead if you do not have both.
• Contact preference. Call, text, email or Messenger. This prevents a well-meaning opener from calling someone who already asked to stay in the thread.

If you cannot reach them again, you do not have a lead. You have a screenshot.

Vehicle and source

• Stock number of the unit they asked about. If they asked about more than one, record the primary and note the others. Without a stock number, inventory, recon and the sales desk cannot help.
• Lead source from a pick-list, not free text. Marketplace, website, portal, phone, walk-in, referral, other. Free text destroys lead source naming and makes ROI a guess. For how that field feeds a report a GM will trust, see tracking Marketplace lead source ROI in your CRM.
• Assigned owner. A person, not a team name. "BDC" is not an owner. A named rep or a named associate is.

Stage and next action

• Status using your store's real definitions, not a default of "new" that never changes.
• Next-step date. A calendar day. "Follow up" is not a field value.

That is the required set: who they are, how to reach them, what they want, where they came from, who owns them, where they sit in the funnel, and when someone must act. Eight ideas. Some CRMs will use nine or ten boxes to capture them. Resist the eleventh.

Illustrative layout

Consider a store taking internet leads from Marketplace, the website and one portal. At create, the rep should not be able to save without:

Optional at create: address, trade details, employer, credit band, second phone, spouse, "how did you hear about us" as a second source question, and desired payment. Collect those when the conversation produces them, not as a tax on the first save.

How to Stage Optional Fields Without Losing Them

Required-at-create is not the same as never collect. Stage the rest so the file gets richer as the deal gets real.

After first meaningful reply

Ask for a last name if you only have a first, confirm the phone if the thread started in Messenger, and record whether a trade is in play. Still optional in the software if you must, but expected in the process.

When an appointment is set

Require appointment date and time, which unit they are coming to see, and whether a trade appraisal is needed. If your CRM has a separate appointment object, use it. Do not bury the time in a note and leave the appointment field blank.

When they are in process

Desking and F&I fields belong here: trade payoff questions, credit application status, expected payment range they stated. Still facts they offered, not values the rep guessed to satisfy a screen.

A simple rule for new fields

Before anyone adds a required field, answer three questions in writing:

1. What decision does this field change this week?
2. Who will notice if it is wrong?
3. What happens if we leave it optional for 90 days?

If you cannot answer the first two, it is not required. If you cannot answer the third, you are not ready to enforce it.

Enforcement: Catch Skips Without Humiliating the Floor

Block save where the CRM allows it

Hard-required beats a laminated checklist. If the CRM can prevent a save without source, owner and stock number, turn that on. Soft-required fields that still save will be skipped on busy Saturdays.

Sample the blanks, not just the deals

Weekly, export or filter leads created in the last seven days with any core field empty. That list is your coaching queue. Do not wait for month-end, when the original thread is cold and the rep cannot remember why the phone was blank.

Ban dummy values in writing

Publish the banned placeholders: 000-000-0000, test@test.com, stock 0000, source "Other" with no note, owner "House." Treat dummy values as missing fields. They are worse than blank because they hide from empty-field reports.

Pair fields with the intake checklist

The required set is the software rule. The human rule sits in your lead intake checklist for every internet lead. If intake says "confirm the unit is still in inventory before you promise a time," the stock-number field is how you prove they did it.

Common Traps When You Tighten Required CRM Fields for Internet Leads

Requiring email on Marketplace-only leads

Many buyers never give an email in the first conversation. Forcing the field produces invented addresses and bounced drip campaigns. Require a reachable channel, not every channel.

Using "source" and "sub-source" with no training

Two source fields are useful if both are pick-lists and both have definitions. They are noise if reps put Marketplace in one and "internet" in the other. Start with one clean source field. Add a sub-source only after the first is trustworthy.

Hiding the owner field behind a round-robin that nobody trusts

If assignment is automatic, still show the owner and still allow a manager to reassign. A required owner field that always says "Auto" teaches people to ignore it.

Copying franchise new-car fields onto used internet leads

New-car CRM templates often assume a configured order, a salesperson on point from the OEM site, and a co-buyer. Used Marketplace traffic does not. Build the used internet required set on purpose, even if the same CRM serves both departments.

How PostToMarket Automates This

Missing CRM fields are often a symptom of missing context at the moment of first reply: the rep cannot see whether the unit is posted, sold or sitting in someone else's queue, so they save a half-empty record and go find the car. PostToMarket does not sync fields into your CRM. It puts inventory state, posting ownership and inquiries where the person handling the lead can see them before they hit save.

Inventory facts that belong next to the lead

• Unlimited vehicles in inventory on every plan, so the stock number you require in the CRM can be checked against a live list instead of a printed recap.
• Statuses: draft, posting, posted, sold, failed. Confirm availability before you require an appointment time in the CRM.
• Bulk CSV and Excel import with a row-level error log, so the stock numbers and VINs in your CRM have a cleaner source file when you bring units in.

Ownership that matches the required owner field

• Per-rep posting queues and manager assignment to associate queues, so the person who should create the CRM record is already attached to the unit.
• Team queue view to release a claim when the owner on the CRM record is not the person who can actually reply today.
• Roles (admin, manager, sales rep, sales associate) with separate logins, so "House" stops being the default owner because four people share a password.

A place for managers to see the inquiry itself

• Leads inbox so managers can compare the original question with the CRM fields a rep saved.
• Team analytics by rep and source so source-field discipline in the CRM can be compared with posting source, not treated as two unrelated worlds.

Require fewer fields. Make the ones you require true. PostToMarket keeps the vehicle and the posting owner visible so those fields have something true to point at.

Lock the Fields, Then Watch the Save Rate

Required CRM fields for internet leads should make the next contact possible, the source report honest and the aging report usable. If a field does not do one of those three jobs at create, it is optional until the conversation earns it. Shorten the form, block dummy values, and sample blanks every week.

The required set only works if the inventory behind the stock number is current. PostToMarket keeps that inventory in one dashboard — Inventory, Queue, Leads, Analytics — with AI listing copy, human-paced posting, and a leads inbox managers can actually open.

Starter runs $59 per month for a solo seller or independent lot with one login. Dealership runs $299 per month for up to 13 team logins and two managers. Both include unlimited vehicles.

Start your 10-day free trial and check out through secure Stripe checkout. Import a file, assign a queue, and give every internet lead a stock number and an owner that match reality. Cancel anytime.