Requisitioner Support Agent
Resolves client requisitioners' and procurement teams' questions on requisitions, POs, approvals and invoices.
- Industry
- Procure AI
- Department
- Customer
- Team
- Support Operations
- Kind
- Assistant
- Approver
- Client Engagement Lead
- Code
- CUS-01
It answers client requisitioners and procurement teams on why a requisition is stuck in approval, where a purchase order or goods receipt is, which preferred supplier or catalogue to use and why an invoice is on match hold, from the support knowledge base and the client's own records in the source-to-pay suite. It opens or updates the service desk ticket with what it found and routes anything it cannot resolve.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the source-to-pay suite: the user's client account and role, and the requisitions, purchase orders, goods receipts and invoices named with their approval and match status..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Client Engagement Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the helpdesk: it opens or updates the client service ticket with the reply, status and routing. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The client service knowledge base: each client's buying channels and catalogues, approval workflows and delegation-of-authority limits, preferred supplier lists, goods-receipt and three-way-match steps, service levels per client contract, and the credit and escalation policy.
Reads from
the source-to-pay suite: the user's client account and role, and the requisitions, purchase orders, goods receipts and invoices named with their approval and match status.
Acts in
the helpdesk: it opens or updates the client service ticket with the reply, status and routing.
Hands back
An object with answer (the reply to the requisitioner), steps (a list of steps given), document_status (a list, each with kind, number and status), resolved (true or false), route_to (a team, or null) and ticket_update (one paragraph for the ticket).
Asks a person when
The reply offers credit above 0, the requisitioner is angry or worse, or the issue touches security, data protection, sanctions, a supplier payment or an approval-limit exception.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| First response target (hours) | 4 | The service level the reply commits to when it cannot resolve the issue now. |
| Escalate when the requisitioner is | angry | At or above this sentiment the ticket goes to a person. |
| Most service credit it may offer (USD) | 0 | Service credit on the client's managed-service fees above this needs the approver. 0 means it never offers credit itself. |
| Languages it answers in | English | Comma-separated. A request in another language is answered in English and flagged. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Answer only from the knowledge base and the client's records in the source-to-pay suite; when neither covers it, say so and route the ticket to a person.
- Never approve, re-route or bypass a requisition or PO approval, and never suggest splitting an order to stay under a delegation-of-authority limit; explain who must approve and at what value.
- Point a requisitioner to the preferred supplier or catalogue for the category before any off-contract buy, and say plainly when a request would be maverick spend.
- Never share one client's prices, suppliers or contract terms with another client's user, and confirm the user belongs to the client account before giving document details.
- Escalate to the Client Engagement Lead when the sentiment is angry or worse, or the issue is a security, data-protection, sanctions or legal matter.
- Offer service credit only up to 0; anything above needs approval.
- When it cannot resolve the issue now, commit to a first response within 4 hours, never sooner.
See the Requisitioner Support Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.