What you will learn
- How agents, tools and agentic workflows divide responsibility.
- How an incident-triage scenario should be bounded.
- Where ACLs, test cases, escalation and observability belong.
- Which project evidence matters for a ServiceNow AI role.
The scenario: triage without uncontrolled resolution
A new incident arrives with a short description. The agent may enrich the record, find relevant knowledge, recommend categorization and route it. It must not silently close a high-impact incident or expose records the requester cannot access.
Agent, tools and workflow
Define the triage goal, permitted decisions, evidence rule and escalation conditions.
Read only fields authorized for the user or runtime identity.
Execute narrow approved automations with auditable inputs.
Coordinate agents and steps without hiding responsibility.
Access and action controls
ServiceNow's platform controls still matter when an agent is involved. Test the runtime identity, ACL behavior, tool permissions and record visibility. A natural-language interface must not become a path around established access rules.
- Use a least-privilege identity for each tool.
- Separate recommendation from record-changing actions.
- Require human confirmation for closure, priority override or sensitive routing.
- Log inputs, selected tools, outcomes and escalation reasons.
- Disable or contain recurring triggers that behave unexpectedly.
Test in the playground before release
| Test family | Example | Expected result |
|---|---|---|
| Normal | Common password-access incident | Correct category, evidence and route |
| Ambiguous | “System is slow” with no service | Ask for required context |
| Permission | Requester asks about another user's case | Do not expose the record |
| High impact | Possible production outage | Escalate without autonomous closure |
| Tool failure | Knowledge search unavailable | Safe fallback and visible error |
What belongs in the portfolio
Include the scenario map, agent instructions, tool list, access matrix, five test families, sample traces, failure analysis and change-control plan. Screenshots alone show configuration; these artifacts show governed delivery.
Primary sources
Platform features vary by ServiceNow release and entitlement. Validate against the target instance before implementation. Last reviewed 12 August 2026.