Source
Service desk, incidents & requests — found from sitemap — Xurrent ITSM
Checked for Xurrent ITSM on 1 Nov 2026
- Page
- https://www.xurrent.com/help/requests-service-desk-overview
- Checked
- 1 Nov 2026, 10:17 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:4fd0a589b799904f737acf3a4919196c99a60a89e2e05d500cd4c94eaf93aefd
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Request record Report an error
“A request is the core record of request fulfillment. It captures one thing a person needs from a service, an incident to resolve, a change to make, information to provide, or an item to order, and tracks it from registration through to completion.”
-
Service desk analyst role Report an error
“The Service Desk Analyst is the front line role that registers requests and moves them through their lifecycle.”
-
Service instance routing Report an error
“The service instance determines the Team the request is assigned to and the SLA targets that apply.”
-
Category fields Report an error
“The category determines which fields and context the analyst sees.”
-
Incident category Report an error
“An incident category routes to service restoration.”
-
Rfc category workflow Report an error
“The RFC category starts a change, which is then carried out by a workflow.”
-
Request template Report an error
“See Request for the record fields, Request Template for registering recurring requests quickly, and Service Level Management for how targets are applied.”
Scores citing this record
- The Change & Configuration Manager Service desk, incidents & requests
- The MSP Owner Service desk, incidents & requests
- The Municipal IT Lead Service desk, incidents & requests
- The Service Desk Lead Service desk, incidents & requests
- The Skeptic Service desk, incidents & requests
- The Solo IT Admin Service desk, incidents & requests