Galloping out of myth and straight into instances, the Centaur release is here to help you charge through incidents with ease! Just like the mythical creature known for its strength, speed, and wisdom, this release gives you the power to respond faster, think smarter, and tackle incidents head-on. Let’s saddle up and take a look at what’s new:

• Get a clearer view of how subscriptions work with a dedicated Subscriptions Details page that shows who is subscribed, what triggers the subscription, and how notifications are delivered.
• Bring AI into your workflows with new Google Gemini: Text Generation steps that flows summarize information, translate messages, or generate text using system and user prompts.
• Share information securely with restricted Public Status Pages which allow access only to visitors with approved email domains.
• Create collaboration spaces automatically with new Flow Designer steps for Google Meet and Zoom Chat, including channel creation and automated messages during incidents.

And so much more! Read on to learn more about what we've been working on...

Availability

Before you scroll down to see all the improvements included in this release, here are some important dates:

• Non-production environment access: Tuesday, December 9
• Production environment access: Tuesday, January 13 (enabled between 10:00-10:30am Pacific)

Though we aim to include as many features in each release as we can, it's possible that not everything in the release will be available at the same time. If that's the case for a specific feature, we'll include a note about availability in its write-up below.

Incident response & service intelligence

The xMatters service reliability platform combines incident management capabilities with service intelligence to give teams the situational awareness they need to respond quickly to digital service interruptions, proactively reduce occurrences, and continually deliver value to customers. In this release, we're introducing restricted public status pages and more.

Restricting public status pages by email domain

This feature allows organizations to limit access to a public status page by requiring visitors to verify their email address against one or more approved domains. When domain restriction is enabled, visitors attempting to view the page are prompted to enter their email. xMatters checks the domain, and if it matches a configured domain, the visitor receives a temporary, single-use access link. Only users with an email address belonging to an authorized domain can view the page.

This provides a controlled, easy-to-access mechanism that doesn’t require additional xMatters licenses, while also ensuring visibility is limited to approved audiences. Organizations can securely share incident updates and service status with trusted external audiences such as customers, partners, or vendors, without exposing sensitive information to the public. For example, a SaaS provider supporting several enterprise customers can configure access to allow only email addresses from their customers’ corporate domains. Authorized users can then enter their email and receive a temporary access link to follow updates throughout an incident.

Incident AI Agent updates

We’re continuing to enhance the xMatters Incident AI Agent experience, and this release includes updates that make it faster, easier to use, and more helpful during incident response.

Ask the AI Agent “Who is on call?” for a group or service

The Incident AI Agent can answer questions like “Who’s on call for Payments?” by pulling current shift members from xMatters schedules and returning the engineers on duty. This eliminates schedule hunting, speeds responder identification when teams want to skip shift escalations without notifying all members, and improves accuracy and confidence by avoiding paging the wrong person.

Copy AI Agent response with a click

To save time, avoid manual errors, and enable consistent handoffs, every xMatters Incident AI Agent response now includes a one-click copy button that places clean text or snippets on your clipboard. For example, if the agent suggests a curl command to test a service, the responder can click copy and run it immediately.

Improved AI Agent output quality and performance 

To reduce follow-up questions and improve incident resolution time, we’ve made updates to how our Incident AI Agent handles context so it can provide clearer, more helpful answers with faster responses. When someone asks for an incident summary or resolution steps, the agent returns concise, relevant guidance quickly.

Incident Console: Add Self as Engaged option

Availability: Now in production instances

The Add Self as Engaged feature gives users with incident-editing permissions a simple way to indicate that they are taking an active role in an incident. When someone viewing the Incident Console is not already engaged, a prompt appears in the Resolvers section allowing them to add themselves. Selecting it updates the incident immediately and replaces the older workflow that required opening a separate dialog and searching for their own name.

This becomes especially useful during an active incident when an engineer or other SME sees activity unfolding and realizes they can help. Instead of waiting to be added or navigating extra menus, they can mark themselves as engaged in one step. The update appears instantly to the rest of the team, helping incident managers see who is contributing and making it easier to coordinate next actions.

