Overview

Starting with Version 2026.1, AI is now a native, provider-agnostic capability of the ESM Platform. 

Customers can design, configure, and execute AI-powered functions using a low-code approach, embedding AI directly into existing workflows, UI actions, and the M42 Assist experience. AI is therefore available as an integrated platform capability rather than as a separate application or isolated feature.

This approach:

• Enables AI extensibility through low-code configuration. 
• Embeds AI directly into existing business processes and user interfaces. 
• Supports different AI providers through a standardized integration model. 
• Reduces dependency on a single AI vendor. 
• Simplifies the adoption, deployment, and scaling of AI use cases. 
• Preserves the existing Matrix42 security and action model.

A centrally configured AI provider framework currently supports: 

• Matrix42 Intelligence
• OpenAI
• OpenAI-compatible providers 

The provider can be changed without redesigning the AI Function or the business process that uses it. 

AI Function executions are recorded with relevant execution information, such as the selected function, provider, request, response, and execution status. This supports troubleshooting, auditability, and controlled use of AI capabilities.

Requirements

During Preview, customers must have one of the following subscriptions: 

• ITSM 2023 Advanced or Enterprise
• ITSM 2025 Enterprise
• A later supported subscription

When Matrix42 Intelligence (M42Next) is configured as the AI Service Provider, an active Matrix42 Intelligence subscription and sufficient Action Credits are also required. When customers use their own supported AI provider through Bring Your Own Model (BYOM), they are responsible for any consumption, licensing, or infrastructure costs charged by that provider.

Predefined AI Functions

Matrix42 provides a predefined set of AI Functions that can be used immediately after a supported AI Service Provider has been configured.

The predefined functions include: 

Detect Ticket Category 

Analyzes the ticket content and suggests the most appropriate service category. 

The suggestion is based on the available ticket information, including fields such as the title and description. 

Detect Ticket Impact

Analyzes the ticket context and suggests an appropriate impact value. 

The result can be reviewed by the user before it is applied to the ticket. 

Detect Ticket Service

Identifies the service that is most likely related to the reported issue or request. 

This can help reduce manual classification effort and improve routing and reporting quality. 

Detect Ticket Type 

Determines whether the ticket is more likely to represent an Incident, Service Request, or another supported ticket type. 

Detect Ticket Urgency

Analyzes the reported situation and proposes an urgency value. 

The function supports consistent ticket assessment while keeping the user in control of the final value. 

Detect Ticket Solution

Analyzes the ticket and available context to suggest a possible resolution.

Depending on the configured scenario, the result can be shown as information, copied into the ticket, or used by an automation process. 

Detect Ticket Solution by Related Items

Similar to the previous AI feature, “Detect Ticket Solution,” this feature analyzes not only the current ticket and available context but also a list of similar tickets and relevant knowledge base articles, if provided, to suggest a possible solution.

Depending on the configured scenario, the result can be displayed as information, copied into the ticket, or used by an automation process. 

Generate Ticket Summary

Generates concise, AI-driven ticket summaries by analyzing the ticket’s title, description, comments, and related context. It extracts the most relevant details - such as the issue type, existing communications, actions taken, affected services, key symptoms, and current status to provide a clear, standardized overview that improves readability, accelerates triage, and supports faster resolution.

The result is displayed in three sections: Overview provides a concise summary of the ticket. Communication shows incoming and outgoing communications for the ticket. Actions Taken focuses on the actions taken on the ticket.

Generate KB Draft

Generates a draft knowledge base (KB) article from ticket information, such as the title, description, and solution. Only closed tickets can be considered during KB draft generation.

Depending on the configured scenario, the result can be shown as information, copied, used by an automation process, or applied to turn support tickets into structured, reusable documentation for your KB.
If applied, a new knowledge base article will be created, with a link to it included in the description of the action result.

Detect Similar Tickets

