Identity and role
A short-lived assistant session carries the delegated user context. It does not give that user administrator access.
Input
Start with your account and the relevant record
Scope
Account permissions and client, partner and warehouse filters apply to business requests. An unauthorised tool remains unavailable.
Business context
Provide the reference, problem and intended outcome. Review the displayed records and sources before making a decision.
Tools
Three practical starting points
Find the work to review
- open an order by ID or reference in the authorised screen
- open receiving, returns or shipment exceptions
- open stock reservations for review; opening the screen does not change them
Prepare the next step
- check that the action is available and provide its parameters
- review that action’s confirmation and dry-run requirements
- create a support ticket with a case summary from an authorised client context
You keep the decision
Each supported action has its own requirements
Request
Name the record, intended action and parameters.
Evidence
Review the available information; a written answer does not replace the business record.
Preview
Preview availability depends on the action. Review its parameters and required confirmations before submission.
Approval
When required, confirmation is bound to the action, user and submitted content. Some actions still require confirmation in the business screen.
Result
Read the service result: success, denial or failure. Check the record before retrying an operation with an uncertain outcome.
Controlled actions
A support handoff creates a trackable case
What is passed on, and the limits
To send a request to support, the assistant needs a delegated user linked to a client and a summary. A numbered ticket is then created with the available context, sources and results.
Ticket creation is audited. It does not guarantee immediate assignment or a response time; follow-up continues in support.
For your own SDK agent, define access, permitted operations and error recovery separately from the assistant’s confirmation flow.
The assistant has no general permission to execute. Disabled tools, insufficient rights, expired confirmations and invalid state changes can block an action.
Choose a use case to set up
Tell us the role, record to find, intended action and support needs. We will identify the available tools and required confirmations.