Feature
Knowledge Base Management
The knowledge base is the complete set of things your AI receptionist is allowed to say. Nothing outside it is answered, which is what makes the system safe to put in front of customers.
What it typically contains
- Services, scope and what you do not offer
- Hours, locations, access and parking
- Published prices and fee structures
- Documents and preparation requirements
- Policies on cancellation, deposits and returns
Approved Information, and Nothing Else
The most common fear about AI answering is that it will say something wrong. The knowledge base is the answer to that: a defined body of information your business has approved, with everything outside it routed to a person.
Building it is mostly a collection exercise. Much of what your team says on the phone has never been written down, so the process itself often improves internal consistency regardless of the deployment.
Maintaining it is the ongoing part. Prices change, services are added, policies are revised. A knowledge base that is not updated becomes a source of wrong answers, so we treat updating it as part of the service rather than an optional extra.
What It Delivers
Answers you can stand behind
Every response comes from text your business signed off, not from a general model’s assumptions.
One version of the truth
Staff and system give the same answer, which resolves inconsistencies your customers already notice.
Gaps become visible
Questions the system could not answer are logged, showing exactly what to add next.
Changes apply instantly
An updated price or policy takes effect on the next call, across every branch at once.
How It Is Maintained
Initial build
We collect what your team says today, structure it, and put it in front of you for approval.
Ownership assigned
Someone in your business owns the content, because approving what may be said is not a technical decision.
Gaps reported
Unanswered questions from real calls are collected and reviewed, usually monthly.
Updates applied
Approved changes go live immediately and are recorded so you can see what changed and when.
Where Accuracy Is Non-Negotiable
Restaurants
Allergen and dietary information must come from the kitchen, stated exactly as confirmed.
RestaurantsCorporate secretarial firms
Process and deadline information changes, and an outdated answer creates a compliance problem.
Corporate secretarial firmsMedical clinics
Preparation instructions and fee information must match what the clinic actually applies.
Medical clinicsDeployment Notes
A single business usually has one owner and one approval step, described under small business deployments.
Networks separate shared content from branch-specific detail so a central update does not overwrite local information, covered under franchise deployments and in the feature library.
Knowledge Base Questions
What happens if a question is not covered?
The system says it cannot answer and follows your fallback rule. It does not improvise, and the gap is logged for review.
Who updates the content?
You approve, we apply. Larger deployments can be given direct editing access with permissions.
How often should it be reviewed?
Monthly works for most businesses, with immediate updates whenever prices or policies change.
Can it pull information from our website?
Website content can seed the initial build, but everything is reviewed before use. Published pages are often out of date in ways nobody has noticed.
Will it ever guess?
No. Declining to answer is the designed behaviour, and it is far preferable to a confident wrong answer.
Decide What Your System May Say
Send us your service information and policies. We will structure the knowledge base and show you exactly where its limits sit.