Analyzes similar tickets and relevant knowledge base articles using AI’s advanced analysis capabilities. It provides an intelligent way to identify and surface related historical incidents, service requests, and self-service resources by analyzing the ticket subject, recognizing patterns, and matching contextual similarities across existing records.

The result returns the top 3 similar tickets and the top 3 relevant knowledge base articles that match the current ticket. This information can help identify related items or be used by an automation process for further activities.

Text Enhancement

 Improves the quality of user-entered text. 

Typical use cases include: 

• Correcting spelling and grammar.
• Improving readability.
• Rephrasing text in a more professional tone.
• Making descriptions clearer and more concise. 

Auto Translation 

Translates text into a selected target language. This can be used for ticket descriptions, journal entries, knowledge content, and other supported text fields.

Where predefined AI Functions can be used

Predefined AI Functions can be integrated into: 

1. UI Actions
2. M42 Assist
3. Workflow Designer
4. Automated ticket-processing scenarios
5. Custom application actions
6. Partner or customer extensions 

The same AI Function can be reused in several contexts without duplicating the underlying business logic.

Use AI Functions in the User Interface

AI Functions can be exposed as UI Actions for supported business objects. 

For example, an Incident can provide actions such as: 

• Detect Ticket Category
• Detect Ticket Service
• Detect Ticket Impact
• Detect Ticket Urgency
• Find Solution
• Find Related
• Summarize
• Generate KB Draft
• Enhance Description
• Translate Text

AI-powered actions are displayed together with standard actions in the user interface and are visually highlighted to make AI-assisted capabilities easier to identify. They are visually identified as AI actions, but follow the same access, security, and configuration principles as other platform actions.

The existing UI Action model remains unchanged. This means that AI actions support the standard platform mechanisms for:

• Security roles 
• Object permissions 
• Conditions 
• Availability rules 
• Context 
• Localization 
• Action placement 

When a user executes an AI action, the result can be displayed through M42 Assist or directly in the action result. 

Depending on the function, the user may be able to: 

• Review the suggestion. 
• Accept and apply the result. 
• Ignore the result.
• Open a generated object.
• Continue editing the generated content.
• Copy the generated result to the clipboard for reuse in another field, message, document, or application.
• Regenerate the result to request a new AI-generated response based on the same ticket information.

AI-generated suggestions are not automatically applied unless the corresponding action or workflow has explicitly been configured to do so.

Predefined UI AI-powered actions

Matrix42 provides a predefined set of UI AI-powered actions that include:

Detect Category

Detect Category analyzes the selected ticket—primarily its subject and available ticket information—to determine the most suitable category.

After the action is executed, M42 Assist displays:

• The ticket for which the action was run, for example TCK00002 – VPN failed.
• A short explanation of the categorization result, based on the ticket content.
• A Suggested Category field with the recommended category and its confidence level, e.g. Service Desk > Incidents > Security (90%).

The suggested category is shown in a selection field, allowing the end-user to review the recommendation and select a different available category before confirming.

Clicking Apply assigns the currently selected category to the chosen ticket. Clicking Cancel closes the suggestion without changing the ticket category.

Detect Impact

Detect Impact analyzes the selected ticket’s summary and description to recommend an appropriate impact level.

After the action is executed, M42 Assist displays:

• The ticket for which the action was run, for example TCK00002 – VPN failed.
• A brief explanation of the recommendation, considering the scope and potential effect of the issue.
• A Suggested Impact field containing the recommended impact value and confidence level, e.g. Workgroup (80%). 

The suggested impact is shown in a selection field, allowing the end-user to review the AI recommendation and select another available impact level if necessary.

Clicking Apply assigns the currently selected impact to the chosen ticket. No change is made until the end-user confirms it. Clicking Cancel closes the suggestion without updating the ticket.

Detect Type

Detect Type analyzes the selected ticket’s summary, description, and related information to recommend the most suitable ticket type.

