Incident & Problem
Triage, routing and resolution with the trail auditors expect.
- Incident categorisation and routing
- Major incident process
- Problem and root-cause workflow
Service requests are easier to manage when ownership and approval steps are visible. We help configure ServiceNow workflows around the people handling the work and the systems they depend on.
Service requests move through inconsistent processes, making ownership and service reporting difficult to trust.
Configure request workflows, service ownership, integrations, and reporting around agreed operational priorities.
Reduce manual routing and repetitive status updates while reusing existing platform capabilities where appropriate. Compare the current effort and running costs before deciding whether the change is worth making.
Discuss Your Requirements
The most expensive ServiceNow mistake is customising the platform instead of configuring it. We stay on the upgrade path.
Triage, routing and resolution with the trail auditors expect.
Change control that protects production without blocking delivery.
A configuration database that is accurate enough to trust.
A request experience staff will use instead of emailing IT.
Flow Designer automation that removes manual triage.
Performance analytics tied to the commitments you have made.
We agree the first deliverable, review it with your team, and use that feedback to guide the next stage.
We review your current processes and how far they really follow ITIL.
Process and data model agreed before any configuration.
Built on the platform, staying on the upgrade path.
UAT with the teams who will live in it daily.
Ongoing enhancement across platform releases.
Most engagements start with a short discovery call. RASPSYS LLP will assess your ITSM maturity and tell you what is realistic.
We deliver for clients across the UK, US, UAE, Canada, and Australia - with teams that work in your time zone.
We configure rather than customise, so your next release is not a project.
Supporting IT organisations across the UK, US, UAE, Canada and Australia.
We fix the process before automating it; automating a bad process just makes it faster.
The questions we are asked most often about ServiceNow Services.
No. ITIL is a framework, not a rulebook, and organisations that implement it literally usually end up with approval steps nobody respects. We follow it where it earns its keep - incident, change, problem - and simplify where your organisation genuinely works differently.
Through Discovery plus reconciliation rules, not manual upkeep. A CMDB maintained by hand is out of date within weeks and then nobody trusts it. We scope it deliberately too: a smaller CMDB that is accurate beats a comprehensive one that is wrong.
It can, and this is the single most common cause of expensive ServiceNow estates. We stay within configuration and supported extension points wherever possible, and document anything that genuinely requires custom code so upgrade impact is known rather than discovered.
A core ITSM deployment - incident, request, change, knowledge and a service portal - typically runs 12-20 weeks. CMDB and Discovery add 6-10 weeks depending on estate size. We phase it so teams get working process early rather than waiting for one large go-live.
End-to-end Salesforce strategy, implementation and managed services.
You should be able to see what has been agreed, what is in progress, and what needs your input. Here is how we organise that work.
Have a workflow or backlog you would like us to look at? Tell us about it in an initial call.
Map one request type from intake through approval and fulfilment.
Identify which records need to move between systems, who owns them, and what should happen when an update fails.
Test approvals, reassignment, exceptions, and the status information available to the requester.
Show users how to complete their regular tasks and give the people maintaining the system a usable handover.
Keep unresolved requests and later ideas in a shared backlog, with a named owner and a reason for each priority.
Start with a piece of work you can assess on its own. We can then discuss a project, phased delivery, or ongoing support to fit the remaining workload.
Map one request type from intake through approval and fulfilment. Keep later additions in a separate backlog so the first phase stays manageable.
Your proposal should say what is included, what your team needs to provide, and what costs extra. Include licences and ongoing support in the comparison.
Agree who reviews the work and how they will check it. Record scope changes and confirm the handover before closing the project.
Tell us where the work gets stuck and what you have already tried. Bring an example if you can; it gives us a useful place to start.
Request a Scoped ProposalBook a free 30-minute call with a RASPSYS consultant.
We will review your current processes and what is worth automating.