One engine. Three bodies of knowledge.
The engine carries no customer's content. Each vertical is its own model file, and every answer in it points back at a source — the operator's own service documentation where it exists, field experience marked as such where it doesn't. Adding a fourth is a content build, not a rewrite.
ATM Resolution Desk
Card capture, dispense faults, note rejects, receipt printers, terminal offline. Separates a processor outage from a machine fault before anyone travels.
Two fleets · one code tableAir & Vacuum Resolution Desk
Almost no error codes on this equipment, so plain words are the only way in. Suction, coin faults, display messages, site electrical.
Plain-word entry · no code tableTire Inflation Resolution Desk
Display codes, deflation faults, compressor and output-side work, install and specification questions. Model variants change the answer.
Model-aware · the variant changes the answerThree real exchanges.
Taken from the working systems, not written for this page.
CATALOG Canister cap plugs
Not just faults.
A support line carries everything that is not a fault, and most of it is cheaper to answer than a call. The build answers all of it from the same content, with the same citations.
One script tag, or a QR on the machine.
The website entry point is a widget in the corner of the operator's own page. The machine entry point is a QR sticker that lands on a full page, because a technician in front of a broken unit is not browsing a website looking for a bubble. Same agent, same answers, two front doors.
Don’t take any of this on trust. The working assistant is shown by invitation, on the operator’s own equipment and content.