Enterprise use case · Personio + ServiceNow + OpenAI
HR request classification and routing
Free-text HR requests arrive without consistent categories and can expose sensitive details when passed between broad queues. Employee requests reach the authorized HR owner with a proposed category and a reviewable response draft.
Systems involved
What each system contributes
The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
Architecture
One governed run
How it starts: An employee submits a request through the designated ServiceNow HR intake process.
Step by step
How the process runs
- 01
Read permitted context
Retrieve the request and the minimum authorized Personio person or document references needed for its handling.
- 02
Classify the request
The selected model proposes an allowed category, separates multiple issues and identifies missing information.
- 03
Check routing boundaries
Rules map the category to an authorized ServiceNow owner and keep sensitive requests out of general service queues.
- 04
Draft an answer
For supported categories, the model drafts from approved policy text and states when the evidence does not answer the request.
- 05
Release the reviewed response
The HR owner approves the answer before the workflow publishes it or applies any separately authorized record change.
Control
Human decision and exception path
Human decision
A named HR owner reviews employee-specific advice and any proposed change to an HR record. Requests affecting access, compensation or employment outcomes require the relevant authority before a separate action proceeds.
Exception path
- Unclear or mixed requests go to HR triage with the model's uncertainty visible.
- Missing or conflicting policy evidence stops the answer draft and requests an HR decision.
- Unauthorized destination access blocks routing rather than broadening visibility to make delivery succeed.
Evidence
What gets audited
- Request reference and permitted Personio context.
- Category proposal, routing rule and policy version.
- Draft answer, supporting passages and HR approval.
- Final response or approved update and destination result.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- Workday-ServiceNow integration
Integration pattern · Employment changes become traceable IT work with named owners and completion evidence.
- Personio connector
12 pre-built actions
- ServiceNow connector
55 pre-built actions
- OpenAI connector
25 pre-built actions
- Governed self-service
Requests with policy and approval built in.
- Order to cash across CRM, ERP and billing
Another enterprise use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- An employee submits a request through the designated ServiceNow HR intake process.
- What if a step is not covered by a pre-built action?
- The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
- Will a sensitive request appear in the general IT queue?
- The routing design restricts categories and destinations to authorized HR owners; failed access checks hold the request instead.
- Can the model make an exception to company policy?
- No; it can identify a possible exception request, but the authorized HR owner decides and approves the response.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.