After the action is executed, M42 Assist displays:

• The ticket for which the action was run, for example TCK00003 – Multiple Laptops Encrypted by Ransomware!
• A brief explanation of the recommendation, based on the ticket’s content and potential business impact.
• Suggested ticket-type options, such as To Incident or To Service Request.

The end-user can select the appropriate ticket type and review or adjust the related values shown in the selection fields, such as Category, SLA, and Role, before confirming.

Clicking Apply changes the selected ticket to the chosen type and applies the selected related values. No change is made until the end-user confirms it. Clicking Cancel closes the suggestion without updating the ticket.

Detect Urgency

Detect Urgency analyzes the selected ticket’s summary and description to recommend an appropriate urgency level.

After the action is executed, M42 Assist displays:

• The ticket for which the action was run, for example TCK00003 – Multiple Laptops Encrypted by Ransomware!.
• A brief explanation of the recommendation, considering the issue’s severity, scope, and need for a timely response.
• A Suggested Urgency field containing the recommended urgency value and confidence level, e.g. Complete Failure (90%). As you can see from the screenshot, the current Urgency value for the ticket set to “Malfunction” that does not match based on its description, summary suggested by AI recommendation.

The suggested urgency is shown in a selection field, allowing the end-user to review the AI recommendation and select another available urgency level if necessary.

Clicking Apply assigns the currently selected urgency to the chosen ticket. No change is made until the end-user confirms it. Clicking Cancel closes the suggestion without updating the ticket.

Find Solution

Find Solution analyzes the selected ticket’s summary, description, and related context to identify a potential solution. It can be used for incidents, service requests, and other tickets.

After the action is executed, M42 Assist displays:

• The ticket for which the action was run, for example TCK00002 – VPN failed.
• A result header indicating whether a solution was found and the confidence level of the proposed result.
• A brief explanation of the identified issue.
• Recommended resolution steps that the end-user can review before taking further action.

The result header color indicates the confidence level:

• Red: 0% confidence
• Yellow: 1–70% confidence
• Green: 71–100% confidence

The M42 Assist provides actions based on the detected solution. Depending on the result, the end-user can:

• Select Send Solution to Requestor to send the proposed resolution to the ticket requester.
• Select Close Ticket to close the ticket after reviewing the suggested solution.
• Select Cancel to close the result without sending the solution or updating the ticket.

When the end-user selects Close Ticket, the Close ticket wizard opens.

The Solution field is prefilled with the solution proposed by M42 Assist. The end-user can review and modify the suggested text, add a knowledge-base article or attachments if needed, and then select Specify Details to continue with the ticket-closing process.

Selecting Close Ticket does not immediately close the ticket; the ticket is closed only after the end-user completes and confirms the closing wizard.

When the end-user selects Send Solution to Requestor, the Send E-mail for specified ticket wizard opens.

The message field is prefilled with the solution proposed by M42 Assist. The end-user can review and modify the email subject and message, add attachments, and select a signature if required.

The end-user can then select Pause Configuration to continue the email process. Selecting Send Solution to Requestor does not immediately send the email; the solution is sent only after the end-user completes and confirms the email configuration.

Summarize

Summarize analyzes the selected ticket’s title, description, comments, and related context to generate a concise, standardized overview.

After the action is executed, M42 Assist displays:

• The ticket for which the action was run, for example TCK00002 – VPN failed.
• An Overview summarizing the issue, affected service, key symptoms, and current status.
• A Communication section summarizing incoming and outgoing communications for the ticket.
• An Actions Taken section focuses on the actions taken on the ticket.

The summary helps the end-user quickly understand the ticket history and current situation, supporting faster triage and resolution.

Unlike actions that recommend changes to ticket fields, Summarize does not update the ticket or provide actions to apply the result. Selecting Close only closes the summary in the M42 Assist panel; it does not modify the ticket.

Generate KB Draft