Automation & integrations

Seamless connections between tools are essential to efficient incident response. By reducing manual effort and streamlining handoffs, these integrations help teams stay aligned, maintain accuracy, and move quickly when it matters most. In this release we're introducing new steps for Google Gemini, Zoom, and Microsoft Teams, adding new options for the Data Sync feature, and more.

Google Gemini: Text Generation steps

Flow Designer now includes two Google Gemini steps (Google Gemini: Text Generation Step and Google Gemini: Text Generation (API key) Step) which use the OpenAI compatible endpoint to generate text for use in flows. Developers can supply system and user prompts along with any optional settings, and the step returns the generated text for use in the flow. This makes it easy to use Gemini in xMatters workflows that already rely on API key based integrations or follow OpenAI request patterns.

Teams can use these steps to transform raw diagnostic output into meaningful, actionable messages before an incident is broadcast. For example, a flow can gather data from multiple tools, send it to Gemini to summarize, and then send the situation brief to responders or collaboration channels. Global organizations can also translate alert messages into a recipient’s local language so communication is clear and easier to act on.

Google Meet: Create Meet Space step 

When every minute counts, reducing manual work during a response process is vital. The Create Meet Space step generates a Google Meet session automatically whenever a workflow requires one. Developers provide the basic meeting parameters, and the step returns the meeting link, join details, and other metadata that the flow can pass directly into notifications, collaboration tools, or ticketing systems. 

In a major incident flow, the step can create a Meet space as soon as an outage is detected. The link is sent to on-call responders, posted in the appropriate channels, and added to the incident record so everyone joins the same space without searching for or sharing a meeting URL. This gives teams an immediate place to coordinate and keeps communication consistent across events.

Zoom Chat: Create Channel step

Availability: Production release

Pausing to create a communication space during an incident can slow teams down, especially when channels need to be created manually or shared across other chats. Automating this step ensures responders always have an efficient, consistent Zoom Chat channel ready as soon as it is needed. The Create Channel step connects Flow Designer to Zoom Chat so a flow can generate a new chat channel automatically. Simply specify the name, owner, and initial members, and the step returns details such as the channel ID and join information for use throughout the workflow. When a service disruption occurs, a flow can create a channel named after the event, add responders, and begin posting summaries and updates immediately.

Zoom Chat: Post Message step

Availability: Production release

The new Post Message step allows Flow Designer to send messages directly into a Zoom Chat channel. Flow developers provide the channel ID and the message content, and the step posts it to Zoom and makes it available as output (such as message ID or timestamp) for use elsewhere in the flow. When combined with the Create Channel step, a workflow can set up a chat space and immediately begin populating it with the information responders need.

For example, during a major incident a flow can create a Zoom Chat channel and then use the Post Message step to deliver a kickoff message that includes the incident summary, severity, responder assignments, and a link to the meeting. As diagnostic checks run, additional messages can share updates or remediation progress so the team stays aligned without switching tools. This helps streamline communication and ensures key details reach the right people at the right time.

Microsoft Teams: Create Online Meeting step enhancements

Availability: Production release

Managing meeting setup manually is time consuming and inconsistent. Organizers can forget to adjust key settings like recording, permissions, or security options, which can create confusion or gaps in compliance. By defining meeting parameters in advance, every meeting created by a flow is configured correctly from the start, removing extra setup steps and reducing human error.

The enhanced Create Online Meeting step gives developers more control over how Microsoft Teams meetings are created and configured. It can set organizers, co-organizers, and presenters; enable or disable recording and transcription; determine attendee permissions; and apply security options such as passcodes or lobby requirements. The step can also associate the meeting with an existing Teams channel so conversation and files stay in one place. This makes it possible for a flow to create a meeting that has already assigned the incident commander, added key responders, enabled transcription, and restricted external access, providing a fully prepared meeting space as soon as an incident begins.

Data Sync: ServiceNow – user device sync 

