01
Retrieval before generation
A grounded assistant searches your approved content first, then writes an answer constrained to what it found. That single architectural decision does more for accuracy than upgrading to a larger model.
It also makes the system auditable: you can show exactly which document produced an answer, and correct the document rather than the prompt.
02
Design the refusal, not just the answer
A good assistant knows what it does not know. Setting an explicit confidence threshold, and a clear behaviour below it, is what makes a bot safe to put in front of customers.
- Below threshold, offer human handover rather than a guess
- Never invent prices, availability, policies or medical guidance
- Log every refusal — it is your content backlog
03
Measure the gaps, not just the deflection rate
Deflection rate tells you how much work the bot absorbed. The list of unanswered questions tells you what to improve. Teams that review that list weekly see accuracy climb quickly in the first two months; teams that only watch deflection plateau.