Generate KB Draft creates a draft knowledge base (KB) article from information in one or more selected closed tickets. It analyzes ticket titles, descriptions, solutions, and related context to turn resolved issues into structured, reusable documentation.

This action is available only for closed tickets. The end-user can select one or multiple tickets to generate a single KB article draft.

After the action is executed, M42 Assist displays:

• The selected source tickets.
• A suggested title for the KB article.
• A draft introduction describing the issue or topic covered.
• Proposed solution steps based on the selected tickets’ information.

The end-user can review the generated draft before confirming it.

Clicking Apply creates a new KB article in Draft status. M42 Assist then displays a confirmation message with a link to the created KB article and links to the source tickets used to generate it.

Selecting the created KB article link opens a preview of the new article, where the end-user can review, edit, and complete the draft before publishing it. Clicking Cancel closes the generated draft without creating a KB article.

Find Related

Find Related analyzes the selected ticket’s subject and contextual information to identify relevant knowledge base articles and similar historical tickets. It helps the end-user find existing solutions, related incidents, service requests, and self-service resources.

After the action is executed, M42 Assist displays:

• Up to three Knowledge Base Articles that are most relevant to the selected ticket.
• Up to three Similar Tickets with matching symptoms, topics, or contextual patterns.
• Key information for each related item, such as its title, short description, status, and rating where available.

The end-user can select one or more related items. The Generate Solution button becomes available only after at least one item is selected.

Clicking Generate Solution creates a proposed solution based on the selected knowledge base articles and/or similar tickets. The generated result includes recommended resolution steps for the selected ticket.

After a solution is generated, the end-user can:

• Select Send Solution to Requestor to open the Send E-mail wizard with the generated solution prefilled in the message.
• Select Close Ticket to open the ticket-closing wizard with the generated solution prefilled in the Solution field.
• Select Related Items to return to the related-items list, select different items, and generate another solution.
• Select Cancel to close the result without sending a solution or updating the ticket.

Show AI Actions in the Object Context

AI actions can be displayed directly next to the field or control they are intended to support. 

This gives users access to AI assistance at the point where the result is needed, without requiring them to open a separate action menu. 

Out of the box, selected ticket previews include contextual AI actions for:

• Detect Ticket Category
• Detect Ticket Impact 
• Detect Ticket Urgency 

For example, the Detect Category action can be shown next to the Category field.

When selected, the AI analyzes the ticket context and suggests an appropriate value. The suggestion is only applied after user confirmation and can be adjusted before saving. 

Administrators and solution designers can add the same pattern to other forms and controls through the Layout Designer. 

To add a contextual AI action: 

1. Open the required layout in Layout Designer. 
2. Select the control where the AI action should be available. 
3. In the control properties, define the Action to be executed. 
4. Define the Action Context that will be passed to the action. 
5. Save and publish the layout. 

The Action determines which AI or standard UI Action is executed. 

The Action Context defines the object or data context available during execution. In a ticket preview, this is typically the current ticket object. The action can use this context to resolve properties such as the title, description, service, category, impact, or urgency. This mechanism is not limited to predefined AI actions. Any compatible UI Action can be attached to a supported layout control, provided that: 

• The action supports the selected object type.
• The required context is available. 
• The user has permission to execute the action. 
• The action’s availability conditions are fulfilled. 

Contextual actions follow the standard Matrix42 security and UI Action model. They are shown only when the configured conditions and permissions allow execution.

Use AI Functions With Automation

AI Functions can be executed from the Workflow Designer and other supported automation scenarios. 

This allows AI to be used as part of a broader business process rather than only as a manually triggered action. 

Example scenarios include: 

• Classifying a newly created ticket. 
• Detecting the related service. 
• Suggesting impact and urgency. 
• Generating a ticket summary. 
• Translating incoming content. 
• Preparing a response for an agent. 
• Generating a Knowledge Base draft. 
• Evaluating whether a ticket may be resolved automatically. 
• Returning structured values for subsequent workflow decisions. 

