Records, History, and Coverage
Suite is where you prevent avoidable mistakes: duplicate recommendations, missed recalls, forgotten declined work, and coverage surprises. The verification step is not clerical. It is customer protection.
Use Suite and the connected workflow to verify history, recalls, warranty, aftermarket coverage, prior concerns, and declined work before the customer conversation moves too far.
What to Verify
| Area | What to check | Why it matters |
|---|---|---|
| Customer record | Name, phone, email, preferred contact, advisor notes | Wrong contact info breaks every update after check-in. |
| Vehicle | VIN, mileage, plate, concern history | Wrong vehicle means wrong history, pricing, and coverage. |
| Service history | Last 12-24 months of work and recommendations | Prevents duplicate selling and surfaces warm leads. |
| Declined work | Prior declined repair ops and dates | Creates a clean follow-up conversation. |
| Warranty / recalls | Factory coverage, open recalls, related TSB context | Customer should not pay for something covered. |
| Aftermarket coverage | Contract company, phone, deductible, authorization path | Coverage must be verified before quoting or repairing. |
Warm Leads, Not Random Upsells
Prior declined work is one of the best uses of Suite. A declined repair op from last visit is not pressure. It is context.
"Last visit we documented rear brakes at 3mm and you chose to wait. Since the vehicle is back today, I asked the tech to recheck them so we can see where they stand now."
Coverage Language
Never promise coverage from memory. Use Suite notes and the coverage process to verify before quoting.
"I see you may have coverage that could apply. I am going to verify it before I quote you, so I do not tell you the wrong thing."
The Dyer Standard
Before the RO leaves the drive, Suite should show who the customer is, what they asked for, what history matters, what coverage may apply, and what promise was made.