Keeping user contact information aligned across platforms is error prone and time consuming, and outdated device details create delays and failures when sending alerts. The ServiceNow user device sync eliminates those inconsistencies by making ServiceNow the source of truth and automating device creation and updates directly into xMatters. This feature also keeps device records in xMatters aligned with the information stored in ServiceNow. When a company manages phone numbers, email addresses, or other device details in ServiceNow, the sync updates those details automatically in xMatters. When employees onboard or update their mobile numbers, alerts, escalations, and on-call notifications reach the correct device without any manual updates.

Data Sync: Sync status from list view 

The data sync configuration list now shows the status of each configuration directly in the table, making it easier for admins to understand the health of their syncs without opening individual records. The list displays whether a configuration is running, healthy, or has failed, giving teams a clearer view of their overall sync environment. This is especially helpful when overseeing multiple ServiceNow or directory syncs. An admin can scan the list to confirm that recent jobs completed successfully and quickly notice if one configuration shows a failure state. They can then open only the configuration that needs attention, review the logs, and resolve the issue more efficiently.

Data Sync: Set properties to use default value

Availability: Production release

Data sync configurations can now assign default values to specific xMatters properties. Instead of requiring every field to come from the source system, admins can choose which ones should always use a preset value. During a sync, those defaults are applied automatically, giving teams more control over how user and device records are created. This is useful when a source system does not store a field required by xMatters. For example, if ServiceNow does not include a user’s site, an admin can set a default in the sync configuration. Each time the sync runs, xMatters fills in that value, keeping records complete and consistent without manual updates or changes to the source system.

Data Sync: Sync history 

Availability: Production release

When something changes unexpectedly in xMatters, admins need clear insight into what happened and how. Without a record of past sync runs, troubleshooting can be slow and uncertain. A visible sync history makes it easier to connect user or group updates to the sync activity that caused them.

To assist troubleshooting, support audits, and enhance understanding of how integrations behave, each data sync configuration now includes a history of previous sync runs. Admins can view timestamps, status, and summary results directly within the configuration, removing the need to track sync activity elsewhere or guess when a job last ran. If a user record changes, an admin can check whether a sync occurred just before the update. A successful run confirms the update came from the source system, while a failure indicates an issue with mapping or source data. 

External Locks for group admins, members, and observers

Groups that are synced from an external source can now be locked so that their membership and supervisor settings are read-only in xMatters. Administrators set externallyOwned = true when creating or updating a group through the API and then choose which areas to lock in the interface via Admin > External Data. When viewing a locked group, the UI clearly shows 'Members Locked', 'Admins Locked', or 'Observers Locked', and the 'Add' and 'Delete' buttons are removed.

This feature is especially helpful for organizations syncing groups from systems such as Workday. While Workday remains the source of truth for group admins and members, group observers can still be adjusted in xMatters for messaging or targeting. 

REST API: Update trigger responses

The REST API now returns more accurate responses and detailed error information when triggering a flow. Instead of generic errors, the API surfaces specific reasons such as disabled workflows, disabled triggers, permission issues, flood control, or configuration problems. When available, the response also includes the workflow and trigger identifiers, making it easier to locate the issue inside xMatters.

These enhancements help teams diagnose failures quickly. For example, a developer testing a new integration may receive a '403 Forbidden' message, but instead of a generic error, the response now explains that the workflow is disabled, allowing them to correct the issue immediately. This additional detail allows for faster troubleshooting and ensures integrations run as expected.

Slack: Link channel to an incident for context 

Managing incidents through Slack often requires users to look up or enter incident IDs, adding unnecessary friction to communication when it matters most. Allowing channels to carry their own incident context removes those extra steps and makes actions more intuitive. This update expands the xMatters Slack app with the ability to link or unlink a Slack channel to an incident using simple slash commands. Once linked, the bot recognizes the association and applies commands such as add note or get details without requiring an incident ID. During incidents, we know that many teams use Slack, so supporting natural interactions (like emoji reactions to add notes 😄) helps communication become smoother and more aligned with how people already collaborate, ensuring important details are captured in xMatters without copying or context switching.

