The Customer Did the Work. Keep the Context.

- PublishedNov 14, 2026
- Sources1
- 5 min read
A practical five-field handoff for dealership teams: preserve the shopper’s stated needs, vehicle interest, estimate assumptions, open questions and chosen next step.
Decide First
One Automotive Universe. From the First Question to the Next Vehicle.
A shopper can compare vehicles, work through a budget and identify an exact unit before choosing to contact a store. If the handoff preserves only a name and phone number, the next person may have to reconstruct that work. This playbook gives a BDC, salesperson and manager a practical way to preserve information the customer has chosen to share inside the systems the store already uses.
This is an operating template, not a claim that every AutoUnite feature is released or every lead contains these fields. Missing information stays missing. No response-rate or sales-lift claim is made.
| Field | Minimum useful content | Boundary |
|---|---|---|
| Field1. Decision and requirements | Minimum useful contentCustomer's stated use case, must-haves and unresolved tradeoffs | BoundaryDo not invent needs or infer sensitive traits |
| Field2. Exact vehicle interest | Minimum useful contentVIN/stock if selected; model/trim/configuration if still researching; listing timestamp | BoundaryResearch interest is not confirmed stock availability |
| Field3. Budget assumptions | Minimum useful contentCustomer-provided budget or estimate inputs, with date and missing assumptions | BoundaryNo credit approval, quoted APR or final OTD price implied |
Comments are shopper discussion, not verified article evidence.
Comments are not open on AutoUnite yet. Published articles and Ask AutoUnite are the current way to get answers.
AutoUnite content is educational and research-focused. Vehicle information, pricing, ownership costs, maintenance, recalls, and other details may vary by region, dealer, and time.
| Field4. Open questions |
|---|
| Minimum useful contentEquipment, price, condition, availability or trade questions in the customer's words |
| BoundaryAvailable equipment is not installed equipment |
| Field5. Chosen next step | Minimum useful contentRequested contact method/time and purpose; permission/source reference | BoundaryAn inquiry is not unlimited marketing permission |
|---|
Keep customer-provided statements separate from computed estimates and facts the dealership has independently verified. A useful CRM note can mark each sentence “Customer stated,” “Research estimate,” “Dealer verified,” or “Unknown.” Preserve the source and date when available. The salesperson should be able to tell which statement can be relied on without opening a dozen tabs.
Customer stated: Needs seven seats and room for family trips. Comparing two models. Wants to understand whether the exact advertised unit has the desired second-row configuration.
Vehicle interest: A selected stock number supplied by the shopper; availability not yet checked. No real VIN or customer data is used in this example.
Research estimate: A payment range was explored using a hypothetical down payment and term. APR, taxes, fees and lender approval have not been confirmed. Do not turn this into “customer approved at $X per month.”
Open question: Can the store provide the actual equipment evidence and an itemized written purchase quote?
Chosen next step: Reply by the method the shopper requested with the answers; do not place them into an unrelated campaign.
The first useful response would be: “You asked about the second-row layout and a written total on the unit you selected. I’m checking those details. Is that still the vehicle you want me to verify?” It acknowledges the real question without claiming a completed inspection, price confirmation or approval.
Shoppers should be able to understand which dealer they are contacting, why information is requested and what will be shared. Describe only the receiving path and capabilities that actually work for that dealership. An inventory listing alone does not prove the dealer has active inquiry routing.
Record the actual submission reference and relevant permission evidence in the existing system. Limit access to the people handling that inquiry. Keep financial documents, identity documents and private customer histories out of editorial examples and shared growth trackers. If a dealer cannot verify the intended recipient, hold routing until the correct destination is confirmed.
Assign one owner and an explicit next action. Reconcile the store and exact vehicle to the correct rooftop; a shared group name is not enough. Check for an existing customer inquiry before creating another task or record. Preserve the original request and timestamp.
Use this evidence sequence:
If the CRM receipt is missing, investigate before resending. Replaying an inquiry can create duplicate records and duplicate calls. An authorized backup path should use the same original reference and be recorded as a fallback, not a new lead. A controlled test must be clearly labeled, authorized by the receiving dealer, and excluded from acquisition results.
Read the open questions first. Confirm availability and exact equipment from attributable store evidence. If an answer needs verification, say who is checking it and give a realistic next step. Do not replace the requested answer with a generic appointment demand.
For price questions, provide the store's actual written quote and identify the vehicle, applicable conditions and unresolved charges. Research estimates remain estimates. For affordability questions, identify which inputs came from the customer and what still depends on the lender or transaction. Never present an estimated payment as an approval.
Ask only for missing information that matters to the next step. A customer who already provided a preferred contact method should not need to explain it again to every role. Respect a change of preference or request to stop and record it in the system that governs further contact.
Use the existing CRM and canonical operating records. Review a small, permitted sample of genuine inquiries and reconcile these questions:
Measure accepted unique inquiries, confirmed CRM receipts, real conversations, appointments held and resulting business outcomes separately. If the denominator or observation window is incomplete, say so. Duplicate records, tests, automated acknowledgments and pageviews do not become qualified leads by changing a label.
Choose one rooftop and a receiving owner. Verify its destination with one authorized controlled inquiry before enabling real shopper routing. Train the BDC and salesperson on the five fields, ownership and missing-data labels. Review actual consented inquiries as they occur; do not manufacture activity to fill a scorecard.
At the next review, compare the records with the team's actual experience. If the context is useful, retain the process. If it is missing or misleading, correct the handoff before expanding. The goal is a better starting point for the customer conversation, evaluated on evidence from the store.
AutoUnite is the automotive operating system for the entire vehicle lifecycle. Dealer OS is designed to work alongside store systems and carry submitted, permitted context forward when available. The current dealer page describes a $0 120-day beta, no credit card and no automatic paid conversion. Application is separate from approval, routing verification and activation. Sample dashboard data and staged features do not establish live participation or outcomes.
Current dealer information: https://www.autounite.com/dealers
The five-field workflow, fictional example and review method are original AutoUnite recommendations. They are not observed customer records or measured results. Follow applicable AutoUnite and dealership privacy and permission requirements. This playbook does not provide a new legal basis for sharing data.