Consistency means patients receive a dependable administrative response wherever they contact the business. It does not mean every location has identical capacity or that reception should answer clinical questions beyond its role.
Standardise the essential information
Agree the minimum enquiry record: contact details, preferred location, service requested, contact preference, next action and owner. Collect only information required for the administrative task. Define when the request needs clinical or other specialist review.
Use shared definitions for new enquiries, duplicates, bookings and unresolved requests. Otherwise a branch comparison may measure different things under the same label.
Keep local constraints visible
Maintain current service availability, opening hours and booking rules for each location. A central team should not promise an appointment based on an old schedule. Name the person responsible for updating branch information.
Define acceptance between locations. If a request is redirected, the receiving team should acknowledge it and inherit the relevant context. Tell the patient what will happen next without making unsupported promises.
Sample real journeys at each branch, including out-of-hours enquiries, incomplete details and requests sent to the wrong location. Measure correct routing, response quality and unresolved age alongside speed.
Use the existing clinic enquiry-routing and reception-model guides as the starting point. Then document a short shared standard with location-specific appendices. A consistent system combines common rules with accurate local information and an explicit human handoff for questions outside reception's authority.
Existing guides: Clinic enquiry routing · Reception model · Pilot design.