On Elena's day off, Luis needs to answer a basic question: “Can I offer a discount because the customer's part is late?”
He finds an old chat message, a meeting summary proposing automatic discounts, and the current policy requiring manager approval. The difficulty is knowing which source governs the decision.
A useful internal knowledge service helps staff find an applicable answer, inspect its source, and reach a responsible person when the information is missing or conflicting.
Mesa Equipment Service and the events in this chapter are fictional. The service design and operating targets are proposed examples.
Your result from this chapter: a defined staff-question workflow with source owners, access rules, escalation, maintenance, and measures of usefulness.
Start with the questions people actually ask
Collect recurring questions from permitted support requests, staff interviews, and observations of the work. Keep identifying information out of the collection unless it is needed and authorized.
Ask where people get stuck: finding a procedure, identifying the current policy, understanding an exception, or locating the person who can decide.
Choose a narrow initial scope. Mesa starts with inspection fees, booking procedures, delayed-parts updates, and approval boundaries. Private employee matters and financial account administration remain outside the coordinator-facing service.
The service may use a searchable document collection, an AI assistant, or both. If a clearly organized page answers a common question well, make that page easy to reach.
Give the service a visible purpose
Tell staff what it covers, which sources it uses, and what happens when it cannot answer. Give it a responsible owner and a backup.
A simple service card might say:
| Field | Fictional Mesa example |
|---|---|
| Audience | Authorized service staff |
| Purpose | Find current operational guidance and route unresolved questions |
| Covered sources | Approved service policies and operating procedures |
| Excluded uses | Private employee records, payment approvals, and independent policy changes |
| Service owner | Operations owner |
| Source owners | Named owner for each policy or procedure |
| Fallback | Open the approved source directly or contact the designated person |
Avoid promising instant definitive answers to every question. Staff need a reliable path to resolution, including when that path goes to a person.
Make the authoritative source easy to recognize
For each important document, record its title, stable identifier, owner, approval status, effective date, audience, and review trigger.
Useful document states are:
| State | How ordinary staff questions should treat it |
|---|---|
| Draft | May inform review; must not be presented as approved policy |
| Approved and current | Available for applicable current-policy answers |
| Superseded | Excluded from ordinary current-policy answers; retained for authorized history |
| Withdrawn or under investigation | Clearly unavailable for reliance until the responsible owner resolves it |
Do not let a new meeting note silently outrank an approved policy. A proposed improvement becomes policy only through the business's approval process.
For Mesa, the discount proposal in the meeting remains unapproved. SERVICE-01 continues to require manager approval. The delayed-parts procedure is a draft until the owner approves it, and backup coverage is unresolved.
Design the staff-question workflow
Use the source-based answering practices from Chapter 8, then add an operational path:
- Receive the question. Identify the actual job the staff member is trying to complete and their authorized role.
- Find permitted evidence. Search the current applicable sources the person may access.
- Prepare an answer. Give the rule, conditions, and source location. Identify missing facts.
- Route unresolved work. Assign an owner when the question needs a decision, a source correction, or new information.
- Confirm the outcome. Record whether the staff member could complete the task and whether the answer needed correction.
- Improve the source. Let the document owner decide whether a recurring gap calls for an approved update.
A question can be answered while the business action still requires approval. Keep those states separate.
Work through the discount question
Luis asks:
“The part is late. Can I give the customer a discount now? The meeting notes mentioned automatic discounts.”
The permitted source set includes SERVICE-01 and the meeting record from Chapter 11. The proposed delayed-parts SOP is marked draft.
An acceptable illustrative answer is:
“SERVICE-01 requires manager approval before a discount or refund is promised. The meeting recorded automatic discounts as a proposal and made no change to that rule. Ask the manager to decide this case before offering compensation.”
The answer should point to the policy clause and the relevant meeting note. It should not say a discount is forbidden in every case; the rule requires approval. It should not imply that merely asking the assistant constitutes that approval.
If the service cannot access the current policy, it should identify the gap and route the question. It should not reconstruct policy from a colleague's old chat message.
Use a prompt that supports the workflow
Help an authorized staff member find current operational guidance.
Use only the permitted sources supplied for this role. Preserve each source's
approval status, effective date, owner, and relevant conditions.
Return:
- A concise answer supported by current applicable evidence
- Source IDs and locations the staff member can inspect
- Any approval or action the answer does not itself authorize
- Missing or conflicting information
- The responsible owner or next step if resolution is needed
Do not turn drafts, suggestions, or prior chat messages into approved policy.
Do not invent a source owner if none is recorded. Flag the ownership gap.
Do not modify a policy, create an approval, or change access permissions.
The application must control which sources enter the task. The prompt expresses the desired answer behavior; it does not enforce access by itself.
Fix permissions where the documents live
An assistant that follows existing access rules can still expose information that was shared too broadly. Review the source permissions as well as the assistant's configuration.
Microsoft documents that Copilot surfaces organizational data within users' underlying permissions. That makes correct sharing in the source systems important; it does not make every existing permission appropriate. Microsoft Copilot privacy and permissions.
Test representative roles in the actual application. A service coordinator and a manager may have different authorized collections. Check answers, search previews, attachments, caches, and logs, including after a person's access changes.
Use synthetic restricted records for planned access tests where possible. Text-only examples in this guide cannot demonstrate that a deployed system's permissions are working.
Treat unanswered questions as work
Provide a way to report “missing,” “wrong,” “outdated,” and “conflicting” answers. Ask for the question, cited source, and reason the answer did not help, using only information appropriate for the feedback system.
Assign the issue to someone. If no document owner exists, the service owner must resolve that gap rather than sending staff around in circles.
Choose a response target the team can actually support. For the fictional pilot, Mesa proposes reviewing ordinary unanswered questions during the next business day's operations review. That is a suggested local target, not a universal service standard. Urgent matters must follow their established escalation route immediately.
Tell the staff member when an issue is resolved and where the approved answer now lives. A feedback form that disappears into an unattended inbox will quickly lose trust.
Update the source before teaching the assistant a new answer
When a recurring question reveals missing guidance, have the responsible person decide the answer and update the approved source. Record the approval and effective date.
Refresh the assistant's source collection or search index as required by the tool. Rerun questions affected by the change, including examples that should now receive a different answer. Check that a current-policy question no longer relies on the superseded version.
A staff correction typed into a chat may improve that conversation without updating the shared knowledge system. Do not assume the assistant has permanently learned a new rule or that every user will now receive it.
Keep a record of changes and retain needed history. This lifecycle approach is consistent with NIST's emphasis on governing and managing AI risks in context over time. The framework is voluntary guidance, not a certification of this service. NIST AI Risk Management Framework.
Test the absence of the usual expert
Ask whether someone other than Elena can find the current procedure, understand its limits, and route an exception. Use a permitted practice task and observe where they need undocumented help.
Do the same when the assistant is unavailable. Staff should be able to open the approved documents directly or contact a named backup. Keep appropriate exports or backups where the business's records policy permits them.
For a nonprofit, this might mean helping a new volunteer find the approved intake procedure while keeping private case information out of the general knowledge service. For an online shop, it might mean finding the correct return rule without exposing supplier costs to every user.
Measure resolution, accuracy, and maintenance
Track whether staff completed the task, whether the answer was supported by the right source, how much time was spent, and whether a human escalation resolved the issue. Track maintenance effort and recurring source gaps too.
An illustrative set of twenty staff questions might produce twelve supported answers, five useful escalations, and three unresolved questions. That is a 60% supported direct-answer rate. It is not proof that 85% of tasks were completed: the five escalations may still be open.
Likewise, fewer questions to a manager might mean the service is useful, or it might mean staff have stopped asking and are guessing. Pair counts with observed task outcomes and feedback.
Include subscription and usage charges, source maintenance, answer review, and escalated support when assessing cost. A service that saves five minutes per question but requires hours of unmanaged document repair needs a different operating plan. Compare total effort and accepted task outcomes over the same period, and keep staff capacity separate from cash savings.
Your next step: use the knowledge-service card and issue queue to design one limited service. Part 4 will apply the same evidence and review habits to marketing and sales.