Note: The release timing of this feature depends on testing completion and coordinating deployments around existing freezes. If it does not reach production in this cycle, it is expected to follow shortly after.

User experience & messaging

User experience & messaging remain central to xMatters, giving teams the tools they need to stay connected and take action quickly. In this release, we’re introducing a new Subscriptions Details page, improving how callers reach the right responders with enhanced Live Call Routing that now evaluates sub-groups, and making it easier for users to respond to alerts via email.

Subscription details page

The new subscription details page provides a dedicated, read-only view of a subscription so users no longer need to open the edit form to understand how it works. The page displays key information in a clear layout—including who is subscribed, what criteria or conditions will trigger the subscription, and how notifications will be delivered—making it easier for users to understand a subscription while avoiding the chance of accidental changes in the editable view. The page also uses the same permissions model as existing subscription functionality, so users only see subscriptions they have access to.

For example, when an administrator reviews subscriptions created by someone who has changed their role or left the company, they can open the subscription details page and quickly understand how each subscription is configured and decide whether it should remain active.

Live Call Routing: Improved responder identification with sub-group evaluation 

Live Call Routing now evaluates sub-groups when determining who to contact during an incoming call. Instead of only looking at the users and devices assigned directly to the top-level group, the routing logic automatically searches through any sub-groups and includes their members in the call sequence. This improves the reliability of reaching someone who can help and allows teams to keep their existing schedules, rotations, and group hierarchies without needing to adjust them for call routing.

For teams that rely on nested groups to manage their on-call coverage, this update enables the Live Call Routing configuration to follow the full group structure as intended. For example, a team may have a sub-group dedicated to active on-call responders while a separate manager group handles escalation. With sub-group evaluation, Live Call Routing can call the active responders first and move to the manager group only if no one answers, preserving the full hierarchy without requiring admins to flatten or duplicate groups. Users will continue to be contacted one at a time using a depth-first approach, completing its call attempts within a sub-group before continuing through the parent group’s sequence.

Mobile updates

When teams need quick access outside their usual workspace, the xMatters mobile apps keep incident response within reach, wherever they are. In Centaur, we’re helping users on the go better understand their upcoming shifts with access to full escalation details directly in the app.

Shift escalation details 

The mobile apps now provide a full view of escalation details for any on-call shift. Users can open a shift to see the group or rotation it belongs to, the start and end times, escalation wait intervals, rotation rules, and any absences or replacements. This gives on-call responders a clearer picture of how coverage is structured before their shift begins, even when they're on the move.

For example, a developer reviewing a weekend shift can see that they begin as primary on-call, then move to secondary mid-shift, and that another team member is marked absent with no replacement. With this information, they can more effectively prepare for their upcoming workload.

Early Access Program & feature delivery update

The goal of our current delivery model is to balance feature delivery with customer change management processes. This means providing visibility into upcoming changes for customers that want it, while allowing other customers to have a more standard non-production environment that matches production.

If you aren't familiar with the current model, we release features only visible to admins/developers at a faster pace than the quarterly release process. These features should not impact end users until a customer provisions them into their workflow. Customers can opt their non-production environments into the Early Access Program to see features and functionality enhancements that impact end users before they're released on a quarterly basis. All customer non-production environments are updated four weeks prior to an official quarterly production release to allow for testing and training on new features.

We regularly reevaluate and improve our deployment processes to ensure they reflect industry best practices and customer feedback. For more information about our deployment process, see our xMatters Deployment and Early Access article. We'll update that document whenever we make a change, and let you know about the change through other appropriate channels.

Learn more

These are the main features for this release but, as always, there are several other small changes and enhancements we're delivering to keep xMatters forging ahead. As always, detailed information and instructions for using these new features will be available in our online documentation.

We hope you enjoy everything we've packed into the Centaur release, and we're looking forward to seeing you again soon for Dragon...

The information in this article is the intellectual property of xMatters, an Everbridge Company, and is intended only for use with xMatters products by xMatters customers and their employees. Further, this intellectual property is proprietary and must not be reused or resold.