Technology AI

A reception knowledge base for consistent answers

How to build and maintain a reception knowledge base so every patient gets the same approved answer: structure, entry template, owners, reviews and gaps.

Ava research teamPublished 6 min read

On this page
  1. Why answers drift
  2. What belongs in it
  3. Anatomy of a good entry
  4. Writing rules for every entry
  5. Building it in a month
  6. Owners, reviews and change control
  7. One source for every channel
  8. Where the knowledge base stops
  9. The gap log
  10. Example: one entry, start to finish
  11. Measures worth tracking
  12. Frequently asked questions
  13. References

Key takeaways

  • A knowledge base turns each receptionist's private notes into one approved set of answers the whole team uses.
  • Every entry needs a short answer first, the detail second, an owner and a review date.
  • Use the same entries for staff, the website and any phone tool, so patients hear one answer everywhere.
  • Log every question nobody could answer; that list is your build plan.
  • Clinical questions are routed, never answered from the knowledge base.

Why answers drift

Ask five receptionists how a patient orders a repeat prescription, gets a fit note or books a smear test, and you may get five slightly different answers. Each is usually reasonable, built from experience and a few sticky notes. The trouble is that patients compare notes, rules change, and a slightly wrong answer creates a second call, a complaint or a wasted appointment.

Consistency matters to patients. In the 2026 GP Patient Survey, 76.7% rated their practice good overall and 72.6% rated their last contact experience good, but only 56.9% said they were offered a choice of time or day for their appointment[1]. Small, consistent improvements in how requests are explained are one of the cheapest ways to move those numbers. NHS England's access plan also expects patients to know on the day how their request will be handled[2], which is only possible if every member of the team explains the process the same way.

GP Patient Survey 2026: selected results
GP Patient Survey 2026: selected resultsBar chart. Rated their practice good overall: 76.7%; Rated last contact experience good: 72.6%; Offered a choice of time or day: 56.9%.Rated their practice good overallRated their practice good overall: 76.7%76.7%Rated last contact experience goodRated last contact experience good: 72.6%72.6%Offered a choice of time or dayOffered a choice of time or day: 56.9%56.9%GP Patient Survey 2026: selected resultsBar chart. Rated their practice good overall: 76.7%; Rated last contact experience good: 72.6%; Offered a choice of time or day: 56.9%.Rated their practice good overallRated their practice good overall: 76.7%76.7%Rated last contact experience goodRated last contact experience good: 72.6%72.6%Offered a choice of time or dayOffered a choice of time or day: 56.9%56.9%

Source: Ipsos (GP Patient Survey provider for NHS England), 2026[1]

Show the data
ItemValue
Rated their practice good overall76.7%
Rated last contact experience good72.6%
Offered a choice of time or day56.9%

What belongs in it

  • Practice information: hours, closures, sites, parking, access, how to reach each team.
  • Processes: registration, appointments, repeat medicines, fit notes, test results, letters and forms, records requests, complaints.
  • Services and self-referral: what the practice offers, which services patients can refer themselves to, and what Pharmacy First covers.
  • Local services: pharmacies, community services, urgent treatment centres, dental access and mental health support, with current contact details.
  • Urgent-help wording: your agreed 999 and NHS 111 wording, word for word.
  • Policies in patient language: missed appointments, zero tolerance, chaperones, confidentiality.
  • Contacts for staff: who to escalate to, internal extensions, supplier helplines.

Signposting entries deserve particular care. Community pharmacies had delivered 3.05 million Pharmacy First consultations by the end of February 2026[3], and patients are far more willing to use the route if the receptionist can say exactly what it covers and where the nearest participating pharmacy is.

Anatomy of a good entry

A template for each knowledge base entry
FieldWhat it holdsFictional example
QuestionThe question as patients ask itHow do I get a sick note?
Other ways people askWords patients actually usefit note, doctor's note, note for work
Short answerTwo sentences a receptionist can sayFill in our online form or ask at reception. If you've been off for seven days or less, you can self-certify with your employer instead.
DetailSteps, exceptions, timescalesWhen a clinician is needed, extensions, hospital discharges
Do notCommon mistakes to avoidDo not promise a date; do not ask about symptoms
Route if unsureWho to pass it toAdmin team task list
Owner and review dateWho keeps it right, and when it is next checkedPractice manager, every six months

Write the short answer in the words you want patients to hear. If it cannot be said in two sentences, the process may be too complicated, and that is worth knowing too.

Writing rules for every entry

