Prefer a short current policy
Over a folder of outdated decks.
Guide
How to prepare your information for an AI integration
Most delays are not in the protocol. They are in unclear ownership, stale files and answers nobody wants to stand behind.
A practical checklist
- List repeating questions. The ones customers already ask every week.
- Name the source of truth. One owner per answer, even if the file still lives in several places.
- Mark what may be automated. And what must stay human.
- Agree who updates each source. Without that, the connection will rot.
- Decide the down path. What the assistant says when the source is unavailable.
Quality over volume
Prefer fields a system already stores
Over text that nobody maintains.
Prefer fewer cases you will measure
Over a complete encyclopedia.
When to stop cleaning and start connecting
When one customer action has a named source, an owner and a next step. Waiting for perfect documentation is how projects never leave the slide. Connecting messy sources is how you get answers you cannot defend. The middle is enough structure for the first case.
Next
Bring the source map, even if it is unfinished
A list of questions, owners and files is enough to see whether a first connection is viable.
Review it with Xagair