New device request: from request to signed custody
An employee needs a laptop with design specs. The request passes the manager, finance because the value is above the threshold, then stock or procurement, then preparation. This journey shows it happen without a single follow-up message.
The journey, step by step
Click any step or use the buttons to see the ticket status.
- Request
From the catalog: device type, justification, cost center.
Employee - Manager approval
One click from email.
Manager - Finance approval
Required above the value threshold.
Finance - Stock
Not in stock; a purchase request is raised.
Inventory - Receive & prepare
OS and software installed, registered as an asset.
Hardware team - Handover
Custody signed on mobile.
Employee - Close
Device in the asset register under the employee; service rated.
System
Before and after
| Aspect | Without a system | With TixDesk |
|---|---|---|
| Approvals | Forgotten emails | Sequential and value-based |
| Follow-up | "Where is my request?" | Status visible in the portal |
| Purchase | Outside any record | "Waiting for vendor" state |
| Custody | Paper | Digital signature |
| Asset | Not always registered | Registered automatically |
Features used in this journey
Service catalog
The request.
Value-based approvals
Sign-offs.
Asset management
Custody.
SLA
Pausing.
Portal
Tracking.
Integrations
ERP for purchasing.
Questions about this case
Can the purchase request link to our ERP?
Yes, via integration to raise and track the purchase.
Can specs depend on the role?
Yes, with form options by title or department.
See the journey on your requests
We apply this case with your details in a live demo.
- A scenario from your reality
- Your teams and policies
- Direct answers