A workflow can: 

1. Start from an event, schedule, UI Action, or another supported trigger. 
2. Pass object data to the AI Function. 
3. Receive the output. 
4. Evaluate the returned result. 
5. Update the object or continue with additional actions. 
6. Request human approval before applying a sensitive result. 
7. For productive automation, Matrix42 recommends including validation or human approval where an incorrect AI result could have a material operational impact.

Predefined AI Agents

Matrix42 can also provide predefined AI-driven automation scenarios based on AI Functions. 

Depending on the installed product version, subscription, and activated extensions, these may include scenarios such as: 

Ticket Preparation 

Analyzes incoming tickets and prepares suggested values before an agent starts processing them. 

This may include suggestions for: 

• Ticket type
• Category
• Service
• Impact
• Urgency
• Possible resolution 

Service Detection 

Identifies the most likely affected service based on the ticket description and available service data. 

Auto-Resolution 

Analyzes eligible tickets and attempts to identify a suitable resolution based on the available context and configured knowledge sources. AI Agents are controlled through their respective configuration, workflow, and security settings. Customers should validate the proposed behavior and results before enabling AI-driven processing for productive scenarios.

Read more here (coming soon).

AI Service Providers

An AI Service Provider defines which AI backend is used to execute an AI Function. 

The provider configuration is managed centrally. This allows administrators to configure the connection once and reuse it across multiple AI Functions and business processes. 

Supported provider types include: 

Matrix42 Intelligence 

Matrix42 Intelligence provides the recommended Matrix42-managed AI capabilities and can offer additional services beyond basic prompt execution. The exact available functionality depends on the customer’s subscription and deployed Matrix42 services. 

OpenAI 

The platform includes an out-of-the-box integration for supported OpenAI models. Customers must provide the required credentials and configuration for their OpenAI account. 

OpenAI-compatible 

Providers that expose an OpenAI-compatible interface can also be connected. Compatibility depends on the provider’s API implementation and the supported model capabilities.

Configure an AI Service Provider

Before AI Functions can be executed, at least one AI Service Provider must be configured and activated. 

The exact configuration fields depend on the selected provider. In general, the administrator must provide: 

• Provider type 
• Service Connection
• Model or deployment name 
• Activation status 
• Capabilities
• Priority

To configure a provider: 

1. Go to Administration > Intelligence > AI Service Providers. 
2. Create a new provider or open an existing provider. 
3. Select the provider type. 
4. Select the required service connection. 
5. Configure the model configuration. 
6. Specify a Capability, e.g., AI Functions.
7. Activate the provider.
8. Save the configuration. 
9. Test the connection, where available. 

After the provider has been configured, it can be assigned to one or more AI Function implementations.

Configure the System Prompt

The system prompt defines the general instructions and behavioral rules applied when AI Functions are executed through the configured AI Service Provider. 

It can be used to establish common requirements such as: 

• Expected response style and tone
• Language behavior
• Formatting conventions
• Security and compliance instructions
• Restrictions on unsupported or unsafe responses
• General rules that should apply across multiple AI Functions 

The system prompt is combined with the function-specific prompt at runtime. The system prompt provides the general execution context, while the AI Function prompt defines the concrete task, such as detecting a ticket category, translating text, or suggesting a resolution. 

To configure the system prompt: 

1. Go to Administration.
2. Open System Settings → Intelligence.
3. Enter or update the AI Function System Prompt. 
4. Save the settings.
5. Test the affected AI Functions. 

Administrators should keep the system prompt generic and reusable. Instructions that are specific to one business use case should be defined in the corresponding AI Function implementation instead. 

Changes to the system prompt may affect all AI Functions. The updated prompt should therefore be tested before being introduced into productive use.

Personalization AI Preferences

