Use Cases / Employee support / An explanation with a source
Policy guidance
Help employees understand published workplace guidance and find the team that handles individual questions. Start with a maintained source and a clear distinction between explaining a policy and deciding a person’s case.
Picture the work
Understand a travel-expense submission process
Illustrative configured agent role over selected knowledge. Expense-system access, personal eligibility checks, and request submission are separate integration scopes.
An employee asks which supporting documents a travel-expense request needs.
A configured agent finds the permitted published guidance and links to its source.
The employee notices an unusual expense and asks which team handles exceptions.
The employee uses the named review route rather than treating the explanation as approval.
01 / A closer look
Explain the guidance in its stated context
A policy may distinguish locations, teams, or types of expense. The explanation should preserve those distinctions and ask for clarification when the employee’s question does not identify the relevant context.
- Point back to the published source used for the explanation.
- Make missing context and unclear applicability visible.
General guidance and individual records
Explaining the documents usually needed for a request does not require the employee’s entire personnel file. Personal balances, eligibility, or prior approvals require explicitly scoped access to the relevant system.
- Begin with shared policy information.
- Add personal lookups only where the task and access path justify them.
Give exceptions a responsible destination
When the published guidance does not settle the question, identify the responsible team and the context it needs. An agent’s proposed interpretation is not an approval or a change to policy.
- Keep the review route part of the guidance.
- Let the policy owner resolve conflicting or unusual cases.
02 / A closer look
Maintain answers through human publication
Nexus supports draft guidance, published versions, and source review. A permitted agent can draft a clearer explanation for the policy owner. Human publication keeps the decision about official wording with the people accountable for it.
- Review wording that employees repeatedly misunderstand.
- Retain the published source and the reasoning behind a revision.
03 / A closer look
Test a focused knowledge role
Configure an illustrative policy-help role in Agent Foundry using available knowledge tools, or build a custom experience in App Studio. Validate downstream identity and source permissions for the chosen path. Test ambiguous questions, personal requests, and topics outside the selected guidance as well as ordinary questions.
- Use read-only tools when the job is explaining guidance.
- Validate administrative registration and compatibility for a Nexus-hosted agent.
The care behind useful AI
Respect the distinction between guidance and authority
Source permissions, personal-data access, and approval authority belong in the support brief. Fabric helps frame those boundaries; the connected systems retain their own relevant authorization checks.
Discover what's beneathRun it your way. Explore your deployment choices
Where could this take you?
Follow the next useful question.
A conversation about your work
Let's talk.
Bring one policy employees often ask about and an example of an exception. Explore a sourced explanation and a clear review route with a Practicus engineer.
A 45-minute session with a Practicus engineer: no sales pitch, real value.
Bring your question