Common questions resolved without ticket creation
Grounded Answer Example
AI should help people find the right answer faster, but only from trusted sources and with clear citations.
User Question
"How do I request temporary staff access for a project worker starting next Monday?"
AI-Grounded Answer
To request temporary staff access, use the Request Intake page and choose Access request. Include the worker name, start date, end date, division, supervisor, business purpose, and the named approver before submission. Access work cannot be completed until the approver is confirmed.
- Use the intake path instead of email or chat so the request is tracked.
- Attach any role or system details if special access is needed.
- If the start date is within 2 business days, mark the timing reason clearly in the request.
Recommended next action: Open `Request Intake` and start an Access request.
Approved Source References
KB-1104 Temporary Staff Access Guide
Owner: Identity service owner | Last reviewed: Apr 2026
POL-2108 Access Approval Standard
Owner: Security and governance | Last reviewed: Mar 2026
SR-1002 Request Intake Field Rules
Owner: Service desk | Last reviewed: Apr 2026
Knowledge Service Lanes
Not every question should become a ticket. The platform should direct people to the right path on purpose.
Self-Service
Use when the action is safe, repeatable, and well documented.
Policy Answer
Use when the person needs guidance on what is allowed, required, or who must approve it.
Route To Intake
Use when the request needs tracking, approval, ownership, or delivery work from IT.
Top Knowledge Domains
These are the content areas that drive the most value when kept current and grounded.
Temporary staff access, role-based approvals, and common identity questions.
Workspace ownership, lifecycle rules, and publishing guidance.
Request expectations, common reporting issues, and known data refresh constraints.
Energy Strategy updates, content workflow, and publish-readiness checks.