Agree a short style guide before anyone writes, so entries read as if one person wrote them. That makes them faster to scan during a call and easier to reuse on the website and in messages.

  • Plain English, written to be said aloud: short sentences, everyday words, no internal jargon such as 'ARRS', 'the hub' or a supplier's product name unless patients use the word too.
  • Lead with what the patient should do, then why, then the exceptions.
  • Give timescales the practice can keep. 'Usually within two working days' is better than a promise you will break in December.
  • Name places and services exactly as they appear on signs and websites, so patients can find them.
  • Avoid conditional chains of more than two steps; split them into separate entries instead.
  • Use the same terms everywhere: if the website says 'online form', the knowledge base does not say 'e-consult' in one entry and 'web request' in another.

Read a sample of entries aloud in a team meeting once a quarter. Anything that sounds awkward when spoken will sound worse to a patient on the phone.

Building it in a month

  1. Week 1: collect

    Ask every receptionist to note the questions they answer for a week, and gather existing notes, scripts and policies in one place.

  2. Week 2: draft

    Turn the twenty most common questions into entries using the template, and agree the urgent-help wording with a clinician.

  3. Week 3: check

    Have the owner of each process check its entries, and have a receptionist test each one on a colleague as if on the phone.

  4. Week 4: launch

    Make it the only approved source, remove old notes from desks and shared drives, and start the gap log.

Choose a tool everyone can search in seconds while on a call: a shared intranet page, a document with good headings, or a dedicated knowledge tool. The best tool is the one staff will actually open.

Owners, reviews and change control

A knowledge base is only as good as its maintenance. The commonest failure is an entry that was right when written and quietly became wrong.

  1. Give each section an owner: the person who runs that process, not just the person who wrote the entry.
  2. Set a review date on every entry, and a shorter one for anything seasonal such as flu clinics or bank holidays.
  3. Keep a change log showing what changed, when and why, so staff can see what is new.
  4. Announce changes in the daily huddle or team chat, and mark changed entries for a week.
  5. Archive old versions instead of deleting them, in case a complaint needs to show what patients were told.

One source for every channel

The same approved answer should appear on the website, in text messages, in the phone greeting and in any automated tool. When the knowledge base changes, the other channels change with it. That is the main way to stop patients hearing one thing on the phone and reading another online.

AI phone tools make this even more important, because they repeat whatever they are given. Ava, for instance, answers from the wording a practice has approved and says it is not sure when something is missing, so a well-kept knowledge base becomes its source as well as the team's.

Where the knowledge base stops

A knowledge base is for practice information and processes. It is not a triage tool, and it should never invite receptionists to judge symptoms. Entries that touch on clinical matters, such as when to seek urgent help, should be written and signed off by a clinician and should route the patient rather than advise them.

Rule for every entry: if answering would need a clinical judgement, the entry says who to route to and nothing more.

The gap log

Keep a simple log of every question that could not be answered from the knowledge base, with the date and who asked. Review it weekly. Each repeated gap becomes a new entry; each one-off goes to the right owner. Over a few months the log shows where processes are unclear to patients, which is useful well beyond reception.

The log also helps with workload. In a BMA survey of more than 1,300 practices, 74% reported that workload rose after the online access changes[4]. Questions that keep appearing in the gap log often point to the parts of a new process that patients do not understand, and fixing the explanation once is cheaper than answering it a hundred times.

Example: one entry, start to finish

Example (fictional): the gap log at a coastal practice shows six calls in a week asking whether the practice offers travel vaccinations.

In this example the practice nurse writes the entry: which vaccines the practice gives on the NHS, which it does not, how much notice patients should give and where to go for private travel clinics. The short answer reads: "We give some travel vaccines free on the NHS. Please fill in our travel form at least eight weeks before you go and the nurse will contact you." The website and phone greeting are updated the same day. The gap log shows no further questions on the subject the following month.

Measures worth tracking

  • Entries past their review date, which should be none.
  • New gaps logged per week, which should fall over time.
  • Repeat calls about processes covered by the knowledge base.
  • Complaints that mention being given wrong or conflicting information.
  • Time for a new receptionist to handle common calls without help.

Frequently asked questions

What is a reception knowledge base?

A single, approved set of answers to the questions patients ask, which every member of the reception team uses so that patients get the same answer from everyone.

How often should entries be reviewed?

At least every six months, and more often for seasonal or fast-changing information such as clinics, closures and local services.

Should the knowledge base include clinical advice?

No. Clinical entries should route the patient to the right service or clinician, using wording a clinician has signed off.

What tool should we use?

Whatever the team can search in seconds during a call, such as an intranet page or a well-structured shared document.

References

  1. Ipsos (GP Patient Survey provider for NHS England) (2026). 2026 GP Patient Survey results released (opens in a new tab) ↑

  2. NHS England and DHSC (2023). Delivery plan for recovering access to primary care (opens in a new tab) ↑

  3. NHS England (via GOV.UK) (2026). NHS England annual report and accounts 2025 to 2026 (opens in a new tab) ↑

  4. British Medical Association (2026). Pressures in general practice data analysis (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo