Begin with the questions customers actually ask
Read a handful of recent conversations and list recurring questions. Look for access requirements, preparation, coverage areas, materials, cleanup, payment arrangements, and what happens after someone agrees to proceed. Start with the questions that interrupt work repeatedly.
Write answers in ordinary language. Instead of a note that says 'access protocol applies,' explain what the customer must provide and when. If the answer varies by service, keep that condition in the same fact so it cannot be separated from the answer.
Applies to: exterior window cleaning. Answer: The customer does not need to be home if the team can access the quoted exterior windows and the agreed water supply. Interior window cleaning requires separate access arrangements. Owner: Operations. Review when the service process changes.
Keep quote facts separate from business policies
A website might say that you offer driveway cleaning. That does not mean the driveway is included in every house-wash quote. A specific document may also contain a special exclusion that overrides the normal service description.
Give quote-specific questions quote-specific evidence. For company policies, use the current approved policy. When the two disagree, ask for review rather than combining them into a confident answer. A useful test question is: 'Would this response still be true for a different customer's quote?'
Importing a website is a starting point
Public pages can supply useful descriptions, service locations, and common questions. They can also contain old promotions, customer reviews, broad slogans, and instructions intended for a different service. Importing everything as an approved fact can turn someone else's testimonial into your own promise.
Review imported material as a readable document grouped by topic. Remove navigation, repeated footers, unrelated reviews, and claims you cannot stand behind. A bulk approval action is convenient, but it should approve a set of information you can actually inspect. Keep the original source link available.
Mark the boundaries as clearly as the answers
Some facts are deliberately unknown. You may not have a general warranty policy for a particular installation, or scheduling may depend on the crew. Record those boundaries so the system knows when it must ask.
An acknowledgment should be useful without inventing a promise. It can say that the question needs confirmation and identify what is being checked. It should not announce a guaranteed callback time unless the business has approved and can meet that commitment.
- Approved answers the agent may use
- Draft or imported information awaiting review
- Quote-specific details and exceptions
- Questions that always need an owner decision
- A source and an owner for each important policy
Treat maintenance as part of running the business
When a policy changes, update the source and retire the old version. Leaving both active forces the system to guess which one matters. Assign someone to review knowledge when prices, services, coverage areas, or working arrangements change.
Use handoffs to find gaps. If three customers ask the same question and the owner gives the same answer each time, consider making it an approved fact. If the answer depends on details unique to each job, leave it as a decision rather than forcing a universal rule.
Finally, test the knowledge as a customer. Ask a direct question, a vague version, and a question that combines two services. Correct information is only useful if the system retrieves it in the situations your customers create.