AI Preferences can affect how M42 Assist generates and presents results. The AI Preferences personalization panel can be accessed either through the User menu

or from the M42 Assist panel.

Depending on the available settings, the end-user can configure:

• Response language — the language used for AI-generated content.
• Writing style — the preferred tone and style, such as casual or formal.
• Technical level — the depth and complexity of explanations for the intended audience.
• AI action preferences — settings that control which records are considered by applicable actions, such as the ticket statuses included when finding related tickets or the knowledge article statuses included in results.

After changing preferences, the end-user can regenerate the result to apply the updated settings.

How AI Functions Work

An AI Function represents a reusable business capability, such as detecting a ticket category or translating text. 

Each AI Function can have one or more implementations. 

At runtime, the platform: 

1. Identifies the AI Function to execute. 
2. Selects the applicable implementation. 
3. Resolves the configured AI Service Provider. 
4. Collects the required input data. 
5. Sends the request to the selected provider. 
6. Receives and processes the response. 
7. Returns the result to the calling UI action, workflow, or automation. 

An AI Function can return: 

• Informational text 
• Formatted HTML 
• A suggested value
• Multiple structured output values
• A reference to a generated object 

Depending on the scenario, the result can be shown to the user for review or processed automatically by a workflow.

Custom AI Functions

Create AI Functions

Users can create new AI Functions or configure existing ones to extend their capabilities. 

These custom functions support two implementation types:

• Prompt-based: this implementation type uses Document/Prompt Designer with data model binding.
  • Prompts can dynamically include data model properties (e.g., ticket data).

Example: Analyze the following ticket and suggest the most appropriate category.
Ticket title: {Title} 
Ticket description: {Description} 
Current service: {Service}

The exact binding syntax is provided by the designer and the selected data context.

• Service-based: this implementation type relies on API or service execution.
  This option is suitable when: 
  • The AI capability is exposed through an existing service.
  • Additional server-side business logic is required.
  •  A custom provider or AI orchestration layer must be called. 
  • The response requires processing before it is returned to the platform. 

The service implementation can return informational or structured output, depending on the function definition.

Configure a Confirmation Wizard for AI Results

An AI Function can use a dedicated Confirmation Wizard to present its result in a structured, guided interface. 

The wizard allows users to: 

• Review the AI-generated proposal. 
• See an explanation or supporting information. 
• Adjust the suggested value where supported. 
• Accept and apply the result. 
• Reject or close the proposal without changing the object. 

This is useful when an AI Function returns an actionable suggestion rather than only informational text. 

For example, the predefined Detect Ticket Category function uses a confirmation wizard to display the suggested category and the AI-generated explanation before the user applies the change. 

How the Confirmation Wizard Works 

The Confirmation Wizard is assigned in the AI Function configuration. 

When the function is executed: 

The AI Function returns its result. 

1. The result is added to the wizard execution context. 
2. The configured wizard opens in M42 Assist. 
3. Controls in the wizard read the AI response from the context. 
4. The user reviews, adjusts, accepts, or rejects the proposal. 

The result is not displayed automatically unless the wizard has been explicitly designed to consume and present the AI Function output. 

Assign a Confirmation Wizard. To assign a wizard to an AI Function: 

1. Go to Administration > Intelligence > AI Functions. 
2. Open the required AI Function. 
3. Select the wizard in the Confirmation Wizard field. 
4. Save the AI Function. 

The selected wizard should be designed specifically for the output returned by that AI Function. 

Create the Wizard Context 

When creating the confirmation wizard, register the AI response as part of the wizard context. 

The wizard context can include values such as: 

• AIResponse 
• Explanation 
• AIFunctionImplementationID
• Additional function-specific values 

The exact context depends on the AI Function and its returned output. 

For example, the predefined category-detection wizard uses: 

• The suggested category returned by the AI Function. 
• The explanation generated by the AI. 
• The current ticket as the action context. 

The wizard controls are then bound to these context values. 

