Skip to content
Writing
Industry playbooks

An AI assistant is only as good as the content behind it

Businesses deploy a website assistant expecting it to answer customer questions and are disappointed when it hedges. The model is rarely the problem. The problem is that the answers live in a salesperson's head, a PDF nobody updated, and a WhatsApp thread from last March.

2 min readOadbox

Start from the questions, not the pages

The fastest way to find out what an assistant needs to know is to read a month of enquiries — the contact form, the sales inbox, the chat log if you have one. Twenty questions will account for most of the volume, and half of them will not be answered anywhere on the site.

Writing those twenty answers properly does more for assistant quality than any amount of configuration. It also improves the site for the people who never open the assistant.

Structure beats volume

Feeding an assistant every page you have ever published produces confident answers assembled from three different eras of pricing. A smaller, curated, dated corpus outperforms a larger stale one.

  • One canonical page per topic, with an owner and a review date.
  • Prices, timelines and availability in one place, referenced elsewhere.
  • Retire old campaign pages instead of leaving them indexed.
  • Mark internal-only content clearly so it never reaches the assistant.

Decide what it must refuse

An assistant that will quote a price, promise a delivery date or confirm a discount has become a salesperson without a manager. Deciding the refusal boundary is a business decision, not a technical setting, and it should be made before launch rather than after an incident.

The useful shape is narrow and honest: answer what is documented, hand over what is not, and never invent a commitment.

Read the transcripts weekly

The transcript log is the highest-value output of a website assistant and the one almost nobody reads. It is a continuous record of what prospects want to know, in their own words, including the questions they would never have picked up the phone to ask.

Half an hour a week reading it will change your content roadmap faster than any keyword tool.

AIContentSupport

Written by the Oadbox team. Something here not match how it works in your business? We would genuinely like to hear it — connect@oadbox.com.

Eleven products, already running. One of them probably fits how you work.

See it on your own data rather than in a slide deck — thirty minutes with someone from the product team.