Resources / Knowledge maintenance

Create a source register for public office facts

Give staff a way to verify where an answer came from.

01

The operational decision

Give staff a way to verify where an answer came from. An answering assistant needs a controlled set of office facts. More uploaded material is not automatically better: old instructions and internal documents can make a public answer less reliable.

02

Prepare the workflow

Assign an identifier to each fact and record its approved public source; keep source ownership separate from whoever types the wording.

03

Example wording for approval

“The answer about this fictional entrance comes from the office-approved directions sheet. If that sheet changes, this answer needs a fresh review.”

04

Worked example

The fictional answer Parking is free appears in three scripts, but nobody can identify its source. Mark that claim unverified and ask the office owner to confirm the actual public policy. Once approved, connect each answer to the same fact identifier. A later change then has a clear set of places to update. The source register should store the public rule and approval history; it does not need visitor receipts, appointment records or recordings of people asking about parking.

05

Handoff record

Record these task-specific fields: fact identifier, source URL, source owner, reviewed date.

06

Acceptance check

Ask the editor to trace a single answer to its source. If the chain ends at an old chat message, obtain a current office approval.

Front-desk time calculator ↗

Try Ava with your business’s public information ↗

Related guides

Your workflow, first

Let’s map your first week.

Bring the calls you want covered. We’ll agree the script, handoff and limits.

Start a pilot