Question handling
Answering will this work with mine, without guessing
This is the most tempting question in the family to over answer. The reasoning always looks sound: it works with the model above and the model below, so it presumably works with this one. Presumably is doing an enormous amount of work in that sentence, and it is the customer who pays when it turns out to be wrong.
What they are really asking
They are about to spend money and they want somebody to take responsibility for saying yes.
- does it work with windows 11
- is it compatible with my model
- will this fit a 2015 golf
- does this work on mac
- is it compatible with my printer
- does it work with the older version
- can i use this with the kit i already have
- does it support 5ghz wifi
- which browsers do you support
- will this work with my existing account
The material that answers it
An assistant is only as good as the document behind it, and for this question the document usually exists but is written in the wrong shape. What each one has to contain to be answerable:
| An explicit compatibility list, with the date it was verified | The entire intent depends on this document existing. Without it there is nothing to retrieve and the honest configuration is a refusal. The verification date matters because compatibility decays quietly as other people ship updates. |
|---|---|
| The negative list | What is known not to work, and ideally why. Almost nobody publishes this and it is as valuable as the positive list: it converts an expensive return into a sentence, and it stops the assistant treating absence from the list as an implied yes. |
| Minimum requirements, stated as thresholds | Version numbers, operating systems, hardware, connection type, physical dimensions. A threshold answers a whole class of questions the list itself cannot enumerate, and it ages better than an itemised list does. |
| A definition of what compatible means here | Works fully, works with an adapter you have to buy, works with reduced function, physically fits but is not supported. These are four different answers and customers hear all of them as yes unless the difference is written down. |
| The identifier a customer can actually find | The model number on the underside, the registration, the serial, the part number on the old one. A list keyed to something the customer cannot locate is a list nobody can use, so publish where to find the identifier alongside the list itself. |
How to handle it
Publish a list or refuse the question
There is no third option that is honest. An assistant reasoning about compatibility from product descriptions is generating a purchasing recommendation out of marketing copy, and it will sound exactly as confident when it is wrong as when it is right.
Where no list exists, the correct behaviour is a refusal naming the person who can check. Run this intent cautiously so a near match on a similar product does not become an answer about a different one.
Match on the identifier, not on the description
My printer, my car, my laptop are not identifiers. The assistant should ask for the model number or the equivalent and tell the customer where to find it, then answer against the list. The extra exchange is cheap and it is the only thing that makes the answer meaningful.
Never generalise from an adjacent product
The same manufacturer, the next model up, last year's version, the same series. Every one of these is a plausible chain of reasoning and none of them is evidence. The material must say the specific thing, or the answer is that it is not listed.
This is worth stating in the indexed material itself, because a compatibility page that says absence from this list means untested rather than incompatible gives the assistant a correct sentence to reach for.
Return an unknown as an unknown, with a route
It is not on our tested list, so I cannot confirm it. The team can check for you, and here is what they will need. That is a good answer. It respects the customer's actual decision, and it is far better received than a hedged yes that turns into a return.
When it stops being an answer
Anything absent from the list
Not a refusal into silence, a refusal into a person. Somebody asking is usually holding a payment card, so the handover should be quick and should collect the model identifier so the answer comes back in one reply.
A purchase riding on the answer
If I order this today will it work with mine is a different question from a general compatibility enquiry, because a wrong answer becomes a return, a refund and sometimes a shipping cost. Where there is any doubt, this belongs with a person.
Anything with a fitting or safety consequence
Parts that bear load, electrical fittings, anything installed rather than plugged in, anything where a wrong match is dangerous rather than merely useless. Compatibility here is an engineering judgement and it should never be produced by matching text.
How this one goes wrong
The inferred yes
The list covers two models either side of the one asked about. The assistant, reasoning helpfully, says it should be compatible. The customer buys, it does not fit, and the return costs the shipping both ways, the restocking, the refund and a review that says the website told me it would work.
What makes this failure worth designing against specifically is that it feels like good service at the moment it happens. The reply is friendly, prompt and wrong. Publish the negative list, define what compatible means, and let the assistant say not tested rather than probably fine.
The same question, trade by trade
The pattern above holds everywhere. The wording, the escalation line and the material behind it do not, so there is a page per trade.
- For a electronics retailerA compatibility list is a fact. Extending it to a model nobody tested is the guess that comes back as an opened box.
- For a bike shopFreehub bodies, axle standards and shell widths are facts. What a previous owner changed is not, and that decides it.
- For a online courseA tablet at home, a locked down work laptop, a phone on a commute. What to publish before purchase rather than after the refund window.
- For a plumbing and heating firmA combi, a system boiler with a cylinder and an old vented setup answer this three different ways, and only a survey separates them.
- For a electrical contractorChargers, showers and hot tubs all raise one question about the supply. The honest answer is the short list the survey checks.
- For a SaaS companyWill it work with our sign in, our browsers and the tools we already pay for. Three questions, and one is answered by the pricing page.
- For a developer tools companyCompatibility answers age badly and end up in procurement decks. Keeping support matrices, deprecations and removal dates answerable.
Questions
- We sell thousands of variants. Is a full list realistic?
- A complete list is not, but thresholds plus the top of the catalogue plus an explicit negative list usually is. Publishing the rule alongside the exceptions covers far more questions than an itemised list of everything.
- What stops it inventing compatibility from a product page?
- Configuration plus content. It answers only from what you index, and below the match threshold it returns your fallback without reaching the model. A cautious setting on this cluster is what turns a weak match into a refusal instead of a guess.
- Is an old compatibility list better than none?
- Only with the verification date on it, so the assistant can say when it was checked. An undated list is a claim about today made from information about a year ago, and other people ship updates without telling you.
Keep reading
- Handling technical troubleshootingThe dominant failure is an answer taken from the wrong release. A refusal beats a confident step list for software nobody is running.
- Handling setup and onboardingMost product material is written for somebody who already understands it. A first run guide has to be ordered, not merely complete.
- Handling warranty and repairsCustomers conflate a manufacturer warranty, an extended plan and their legal rights. Keep the three apart and never close the third.
- Every question typeHandling patterns for the questions every support inbox gets.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.