Knowledge Center

What to Put in Product Knowledge for AI Support

A packing list of facts AI Product Expert™ can use, and what must stay out. Not a ranking promise. Discoverability and answer behaviour stay on their own essays.

Editorial owner: MyQRGuide Editorial · Published Sep 18, 2026 · Last updated Sep 18, 2026

Approved product facts packed for AI Product Expert, with private records left out

This page is a packing list: which facts belong in the Product Experience so AI Product Expert™ can answer from approved copy. It is not a second discoverability essay and not a second “how the assistant should behave” essay.

Where to publish and whether to opt in: make product information easier for AI to find. What to do when the fact is missing: AI customer support for physical products. Explore the knowledge layer: AI Knowledge Engine for official product knowledge.

Pack this (in HTML)

Write these on that Mini Site in visible HTML — not only inside an image or a PDF. Delete any row that does not apply. Do not leave “TBD” on a live page.

Include Write it as
Identity The name and model the customer can see on the unit. What the product (or location) is.
First use Unbox, power, first cycle. One action per step.
Care Cleaning, storage, consumables you actually sell or specify.
Troubleshooting Symptom, safety, steps, “if that fails.” Use the troubleshooting template.
Specs you publish Voltage, size, capacity — only figures a qualified person has approved.
Spare parts Part names and numbers you sell or specify. Do not invent a code.
Warranty rules in force What the brand actually offers. Not the customer’s submitted registration record.
Stop and call a person Injury, burning smell, licensed-technician work, anything outside these facts.

Dashboard clicks: Add a Product Guide. Languages you support must be reviewed the same way — see multilingual manuals.

Do not pack this

  • Warranty submissions, tickets, chat transcripts, receipts, names, phones
  • A marketplace buyer list — MyQRGuide does not receive one
  • Forum guesses, competitor manuals you do not have rights to, or unreviewed machine translation of a safety line
  • Medical or safety claims a qualified person has not approved

Those records stay private even if the Mini Site is live. Publication is not the same as dumping a support inbox into the assistant.

Illustration

This is a labelled example, not a SKU and not an accuracy score.

Empty pack. The Mini Site has a product photo and “see PDF.” Asked “why does the pump hum with no water?”, the assistant has no approved sentence. It should say so and offer a person — not invent a spare-part number.

Usable pack. Identity, first-use, the pump symptom from the template, the fuse rating you publish, and “stop and contact support” if that fails. The assistant can reuse those sentences. Questions outside the pack still go to a person.

AI answers can be incomplete or incorrect. Token allowances depend on plan: Basic starts at 0 tokens; Silver and Premium include a starting allowance. Exact numbers stay on Pricing.