Look at a month of support enquiries and the shape is always the same. A long tail of genuinely unusual questions, and a very short head of the same handful asked over and over.
Delivery times. Returns. Whether you ship to New Zealand. Whether that thing comes in blue.
Paying an AI to compose a fresh answer to "how long does delivery take" four hundred times is paying four hundred times for one piece of work.
What gets cached
When an anonymous visitor asks a question and gets a clean, well-sourced answer, that answer is stored. The next anonymous visitor asking the same thing gets it immediately, with no API call.
The matching is smarter than exact string comparison. Questions are reduced to their meaningful words with the filler removed, then sorted, so "what is your refund policy" and "refund policy, what is it" resolve to the same cached answer. Customers do not phrase things consistently and the cache does not require them to.
What deliberately is not cached
Logged-in customers. Their answers can include their own orders and account details, and that must never be served to somebody else. Anything personalised skips the cache entirely.
Anything that used a tool. If answering involved looking up an order, checking stock or reading shipping zones, the answer reflects a moment in time and is not reused.
Rejected answers. Only answers that passed the grounding check are stored, so a bad answer cannot be cached and repeated.
Staying fresh
A cached answer about your delivery times is a liability the day you change your delivery times.
So the cache clears itself whenever the underlying facts could have moved: after your content is reindexed, and whenever you save your AI settings. Entries also expire after thirty days regardless, and there is a manual clear button for when you have just edited something important and want it gone now.
The rule is that a cached answer never outlives the content it came from.
What it saves you
The cache screen shows how many answers are stored, how many times they have been served, and what that has saved, along with the twenty most-hit questions.
That last list doubles as insight. The questions your cache serves most are the questions your site answers worst, in the sense that people are having to ask rather than finding it. Several of them usually belong on a page, in your navigation, or in your product descriptions.
Nothing to configure
Caching is on. There is no setting, because there is no scenario where you want to pay repeatedly for the same answer while your content sits unchanged.