Design the confirmation interface. In Layout Designer, add the controls required to display and confirm the AI result. 

A confirmation wizard typically includes: 

• A text control for the AI-generated explanation. 
• A field or selection control for the proposed value. 
• An option to adjust the suggestion before applying it. 
• Confirm and reject actions. 

For example, the predefined AI Detect Ticket Category wizard displays: 

• The AI explanation. 
• The suggested ticket category. 
• A selectable category field that can be changed by the user before confirmation.

Map the AI response 

The wizard creator must explicitly map the AI Function output to the wizard context and UI controls. 

For example: 

• The returned explanation is mapped to an Explanation context property. 
• The proposed category is mapped to a category selection control.
• The current ticket is mapped through the Object action context. 

The mapping must match the response structure returned by the AI Function implementation. If the expected output is missing or mapped incorrectly, the wizard may open without displaying the generated proposal.

Security and Governance

AI Functions use the existing Matrix42 security and object-access model. 

Access can be controlled through: 

• Roles
• Permissions
• Audience
• UI Action security
• Object-level access

Administrators should ensure that only authorized users can: 

• Configure AI Service Providers. 
• View or change credentials. 
• Create or edit AI Functions. 
• Access execution details. 
• Execute functions against sensitive data. 
• Enable automated AI processing. 

The data sent to an AI provider depends on the configured prompt, input parameters, and object context. 

Administrators must therefore review each implementation to ensure that: 

• Only the required data is sent. 
• Personal or confidential information is handled appropriately. 
• The selected provider meets organizational and regulatory requirements. 
• Data retention and processing conditions are understood. 
• The configuration complies with internal security policies.

Execution Transparency

Each AI Function execution creates an execution record. 

Depending on the provider and implementation, the execution information can include: 

• AI Function
• Implementation
• AI Service Provider
• Execution time
• Execution status
• Input parameters
• Prompt or request
• Response
• Output parameters
• Error information
• Related business object
• Initiating user or process

This information supports: 

• Troubleshooting 
• Prompt optimization
• Auditing 
• Usage analysis
• Provider validation
• Identification of failed executions 

Access to execution details should be restricted because prompts and responses may contain business or personal data

Troubleshooting

AI Function executions can be reviewed from the corresponding AI Function Executions area. 

When an AI Function does not return the expected result, verify the following. 

The AI action is not visible 

Check: 

• Whether the AI Function and UI Action are active. 
• Whether the current object type is supported. 
• Whether the user has the required role and permissions. 
• Whether the UI Action conditions are fulfilled. 
• Whether the required extension is installed. 
• Whether a supported AI Service Provider is configured. 

The action is visible but cannot be executed 

Check: 

• Whether the provider is active.
•  Whether credentials are valid. 
• Whether the configured model or deployment exists.
•  Whether all mandatory inputs are available. 
• Whether the customer has sufficient Action Credits. 
• Whether the provider endpoint is reachable. 

The execution fails 

Open the corresponding AI Function execution and review: 

• Execution status
• Provider response
• Authentication error
• Endpoint error
• Rate limit
• Timeout
• Invalid model configuration
• Invalid prompt
• Missing data binding
• Invalid structured response
• Matrix42 Dispatcher Service not running

For external providers, also review the provider’s own monitoring and consumption portal. 

The result is incomplete or inaccurate 

Review: 

• Prompt wording 
• Data included in the prompt
• Input object quality
• Selected model
• Output format
• Available knowledge or context
• Temperature or provider-specific parameters, where supported 

AI output depends on the supplied context and the selected model. Administrators should test functions with representative customer data before making them broadly available. 

Structured output is not populated 

Check: 

• Whether output parameters are defined in the AI Function. 
• Whether the implementation returns the expected output structure from the Prompt.
• Whether parameter names and types match. 
• Whether the calling UI Action or workflow maps the returned parameters correctly.