Cerbo EHR · Governance

Call Quality & QA for Cerbo AI Practices

A practical call quality routine for Cerbo practices using Katie: which summaries to review, what to check, and how findings become rule changes.

Quality is a habit, not a launch task

Launch day is when Katie's rules are newest and least tested against real callers. Real callers phrase things in ways no planning session predicted, and practices change their services, prices and staff all year. A short, regular review is how the phone experience stays right.

The review is also how staff come to trust the system. A team that has read the summaries and seen problems fixed is far more comfortable letting Katie take more of the calls.

Choosing what to review

In the first weeks, read a handful of summaries from every day. After that, a weekly sample is enough, chosen to cover each call type rather than only the easy ones. Always include every call your escalation rules marked urgent.

Read each summary the way the staff member acting on it would. Could they act without calling the patient back to ask something basic?

Include a few calls where nothing seemed to happen: a caller asked a question, got an answer and hung up. Those are where small inaccuracies in approved answers hide, because no staff member ever acts on them.

The review checklist

For each summary in the sample, ask:

  • Was the reason for the call captured clearly and in plain words?
  • Did the call follow the right path under your routing rules?
  • Were urgent situations handled under the escalation rules exactly as written?
  • Did the caller get accurate information about prices, hours and services?
  • Did the caller ask something Katie had no approved answer for?
  • Was the summary filed to the correct patient's chart in Cerbo?

From finding to fix

Most findings point to a rule, not to the call. If callers keep asking about a service Katie has no answer for, add an approved answer. If refill requests arrive without the pharmacy name, add the question. If an urgent call was handled correctly but the wording sounded cold, ask a physician to rewrite it.

Record each change in your change log with the reason. Next month's review then checks whether the fix worked.

Who reviews

Pair an operational reviewer, usually the practice manager, with a clinician for anything touching clinical calls or escalation. Clinicians' time is short, so give them only the clinical sample. Front desk staff are a valuable source too: they see every summary and notice patterns first.

Close the loop through the chart. MedReception Autopilot files summaries to the patient's chart in Cerbo from a staff member's signed-in browser, so a reviewer can open the chart and see what the practice did after each call, not only what the caller said.

Frequently asked questions

How much time does call review take?
More at the start, when rules are newest. After the first weeks, a short weekly session is usually enough.
Who can change Katie's rules after a review finding?
The practice sets the rules. Route changes through the owner you named, with physician sign-off for anything clinical.
Should we test with mock calls as well?
Yes, especially after rule changes. A staff member calling with a scripted scenario is the quickest way to confirm a fix. Keep a short library of test scenarios so the same checks can be repeated after every change.
What if we find a call that went wrong?
Treat it as a rule problem first. Fix the rule, record the change, and follow up with the patient as your practice normally would.

Ready to implement this for your Cerbo practice?

Book a demo and we'll walk through your specific Cerbo workflow: your scheduling rules, the call summaries MedReception Autopilot files to the chart, and after-hours coverage.