Separate department contacts by public purpose

The operational decision

Prevent a caller from being sent to a department merely because its name sounds relevant. A contact directory is useful only when each destination has a clear purpose. A publicly listed telephone or mailing address can be shared without collecting the details of a patient request.

Prepare the workflow

Define each public department label and the questions staff approve for that route; avoid collecting details to make a clinical routing decision.

Example wording for approval

“For general billing-office contact information, use the published billing number. Questions about your own account should be discussed directly with that team.”

Worked example

A fictional office publishes reception and billing contact numbers but no public laboratory number. Someone asks for the laboratory because they want a result. The assistant should neither guess a department extension nor collect the test details to route the request. It gives the practice-approved patient contact instruction. The directory review records that the requested public route was absent and whether the fallback worked, without turning the absence into an invented departmental service.

Handoff record

Record these task-specific fields: department label, public remit, published number, directory owner.

Acceptance check

Ask for a department not in the directory. The assistant should use the general office route instead of inventing a number.

Related guides