IT service management (ITSM) is the way an organization plans, delivers, and supports its IT services. ITSM software helps teams do that work by recording requests and incidents, assigning tasks, and tracking progress. The software supports the process; people still decide how services should work and who is responsible for them.

How an ITSM workflow fits together

Consider an employee who needs access to an internal application. An ITSM platform can record the request, send it for approval, assign a task to the appropriate team, and show when the work is complete. Depending on its configuration, it may also notify the employee when more information is needed.

That workflow has to be maintained as teams change, approval rules evolve, and applications are replaced. Buyers considering Matrix42’s ITSM platform can assess its configuration and maintenance requirements alongside those of other shortlisted tools.

A platform may also support incidents, such as an application outage, and connect staff with knowledge articles. Start by identifying the services and workflows your team needs to manage. Then ask vendors to demonstrate those tasks rather than provide a generic tour of the interface.

Find out who can change a workflow

A vendor may describe a platform as configurable, but that leaves a practical question: configurable by whom?

During a trial, ask a prospective administrator to make a small adjustment. For example, change the team that receives application-access requests when the usual team is unavailable. Watch how the administrator finds the existing rule, changes it, and checks which requests it affects.

The exercise should reveal whether the work uses settings, requires scripting, or depends on a vendor or implementation partner. Ask what permissions are needed and what training is included. A specialist may be the right person for complex changes, but the service team should know which routine adjustments it can make itself.

Check how administrators can inspect the current configuration, too. If the person who created a rule has left, can a colleague find out what it does and which workflows depend on it?

Test changes before they go live

A demonstration should cover more than editing a rule. Ask how the team can check the change before it affects live requests.

In a test environment, submit one request that should follow the new route and another that should stay with the original team. Check the assignment, notifications, and status in each case. Then ask how the approved change moves into the live environment and how an administrator can restore the previous version if something goes wrong.

Find out whether a separate test environment is included in the proposed package and whether it can reflect the relevant live configuration. Seeing the full path from adjustment to verification gives buyers a better picture of the work involved than a configuration screen alone.

Follow the integrations after setup

An access request might rely on a connection to an employee directory or another system. An integration can reduce duplicate entry, but someone needs to know when it stops working.

For each essential connection, establish who builds it, who monitors it, and who investigates failures. Does the platform show a failed transfer clearly? Can the team retry it, or must someone recreate the request? Ask what happens when the connected system changes its interface or authentication requirements.

Request documentation for the proposed connectors and identify any third parties responsible for them. When comparing platforms, account for the time and skills needed to maintain those connections as well as the initial implementation work.

Request deployment and data-handling evidence

For European organizations, platform administration also involves knowing where service data goes and who can access it. Requests may contain employee details, attachments, or information about internal systems.

Ask vendors to document the available deployment options, the locations used for hosting and backups, and where support staff may access data. Request the list of subprocessors and the data-processing terms for the specific service being offered. If AI features are part of the proposal, ask separately where submitted content is processed and retained.

Review those answers against the organization’s requirements. A European hosting location alone does not establish that every aspect of a service meets them. The UK’s national cyber security center offers cloud provider guidance with questions for assessing how a provider protects and operates a service.

Before choosing, record what each vendor demonstrated and what depends on paid support, specialist skills, or further configuration. Ask for estimates covering administrator training, integration upkeep, and future changes, as well as initial setup.

A platform that handles the example workflow is a starting point. The stronger fit is one the organization can maintain and support with the people and resources it expects to have after launch.