Does it fit mine? Sabato's agent takes the registration or the VIN, checks it against your fitment table, and says yes, no, or “that one was superseded — here’s the current part”.
WHAT THE CALLER JUST ASKED
“I’ve got a 2016 Golf, 2.0 TDI — will these front discs fit it?”
Example call. Illustrative interface, not a customer recording.
Why this category phones
Parts buyers are not browsing. They have a car in pieces, or a customer waiting, and a specific question: does this fit. Get it wrong and you pay the return, the courier, and often a labour claim from a garage that already started the job.
The product page can host a registration lookup, and it should. It still cannot answer “mine’s a facelift model, does that change the caliper?” — which is exactly the call that arrives instead.
Ordered by how often we hear them in this category. We do not publish a call-mix distribution we have not measured — replace this with your own tagged call log before you act on it.
Fitment is a data problem before it is a service problem. Every answer here resolves against a specific table, and where the table is thin the agent hands over rather than guessing — a confident wrong fitment is the most expensive answer in this category.
“Will this fit a 2016 Golf 2.0 TDI?”
Registration or VIN decoded to the exact vehicle variant, then matched against the fitment table for the part family.
vehicle.by_vin · fitment.k_type“Mine’s the facelift — does that change anything?”
Build-date range on the fitment record, which is where most wrong-part orders actually originate.
fitment.build_from · fitment.build_to“That part number doesn’t come up any more.”
Supersession chain followed to the current part, with the original number kept in the order notes for the garage.
part.superseded_by[]“Is the aftermarket one as good as the OEM?”
Brand tier and the OE reference cross-match, stated as an equivalence claim from your data — not as an opinion the agent invents.
part.oe_refs[] · brand.tier“I need it tomorrow, the car’s on the ramp.”
Stock by warehouse plus the cut-off time for next-day dispatch on the caller’s postcode.
stock.by_wh · carrier.cutoffIf a row here could be copied onto another industry page unchanged, it does not belong on this page.
Recognise your own call log?
We’ll run these questions against your catalogue on the intro call.
The fitment call. The one that decides whether the order is right.
02A garage with a car on a ramp asks differently. Answered from live carrier events.
03Wrong-part returns triaged by cause, so the fitment data gets fixed rather than the return processed.
04Part number, vehicle and fitment confirmation in writing before the card is charged.
Hi, I’m after front brake discs for a Golf, 2016, the 2.0 diesel.
I can check that exactly if you have the registration.
Yes — it’s a Mark 7, reg is on the paperwork here, one moment.
Take your time. While you find it: is it the standard model or the GTD?
Standard. Reg is BD16 ZKP.
Got it — 2016 Golf 2.0 TDI, built March 2016, which puts it after the facelift. That takes the 312 millimetre vented disc, not the 288 the earlier cars use. The ones you were looking at are the 288, so those would not fit.
Good job I called.
The 312 pair is in stock in the Birmingham warehouse, cut-off for next day is four o’clock. Most people take the pads at the same time — same axle, same job. Want me to put both on?
Yes, both.
Illustrative transcript built from the workflows above. Not a customer recording; no customer data is shown.
Hear this run against your own data.
Same call, your catalogue, on the intro call.
Fitment data ages badly. Manufacturers revise, supersede and re-reference constantly, and a table that was correct two years ago will quietly produce wrong answers today. We audit these before the pilot.
THE HONEST PART
Bad source data produces confident wrong answers. If a field is stale, the agent will speak it fluently — and a wrong answer at speed is worse than a slow right one, because it converts into an order that fails. We audit the fields this page depends on before the pilot, and we cap the agent to hand over on anything unmapped.
Registration or VIN to the exact variant: engine code, build date, trim.
Part family to vehicle variant, with build-date ranges — the field most often missing.
Old part number to current, so a discontinued reference still lands on a sale.
Which aftermarket references map to which OE numbers, and at what brand tier.
Plus carrier cut-off times, because next-day is the whole question for a garage.
We start with your real call recordings and your real data. Four weeks, one workflow, a baseline measured before the agent goes live and again after. If the numbers don’t move, you stop — no annual lock-in, and no case study written before the result exists.
We baseline your current call volume, answer rate and missed-call hours first.
One workflow live in week one, on your own number, with a human fallback.
You see the transcripts of every call the agent takes, including the ones it hands over.
Two named customers, no logo wall — we won’t show you a client we don’t have.
Can a voice agent really confirm fitment on the phone?
Only as well as your fitment table allows. Given a registration or VIN it decodes the variant and matches the part family, including build-date ranges. Where the table has no record for that variant it says so and hands over — it does not infer fitment from a similar model.
What about trade customers who call every day?
They are the ones who benefit most, because the call is short and repetitive: part, vehicle, stock, cut-off. The agent recognises the account from the number and skips the parts a regular caller does not need to hear.
Can it handle a caller who does not know their VIN?
Yes — it asks for the registration first, and falls back to make, model, year and engine, flagging that the answer is less certain than a VIN match. That caveat is spoken, not buried.
Does it work out of hours and at weekends?
Yes, and in this category that matters more than most: a lot of parts buying happens on a Saturday with the car already apart.
What does it need from our store to go live?
Read access to products and orders, your fitment and supersession tables, and stock by warehouse with cut-off times. If fitment lives in a supplier feed rather than your catalogue, we read the feed.
Bring a registration and a part number to the intro call. We’ll run it against your own fitment data, live.
Start Free Pilot