2.2 Customer & Vehicle Information and Customer Types
Key Takeaways
- Obtain, confirm, and document vehicle identifiers plus customer contact details before work begins
- Verify—not assume—year, make, model, mileage, license, and VIN against the vehicle and systems of record
- Identify customer type (first-time, warranty, repeat repair, fleet, etc.) because process and tone change
- Identify payment source early (retail, warranty, service contract, fleet PO, insurance) to avoid RO errors
- Incomplete contact info is a C1 failure mode: status updates, authorization callbacks, and CSI all depend on it
Customer & Vehicle Information and Customer Types
Quick Answer: Before diagnosis or repair, the service consultant must obtain, confirm, and document vehicle data and customer contact information, then identify customer type and payment source. Accuracy here prevents misrouted warranty claims, missed callbacks, and repair orders written on the wrong vehicle.
Two Customer Relations tasks sit at the heart of intake:
- Task 2: Obtain, confirm, and document pertinent vehicle/customer contact information
- Task 11: Identify customer type (first time, warranty, repeat repair, fleet, etc.) and source of payment as necessary
On C1, "pertinent" means the data the shop needs to dispatch, communicate, authorize, and bill correctly—not every field imaginable, and not guessing from memory.
Vehicle Information: Obtain, Confirm, Document
Obtaining information is only step one. Confirming means checking the customer's statements against the vehicle and your systems. Documenting means the repair order (and DMS) contains what the technician and cashier will rely on.
Typical vehicle fields:
| Field | Why it matters | Confirmation tip |
|---|---|---|
| Year / make / model / trim | Parts fitment, maintenance schedule, TSB applicability | Match door sticker / VIN decode; do not trust memory alone |
| VIN | Identity of the exact vehicle; warranty and campaigns | Read from vehicle or reliable scan—not a prior RO for a different car |
| License plate / state | Lot identification and pickup matching | Confirm plate matches the vehicle in the lane |
| Mileage / kilometers | Maintenance intervals, warranty limits, inspection logic | Record current odometer; note if cluster seems inaccurate |
| Color / unit number (fleet) | Prevents delivering the wrong similar vehicle | Especially important for fleets and identical rental units |
Trap: Copying last visit's mileage or VIN without verifying. Vehicles get sold, loaners get mixed up, and households bring a different car. C1 rewards the consultant who confirms identity every visit.
Trap: Accepting "it's the silver Camry" as enough when two silver Camrys are on the lot. Use VIN or plate.
Customer Contact Information
Contact data enables authorization calls, delay updates, and pickup coordination. Capture and confirm:
- Preferred name and how they want to be addressed
- Primary phone and whether texting is allowed
- Secondary contact if the primary will be unreachable
- Email if the facility uses digital estimates or CSI surveys
- Best callback window (important for fleet managers and shift workers)
Confirm spelling of names and phone digits by reading them back. A single transposed digit can strand a diagnostic authorization for hours. If someone other than the owner drops off the vehicle, document the drop-off person's contact info and clarify who can authorize additional work and who pays.
Customer Types and Why They Change Your Process
ASE explicitly lists examples: first time, warranty, repeat repair, fleet, and similar categories. Identifying type is not labeling people—it is choosing the right process and communication stance.
| Customer type | What to recognize | Consultant implications |
|---|---|---|
| First-time | New to your facility | Orient them to process, wait times, transportation, and how updates work; build trust carefully |
| Warranty | Concern may be covered under OEM or extended coverage | Gather in-service date, mileage, prior claims context; follow warranty documentation rules |
| Repeat repair / comeback | Same or related concern after recent work | Acknowledge prior visit, pull history, escalate documentation quality; avoid dismissive tone |
| Fleet | Business vehicles, often with PO rules and unit numbers | Confirm billing account, authorized contacts, downtime priorities, and required paperwork |
| Retail cash/card | Customer-pay maintenance or repair | Discuss estimates and authorization clearly; payment method readiness at delivery |
| Service contract / insurance | Third-party approval may be required | Identify administrator requirements early; do not promise coverage you cannot verify |
A first-time customer who hears "we'll call if we find anything" without knowing typical timing may feel abandoned. A fleet manager who needs a loaner policy and a PO number will be frustrated by a retail-only script. A repeat-repair customer needs empathy and precise history review—not a cheerful upsell opening that ignores the failed prior repair.
Payment Source Identification
"Source of payment" ties directly to how the RO is opened and who must approve work:
- Customer-pay (retail) — customer authorizes and pays
- Manufacturer warranty — dealer/OEM process; coverage verification required
- Extended service contract — contract terms, deductibles, and prior authorization rules
- Fleet / company account — purchase orders, rate caps, approved vendors
- Insurance / glass / body-related — claim numbers and adjuster rules when applicable
- Internal / goodwill — manager approval pathways (know when to escalate)
Identify payment source as early as practical—often during intake—not at cashier time. If a customer says "it's under warranty," your job is to document that claim and verify process, not to argue in the lane or to assume coverage. If they say "bill the company," confirm account status and authorized signer before promising work.
Integrated Intake Sequence
A practical consultant flow that maps to tasks 2 and 11:
- Greet and acknowledge (prior section)
- Confirm who is present and who authorizes
- Identify vehicle (VIN/plate/odometer) and open or create the RO correctly
- Capture/confirm contact preferences
- Ask what brings them in (concern interview comes next)
- Note customer type cues (first visit? recent related repair? fleet unit?)
- Clarify expected payment path and any paperwork needed
Skipping step 3 or 7 is how shops write beautiful concern notes on the wrong unit or perform work that cannot be billed as promised.
Scenario: Same Concern, Different Type
Three customers report "check engine light on":
- First-time retail — explain diagnostic charge policy, transportation options, and callback process
- Warranty within terms — follow warranty write-up and documentation standards; set coverage expectations carefully
- Repeat repair two weeks after a sensor replacement — flag as related/comeback, pull prior RO, communicate that the shop will investigate the prior correction path
Same symptom; different consultant actions. C1 loves this distinction.
Documentation Quality Standard
"Document" means another trained person could continue the job from the RO. Incomplete phone numbers, missing mileage, or "warranty?" with no clarification force technicians and managers to stop and chase information. That is a shop-operations problem caused by a communications failure at intake.
Exam Focus
When a question asks what information is needed before writing the order, prioritize verified vehicle identity and usable customer contact data. When it asks how to handle a fleet or warranty customer, choose the option that identifies type and payment source and adapts process—not a one-size-fits-all retail script.
What is the best way to confirm vehicle identity during intake when a customer says they brought "the same car as last time"?
A company driver drops off a van and says, "Just fix it and bill the office." What should the service consultant identify early?
Why must customer contact information be confirmed—not just collected—during write-up?
A customer returns with the same symptom two weeks after a related repair. Which customer-type recognition is most important for the consultant?