How to prepare your website for an AI assistant

Choose a question your business already receives: “Do you cover my area?” or “Which cleaning service should I ask about?” Then define a useful outcome, such as understanding the service or preparing a quote request.

This gives the knowledge review a purpose. You can judge whether the information helps a visitor complete that journey, rather than collecting documents without knowing how they will be used.

For the chosen service, gather the description, inclusions, exclusions, coverage and next steps. Add preparation instructions or current policies where they affect the visitor’s decision.

Be explicit about conditions. “We work across the city” may hide exceptions. If coverage depends on the type of work, say so in the source information.

For each fact, record where it comes from and who can confirm it. A simple worksheet can use these columns: topic, approved answer, source, owner and review date.

Compare the service page, FAQ, downloadable documents and any current offer. Look for differences in names, prices, coverage or scope.

Ask the business owner which version is current. Correct the website where possible and exclude superseded material from the assistant’s setup. Do not expect an assistant to resolve an internal policy disagreement.

Avoid giving a pilot information you do not want a visitor to receive. Public service information and private business records need separate handling and access decisions.

Write down the questions that require judgement or a live check. These may include a bespoke quote, a guaranteed completion date, suitability for an unusual material or a confirmed appointment.

For each gap, define the useful next step. “The team needs to assess the fabric; prepare a question for them” gives the visitor more direction than a vague refusal.

This list becomes part of your evaluation. Ask those questions deliberately and check that the assistant does not fill the gap with an invented answer.

Look at an enquiry your team could respond to without immediately asking for the basics. Which details made it useful?

Those might include the service, property type, approximate scope, location, preferred timing and a contact method. Keep only the details that affect the response. Give visitors an easy way to correct them.

Distinguish a preference from a commitment. “Tuesday would suit me” belongs in the request as a preferred date. It does not establish that the business is available.

Choose the person or team responsible for follow-up. Define where the request should arrive and what acknowledgement the visitor should see.

Test the complete path with non-sensitive sample information. A message appearing in the conversation does not prove that an enquiry was saved or that the receiving team got it.

Check the saved request and the receiving destination. Also check what the visitor sees if the handoff fails or the result is uncertain.

Include a straightforward question, a vague opening, a correction, an unsupported service and a request for an unpublished price. Add a visitor who stops before confirming.

For each case, write the expected answer or boundary before running the test. Save the observed result and fix the source information or behaviour when it misses that expectation.

You now have a practical baseline to reuse when the business changes its services or the assistant changes its behaviour.

• A named service and visitor journey.
• Current service, coverage and policy information.
• A clear owner for each important fact.
• Conflicting or expired content resolved.
• Unknowns and escalation steps documented.
• Minimum enquiry details agreed.
• A receiving team and verified handoff.
• Realistic test questions with expected outcomes.

Assign ownership for updates when services, offers, coverage or policies change. Repeat the relevant tests after each meaningful update.

The preparation is not complete because a document was uploaded. It is useful when the information supports accurate answers and an enquiry process your team can follow.

See SiteKnova’s business knowledge approach ↗ · Use the evaluation checklist ↗

Bring a service page and a question it should answer. We can use them to discuss a focused SiteKnova demo.

Request a demo ↗