Table of Contents
Introduction
Matrix42 Enterprise Service Management provides an integrated platform for designing, delivering, operating, and continuously improving IT and business services.
It combines Self Service, Service Catalog, Service Desk, Service Level Management, Knowledge Management, workflow automation, configuration and asset context, reporting, AI, and low-code extensibility in one environment. These capabilities help organizations establish standardized service management processes while retaining the flexibility to adapt them to their own organizational structures, governance requirements, and business processes.
Matrix42 Enterprise supports established ITIL 4 practices such as Incident Management, Service Request Management, Problem Management, Change Enablement, Service Level Management, Knowledge Management, Service Catalogue Management, and related service management disciplines.
At the same time, the underlying Matrix42 Enterprise Service Management Platform allows the same principles to be applied beyond IT, for example to HR, Finance, Facilities, Procurement, Legal, and other enterprise service functions.
A key characteristic of Matrix42 Enterprise is that the delivered processes are not rigid templates. Processes, user experiences, data structures, workflows, automation, and business logic can be adjusted or extended using the integrated low-code platform. When the recommended customization mechanisms are used, customer-specific adaptations are stored separately from the Matrix42 product definition and merged at runtime. This allows customers to preserve their customizations while continuing to receive product updates and improvements
Service Management Based on ITIL 4 Principles
ITIL 4 approaches Service Management as an interconnected set of practices and value streams rather than a collection of isolated ticket processes.
Matrix42 Enterprise follows the same principle. Information created in one area of Service Management can be reused by other processes and practices.
For example, an employee can report a service interruption through the Self Service Portal. The resulting Incident can be handled in the Service Desk, associated with an affected service or configuration item, controlled by an applicable service level, investigated using existing Knowledge Base articles, and linked to a Problem when a deeper root-cause investigation is required.
If resolving the underlying cause requires a controlled modification of the production environment, a Change can be initiated. A significant disruption can additionally enter the Major Incident process.
This creates a connected service management model:
Users and services → Requests and incidents → Service Desk processes → Assets and configuration context → Knowledge → Automation → Service levels → Reporting and continual improvement
Instead of implementing these activities as disconnected tools, Matrix42 Enterprise provides them as components of one extensible platform.
How Matrix42 Enterprise Supports the Service Lifecycle
Self Service and Service Catalogue Management
The Self Service Portal provides the primary interaction point between service consumers and the organization delivering services.
Services can be centrally defined in the Service Catalog, organized into appropriate categories, made available to defined audiences, and published to users. This enables employees to request hardware, software, access, business services, information, or other standardized offerings without needing to understand the internal organization responsible for fulfilling the request.
A service offering can define the information required from the requester as well as the processes that take place after submission.
Depending on the service, Matrix42 Enterprise can initiate:
- approvals;
- fulfillment activities;
- workflow automation;
- notifications;
- technical provisioning;
- manual tasks;
- integrations with external systems.
Users can follow the progress of their requests through Self Service instead of contacting the Service Desk for status information.
This supports the ITIL 4 practices of Service Catalogue Management and Service Request Management while also providing an important foundation for Enterprise Service Management beyond IT.
Service Request Management
Service Request Management handles predefined and typically repeatable requests such as:
- requesting hardware or software;
- requesting access or permissions;
- ordering a workplace or business service;
- requesting information;
- requesting an employee service;
- initiating onboarding or offboarding activities;
- triggering standardized business processes.
A Service Request commonly starts with an offering in the Service Catalog.
Matrix42 Enterprise can then coordinate the complete fulfillment process, including approvals, tasks, workflow activities, communication, provisioning, and integrations.
This creates an important distinction between standardized service delivery and unplanned service interruptions handled through Incident Management.
Because the Service Catalog, organizational data, workflow capabilities, security model, Service Desk, and integrations are part of the same platform, fulfillment can combine human and automated activities within one process.
Incident Management
The objective of Incident Management is to restore normal service operation as quickly as possible when a service is interrupted or degraded.
Matrix42 Enterprise supports the complete lifecycle of an Incident:
- registration;
- classification and categorization;
- impact and urgency assessment;
- prioritization;
- assignment and ownership;
- communication with the requester;
- investigation;
- escalation;
- resolution;
- closure;
- activity and journal history.
Incidents can originate from end users, Service Desk personnel, integrations, monitoring systems, automation, or other processes.
Agents have access to the operational context required to work on the Incident, including related services, users, configuration information, journal entries, tasks, service levels, and available actions.
Incident Management is closely connected with other ITIL practices:
- Knowledge Management helps identify existing resolutions and workarounds.
- Service Level Management controls reaction and resolution targets.
- Problem Management provides structured root-cause investigation.
- Change Enablement controls changes required to remove underlying causes.
- Configuration and asset information provides service and infrastructure context.
- Major Incident Management provides additional coordination for exceptional high-impact disruptions.
This enables organizations to move beyond simple ticket tracking toward structured service restoration.
Major Incident Management
Major Incidents require additional coordination because of their significant business or service impact.
Matrix42 Enterprise supports a dedicated Major Incident process that complements standard Incident Management.
The process can include:
- identification or proposal of a Major Incident;
- validation and confirmation;
- escalation and de-escalation;
- identification of affected services;
- coordination between responsible teams;
- communication with users and stakeholders;
- tracking of related incidents;
- restoration of the affected service;
- follow-up activities.
The Service Availability Center can provide additional visibility into the status of important services and Major Incidents.
Matrix42 Intelligence can further assist with proactive scenarios, for example by analyzing service-management information and helping identify situations that may require Major Incident handling.
Problem Management
Incident Management primarily focuses on restoring service. Problem Management focuses on understanding and addressing the underlying causes of incidents.
Matrix42 Enterprise enables Problems to be related to:
- Incidents;
- services;
- configuration items;
- known errors;
- workarounds;
- solutions;
- Changes;
- Knowledge Base articles.
Typical Problem Management activities include:
- identifying recurring incidents;
- analyzing patterns;
- investigating root causes;
- documenting known errors;
- defining temporary workarounds;
- identifying permanent solutions;
- initiating Changes where required;
- transforming successful resolutions into reusable knowledge.
This provides a structured transition from reactive incident resolution toward proactive improvement of service stability.
Change Enablement
Organizations need to introduce changes without creating unnecessary risk to productive services.
Matrix42 Enterprise supports structured Change Enablement through workflow-driven Change processes.
Different Change processes can be used depending on the type and risk of the modification, including concepts such as:
- Standard Changes;
- Normal Changes;
- Emergency Changes.
Change workflows can coordinate:
- initiation;
- classification;
- planning;
- risk and impact assessment;
- approvals;
- scheduling;
- implementation;
- tasks;
- testing and validation;
- review;
- closure.
Matrix42 delivers processes that can be used as a starting point, but customers are not limited to those predefined flows.
Change processes can be adapted using Matrix42 Enterprise workflow and low-code capabilities to reflect organization-specific governance, approval structures, responsibilities, automation, or regulatory requirements.
Changes can also be associated with Incidents, Problems, services, configuration items, and other operational data to provide the context required for impact and risk assessment.
Knowledge Management
Knowledge Management is integrated directly into Service Management.
The Matrix42 Knowledge Base can contain:
- troubleshooting information;
- solutions;
- instructions;
- operational procedures;
- manuals;
- frequently asked questions;
- self-service guidance;
- internal support information.
Knowledge articles can be categorized, assigned to appropriate audiences, related to service-management records, maintained through their lifecycle, searched by Service Desk agents, and made available to end users where appropriate.
Knowledge can also be generated from operational experience. For example, a successfully resolved Incident can become the basis of a reusable Knowledge Article.
This creates an improvement cycle:
Issue reported → Incident investigated → Solution identified → Knowledge captured → Knowledge reused → Future resolution becomes faster
Matrix42 Intelligence can additionally assist users and Service Desk agents in discovering relevant existing knowledge or creating new knowledge content.
Service Level Management
Service Level Management establishes measurable expectations for service delivery.
Matrix42 Enterprise supports service-level concepts including:
- Service Level Agreements (SLA) between provider and customer;
- Operational Level Agreements (OLA) between internal delivery organizations;
- Underpinning Contracts (UC) supporting service delivery through external suppliers.
Service levels can define criteria such as:
- applicable services or ticket types;
- priorities;
- service times;
- reaction targets;
- resolution targets;
- escalation conditions.
Service Level Management is connected directly with operational Service Desk processes so that commitments can be monitored against the actual work being performed.
This enables organizations to identify situations in which service commitments are at risk and use the resulting information for operational management and continual improvement.
Service Configuration, Assets, and Dependencies
Effective Service Management requires more than ticket information.
When investigating a service interruption or planning a Change, teams need to understand the associated services, users, devices, assets, and configuration components.
Matrix42 Enterprise brings Service Management together with broader enterprise information and allows service-management objects to be related to relevant configuration and asset information.
This context supports activities such as:
- assessing Incident impact;
- determining affected users;
- understanding service dependencies;
- identifying affected devices or assets;
- investigating Problems;
- evaluating Change risk;
- analyzing Major Incidents;
- understanding service availability.
By connecting service processes with underlying enterprise information, Matrix42 Enterprise enables Service Management to operate as part of the broader IT environment rather than as an isolated ticketing solution.
Workflow Automation
Service processes in Matrix42 Enterprise are not limited to fixed ticket-status transitions.
The underlying Enterprise Service Management Platform provides workflow technologies and low-code capabilities for implementing both simple and sophisticated business processes.
Organizations can build workflows combining activities such as:
- approvals;
- manual tasks;
- notifications;
- data operations;
- conditional business logic;
- API calls and integrations;
- technical automation;
- user interactions;
- AI-powered activities.
Matrix42 Enterprise provides both established service-management processes and the platform capabilities required to adapt them to different organizational requirements.
Adapt Every Process to Your Organization
A central design principle of Matrix42 Enterprise is extensibility without forcing organizations to abandon the standard product.
Low-Code Extensibility
The Enterprise Service Management Platform is a low-code platform. Its SolutionBuilder, Layout Designer, workflow technologies, configuration model, localization framework, extensibility mechanisms, and APIs enable customers to adapt the delivered solution or create additional business applications.
Organizations can therefore adapt areas such as:
- forms and previews;
- landing pages and workspaces;
- data structures and business objects;
- Service Catalog offerings;
- workflows;
- approval processes;
- business rules;
- roles and permissions;
- notifications;
- automations;
- integrations;
- dashboards;
- reports;
- localized terminology;
- complete enterprise applications.
This flexibility is particularly important for ITIL implementations because organizations rarely implement an ITIL practice in exactly the same way.
Matrix42 provides a standard process foundation while allowing the implementation to reflect the customer’s organization, maturity, governance, regulatory environment, and automation strategy.
Update-Safe Customization
Extensibility should not require customers to choose between customization and future product innovation.
Matrix42 Enterprise therefore distinguishes between product-owned definitions and customer customizations.
When a standard product layout is customized using the recommended Matrix42 mechanisms, the customer changes are stored separately from the original product definition. During runtime, Matrix42 combines the updated product definition with the customer’s customization.
This architecture is designed to provide two benefits simultaneously:
Customer-specific changes remain available after an update, while new Matrix42 product improvements can continue to be delivered to the underlying standard component.
For this reason, Matrix42 recommends customizing existing product layouts whenever possible rather than creating independent copies.
A copied layout becomes customer-owned and provides complete freedom, but it no longer automatically receives Matrix42 product changes delivered specifically for the original layout.
This update-safe customization model allows organizations to continuously adapt their Service Management environment without turning every product upgrade into a replacement of their implementation.
Matrix42 Intelligence and AI-powered Service Management
AI is integrated into Matrix42 Enterprise as part of the Service Management and platform experience rather than being limited to a separate chatbot.
Starting with Matrix42 Enterprise 26.1, AI is provided as a native, provider-agnostic platform capability. AI-powered functions can be configured and embedded into workflows, user actions, and conversational experiences using the same platform architecture.
Matrix42 Intelligence can support different stages of service delivery, including scenarios such as:
- understanding and preparing tickets;
- summarizing ticket information;
- improving or translating text;
- identifying relevant knowledge and related tickets;
- supporting resolution;
- drafting Knowledge Articles;
- identifying relevant services;
- supporting automated ticket resolution;
- assisting with Major Incident scenarios;
- enabling conversational interaction with enterprise information;
- using AI within workflows and automation.
Agentic Conversational Assistance
The conversational experience can assist users and agents with contextual questions and, where supported and authorized, work with tools and actions rather than only returning text responses.
Native AI Functions
AI Functions provide reusable AI capabilities directly inside business applications and workflows.
They can be called from user interfaces and automation, enabling AI to become part of normal operational processes.
AI Agents
AI agents can coordinate multiple steps for more sophisticated automation scenarios. They can support predefined service-management scenarios as well as processes designed by customers.
AI Within Low-Code Automation
Because AI is part of the ESM Platform, organizations can integrate AI capabilities into their own processes using low-code configuration rather than limiting AI adoption to predefined Matrix42 use cases.
This combination of AI + workflows + enterprise context + human control allows organizations to introduce AI incrementally while retaining control of their service-management processes.
Multilingual Service Management
Matrix42 Enterprise is designed for international and multilingual organizations.
The platform user interface currently provides supported localization for:
- German;
- English (United Kingdom);
- English (United States);
- Dutch;
- Spanish;
- French;
- Italian;
- Polish;
- Portuguese (Brazil);
- Finnish;
- Swedish;
- Russian;
- Arabic;
- Chinese.
Additional languages including Czech, Danish, and Norwegian are currently available as beta localizations.
Administrators can configure the default user-interface language and supported user languages centrally.
Matrix42 Enterprise also provides user-defined localization, allowing organizations to introduce additional languages or cultures and provide their own translations for user-interface elements. This can also be used when an organization wants to replace standard terminology with organization-specific terminology.
This is particularly useful for multinational organizations that operate one Service Management platform across countries while providing localized experiences for their users.
Matrix42 Intelligence can additionally support multilingual AI scenarios such as translation and localized communication.
Accessible Service Management
Service Management must be usable by all employees.
The Matrix42 Service Management Platform has undergone an independent accessibility evaluation based on the BIT inklusiv BITV software test. The assessment was performed by Aeir on May 28, 2025.
Matrix42 ESM Platform based products are BITV-Test certified, based on Germany’s BITV accessibility requirements and aligned with the European EN 301 549 standard and WCAG 2.1 AA requirements.
Accessibility-related capabilities include considerations such as:
- keyboard operation;
- screen-reader-compatible structure;
- structured headings;
- alternative text;
- sufficient color contrast;
- clear and understandable presentation.
Because Matrix42 Enterprise is highly customizable, customers should also consider accessibility when introducing their own layouts and modifications.
Matrix42 Accessibility Statement and BITV certification information
Designed for European Organizations
Matrix42 is a European software company headquartered in Frankfurt, Germany.
Our software is made and supported in Europe, with a Europe-first approach to development, data protection, regulatory requirements, data sovereignty, and customer support.
This is relevant for organizations that need to consider requirements around:
- GDPR;
- data residency;
- sovereignty;
- information security;
- AI governance;
- European regulatory requirements.
Matrix42 combines this European foundation with international availability, multilingual software, local-language support, and a network of partners across different countries.
Deploy Service Management Your Way
Organizations have different requirements regarding infrastructure, data residency, security, governance, and operational responsibility.
Matrix42 therefore follows its Cloud Your Way approach and supports multiple deployment models.
Matrix42 Cloud
A managed cloud deployment in which Matrix42 operates the software for the customer.
This model provides SaaS-style operation while supporting data residency requirements through Matrix42’s cloud approach and regional infrastructure partners.
Matrix42 Private Cloud
Organizations can choose the data center or cloud environment while Matrix42 or regional Partner manages the Matrix42 solution.
This provides greater infrastructure and data-location control while retaining SaaS-like application management.
Matrix42 On-Premises
Organizations that require full infrastructure control can operate Matrix42 Enterprise in their own environment.
This provides maximum control over infrastructure, operational processes, and data location.
In summary, Matrix42 supports public/managed cloud, private cloud, and on-premises deployment models, allowing customers to select the operating model that best meets their security, regulatory, sovereignty, and operational requirements.
Roles, Responsibilities, and Controlled Access
Service Management involves multiple responsibilities rather than one universal Service Desk role.
Matrix42 Enterprise supports role-based access and organizational responsibilities across areas such as:
- Incident Management;
- Service Request Management;
- Problem Management;
- Change Management;
- Knowledge Management;
- Service Level Management;
- Service Desk Management;
- administration.
Users can receive multiple roles where their responsibilities span several practices.
The Matrix42 security model determines which applications, data, records, and actions users can access and allows customer-specific responsibilities and governance structures to be implemented.
The same underlying security principles are also used by workflow automation and native AI capabilities, helping ensure that additional automation does not require a separate authorization model.
Reporting, Measurement, and Continual Improvement
Service Management generates information that can be used to measure service quality and improve operations.
Matrix42 Enterprise provides reporting, dashboards, and analytics capabilities that allow organizations to analyze operational data such as:
- ticket volumes;
- processing times;
- SLA performance;
- workloads;
- recurring issues;
- service performance;
- trends;
- process effectiveness.
Because reporting uses information from the same platform as the operational processes, organizations can move from operational activity to measurement without maintaining an independent service-management dataset.
This supports continual improvement by helping identify areas such as repeated incidents, overloaded teams, service-level risks, process bottlenecks, or opportunities for additional automation.
From IT Service Management to Enterprise Service Management
Many ITIL principles are equally valuable outside IT.
Defined services, transparent ownership, standardized requests, approvals, workflow automation, knowledge, service levels, measurement, and continual improvement can also be applied to enterprise functions such as:
- Human Resources;
- Finance;
- Facilities;
- Procurement;
- Legal and Compliance;
- Workplace Services;
- other shared-service organizations.
The Matrix42 Enterprise Service Management Platform provides the common low-code foundation required to extend service-management concepts to these departments.
For example, the same service value flow used to request software can also be applied to an HR request:
Service Catalog → Request → Approval → Workflow → Tasks → Fulfillment → Communication → Measurement
Organizations can therefore implement shared service-management principles while retaining department-specific processes, applications, data, responsibilities, and terminology.
ITIL 4 certification
Matrix42 Enterprise Service Management is independently recognized for its alignment with ITIL 4 through two established certification and accreditation schemes.
PinkVERIFY® ITIL 4 Certification
Matrix42 Enterprise has been assessed by an accredited Pink Elephant consultant and is PinkVERIFY certified across 11 ITIL 4 practices. Matrix42’s current product information specifically references Matrix42 Enterprise 25.4 as PinkVERIFY-certified.
PeopleCert Tool Vendor Accreditation
Matrix42 Enterprise Service Management is also listed in the official PeopleCert Tool Vendor Accreditation directory as an ITIL 4-compliant Service Management tool. PeopleCert independently lists Matrix42 Enterprise Service Management and its certified practices.
The 11 validated ITIL 4 practices are:
- Change Enablement
- Deployment Management
- IT Asset Management
- Incident Management
- Knowledge Management
- Monitoring & Event Management
- Problem Management
- Release Management
- Service Catalogue Management
- Service Configuration Management
- Service Request Management
These certifications provide independent validation that Matrix42 Enterprise supports established ITIL 4 practices and can be used as the foundation for standardized service-management processes.
Matrix42 Enterprise also provides capabilities supporting additional ITIL-aligned disciplines and service-management scenarios beyond the practices formally covered by these certifications.
How the Practices Work Together
The value of an integrated Service Management platform becomes especially visible when several practices participate in the same service value stream.
Consider the following example:
- An employee experiences an interruption and reports it through the Self Service Portal.
- An Incident is created and the appropriate service level is determined.
- Service and configuration information gives the Service Desk context about the affected service.
- Matrix42 Intelligence can help prepare or summarize the case and identify relevant information.
- The agent searches or receives relevant Knowledge and previous resolution information.
- If the interruption has significant organizational impact, the Incident can enter Major Incident Management.
- If similar Incidents repeatedly occur, a Problem can be created for root-cause investigation.
- A permanent solution may require a Change.
- The Change process coordinates assessment, approval, implementation, and validation.
- The successful resolution can become a new Knowledge Article.
- Reporting and service-level data help determine whether additional improvement is required.
- If the standard process does not fully meet organizational requirements, the workflow can be adapted using the Matrix42 low-code platform.
The result is not simply a sequence of ticket types. It is an interconnected service value stream using shared information, automation, knowledge, and responsibilities.
Core Components of Matrix42 Enterprise Service Management
| Component | Purpose |
|---|---|
| Self Service Portal | Gives employees one place to find information, request services, report issues, and follow their requests. |
| Service Catalog | Defines services and offerings, target audiences, request information, approvals, and fulfillment. |
| Service Desk | Provides the operational environment for Incidents, Service Requests, Problems, Changes, Knowledge, Major Incidents, and related work. |
| Service Level Management | Defines and monitors SLA, OLA, and Underpinning Contract commitments. |
| Knowledge Base | Captures reusable knowledge for Service Desk personnel and end users. |
| Service and configuration context | Connects operational processes with relevant services, assets, users, and configuration information. |
| Matrix42 Intelligence | Adds conversational AI, Native AI Functions, AI Agents, and AI-supported automation. |
| Workflow Designer / Workflow Studio | Automates service-management and enterprise processes. |
| SolutionBuilder | Provides low-code capabilities for adapting existing applications and creating new ones. |
| Reporting and Analytics | Provides operational visibility, performance measurement, and improvement insights. |
| Enterprise Service Management Platform | Provides the common data, security, UI, low-code, workflow, integration, localization, and extensibility foundation. |
The Service Management documentation provides detailed guidance for configuring and operating the Service Management applications, while the Enterprise Service Management Platform documentation covers the underlying platform capabilities used for configuration, automation, extension, and application development.
One Platform — Standardized Where Useful, Adaptable Where Necessary
Matrix42 Enterprise combines two principles that are particularly important for long-term Service Management implementations.
First, organizations receive predefined Service Management capabilities and processes based on established service-management practices rather than having to build an ITSM solution from scratch.
Second, these processes are built on the Matrix42 Enterprise low-code platform and can be extended or adjusted to customer requirements.
This means organizations can start from a maintained Matrix42 standard and then evolve the implementation as their organization, maturity, regulations, automation requirements, or business processes change.
Using the recommended Matrix42 customization model also means customers do not need to freeze the product version in order to protect their adaptations: customer customizations can be preserved while Matrix42 continues to deliver product updates to the underlying standard components.
This combination of ITIL-aligned standard processes, low-code extensibility, update-safe customization, integrated AI, multilingual support, accessibility, and flexible deployment provides the foundation for using Matrix42 Enterprise both as an IT Service Management solution and as a broader Enterprise Service Management platform.