We're now hard at work on our next quarterly release, Bigfoot, which will be rolling out in the September/October 2025 time frame.
Please follow this article and its comments to receive updates throughout the quarter about new features and functionality that we're working on for the Bigfoot release. We'll also use this document to capture highlights of additions and updates to our mobile platforms and the xMatters REST API.
For a list of changes made in each deployment that aren't covered in the Development Highlights, see the support notes included below each highlight. While most features will be added to production environments as part of our quarterly releases, the support notes typically describe fixes, which can sometimes affect product behavior.
Release schedule
Here are the dates we're expecting the release to be available:
- Non-production environment access: Tuesday, September 23, 2025
- Production environment access: Tuesday, October 21, 2025
Customers interested in previewing new features before they're released can opt into our Early Access Program (EAP), which delivers new features into non-production environments as they're rolled off the assembly line.
October 20 - 24, 2025
Bigfoot has appeared!
The Bigfoot release is now available in production environments. To read more about everything that's new, our Release Overview has all the details, including specific availability timing for features where applicable.
Feature Spotlight on incident playbooks
Incident management often involves coordinating multiple teams, tracking tasks, and following detailed procedures. The Playbooks feature in xMatters helps teams codify these processes so resolvers can focus on resolving issues instead of managing steps manually. When an incident is initiated, xMatters compares the incident’s severity and impacted services with your configured playbooks. If there’s a match, the appropriate task lists are automatically added to the Incident Console so teams immediately know what actions to take.
For example, a 'Major Incident' playbook could outline steps for updating stakeholders and coordinating communications. Additionally, a service-specific playbook might provide direct links to monitoring tools or rollback procedures. Creating playbooks in xMatters ensures every resolver has the information they need—exactly when they need it—to respond quickly and consistently.
Support notes (week of October 20 - 25)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-134729 |
Flow Designer - Create Alert step (usability fix): Fixed an issue to ensure a consistent look and feel on the Devices page when devices are selected and deselected. |
October 13 - 17, 2025
Feature Spotlight on Group Calendars
As a group supervisor, you have the ability to customize and refine an on-call shift's details to make it easier to build and manage your team’s xMatters shift schedule and match it to your organization’s schedule.
We built the calendar so it’s easy to customize – simply click any empty space on the day or week view to create a new shift occurrence at the selected time. You can also click on an existing shift to update its details. When you create or modify a shift, you can configure the shift's type, name, description, start and end time, frequency (to create a series), and shift members from a side panel so you can view your full schedule alongside it.
Support notes (week of October 13 - 17)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-134453 |
Users - Schedule (usability fix): Fixed a navigation issue some users could encounter when creating a new temporary absence. |
| COR-125669 |
Document Library (usability fix): Removed an incorrect and extraneous error message that could appear when documents were successfully deleted from the Document Library. |
October 6 - 10, 2025
Feature Spotlight on the Incident Resolution workflow
When notifying teams about an incident, it’s vital to include the relevant information they need in the initial message so they can jump on resolving the issue quickly. Our customizable Incident Resolution workflow includes steps such as the Create Alert step, Notify to Engage trigger, and Get Incident Collaboration Channels step to help automate the process of including current incident details in resolver notifications.
When you open the workflows in Flow Designer, the Notify to Engage trigger and Create Alert step are connected so you can customize the message sent to resolvers right on the canvas. You can also use the connected Get Incident Collaboration Channels step in your flow to include links to collaboration channels in the message sent to resolvers.
Support notes (week of October 6 - 10)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-134433 (SUP-31131) |
Users - User profile: Ensured that specific fields on the Edit Profile window for externally owned users cannot be edited. |
| COR-134684 |
Playbooks (usability fix): Adjusted the positioning and layout of some page elements on the Playbooks pages. |
| COR-134157 (SUP-31096) |
Groups - Shift Occurrences: Corrected an issue that caused some users to see an empty shift instead of the appropriate shift occurrence. |
| COR-133890 (SUP-31103) |
Groups - Add/Edit Shift Series: Fixed an error that could occur when adding or editing some shift series. |
September 29 - October 3, 2025
New features available in non-production
A few more features from our Bigfoot release are now available in non-production instances:
- The Incident AI Agent is live in EMEA/APAC Advanced plan NP environments, giving resolvers an AI-powered assistant directly in the Incident Console.
- The new ServiceNow Pull Data Sync lets administrators import user and role data directly from the ServiceNow API with greater flexibility and control.
- Flow Designer now includes the Jira Modify Issue in Project step, which allows you to update issues in a project using dynamically configured inputs.
Feature Spotlight on automatic incident updates to chat channels
Effective communication is essential to successful incident management, and chat channels in apps such as Microsoft Teams and Slack are powerful tools for keeping people connected. During the incident resolution process, you can configure xMatters to automatically send updates to a channel whenever there’s a change in status or priority, or when someone updates the incident’s description or impacted services.
Automating these notifications ensures members are updated simultaneously and remain on the same page as the incident progresses. By removing the need for manual updates, teams can keep communication consistent and focus their attention on resolving the incident.
Support notes (week of Sept 29 - October 3)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-132771 | Messaging - Recipients (usability fix): Ensured a consistent look and feel for messaging when users without valid permissions click the Expand Group link in the recipients section of the form. |
| COR-133626 | Flow Designer - Post Incident Report: Fixed an issue that would occasionally prevent the creation of a Post Incident Report when an incident's status is set to Resolved. |
September 22 - 26, 2025
Bigfoot release overview
On Tuesday, September 23, the latest features from our Bigfoot release appeared in non-production instances! These updates include our new Incident AI Agent, public status pages, calendar views for the user schedule on our mobile apps, an updated Live Call Routing report—and lots more. If you're wondering what else is new, our Bigfoot Release Overview is your complete guide to everything that's included.
Feature Spotlight on incident resolvers
When your team is in the middle of mitigating an incident, the Resolvers section of the Incident Console lists the groups and individuals you can notify when there are updates to the incident. Incident resolvers are people in your organization engaged in the incident resolution process, and the Incident Commander is the resolver in charge of the incident. As the incident progresses, you can renotify resolvers, dismiss people whose expertise is no longer needed, and engage new resolvers. If you need to replace the current commander, you can reassign the role to any engaged resolver.
Support notes (week of Sept 22 - 26)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-132585 (SUP-30971) |
Flow Designer - Incident Automation step: Fixed an issue with the Incident Automation step that prevented the Incident Console from displaying updated incident properties. |
| COR-132379 |
Flow Designer: Corrected an issue that prevented some users from successfully saving flows after adding an HTTP webhook trigger to the canvas. |
September 15 - 19, 2025
ServiceNow integration certification for Zurich release
The xMatters ServiceNow integration app (version 5.8.3) is now certified for compatibility with the Zurich release. As there are no functionality changes, it will continue working seamlessly with current workflows.
Feature Spotlight on impacted services
It’s critical to understand which applications and technical services are affected by an active incident. In xMatters, you can easily review important impacted service information such as the service owner, whether the service is being impacted by other active incidents, and any changes made to the service within the last 24 hours. From the Incident Console you can quickly notify the service owner to engage them as an incident resolver, run an automation related to the service, or view the incident’s dependencies map to identify potential root causes.
Support notes (week of Sept 15 - 19)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-132902 | Groups - Who's On Call: Corrected an issue in the date pickers that prevented users from selecting an end date, even when the date range was within a valid range. |
| COR-132588 (SUP-30968) |
Alert Inbox: Fixed an issue that could cause users to see an error when trying to view alerts in the Inbox. |
| COR-130749 (SUP-30749) |
Alerts Report - Log tab: Corrected an issue that caused users with the appropriate roles and permissions to see an error after selecting the Log tab. |
| COR-132932 (SUP-30997) |
Live Call Routing - Agent Not Available: Fixed an issue that prevented users from receiving an alert when the caller leaves a voicemail. |
| COR-132006 (SUP-30895) |
xMatters REST API - get shift occurrences: Corrected an issue that caused requests to return a 404 error when querying shift information. |
| COR-132032 (SUP-30898) |
Groups - Shifts: Ensured that the group calendar accurately showed all shift information in week and month view. |
September 8 - 12, 2025
Simplified Activity Report for Flow Designer
Integration logs can quickly become difficult to read when they include large HTTP payloads, making it harder to spot the details you need. Flow Designer logging now offers two formats: 'Simple' & 'Verbose'. The simple log captures only key information like status codes and endpoint URLs, while verbose logs still provide full details. Both formats are generated for each flow and can be viewed or exported independently, so you can choose the level of detail that best fits your troubleshooting or reporting needs.
xMatters Terraform Provider v0.2.0
Managing user devices manually can be time-consuming and inconsistent across environments. With v0.2.0 of the xMatters Terraform Provider, you can now define and manage device properties. The update supports all importable devices (except mobile app, Slack, and MS Teams) and allows you to set initial device order using the Terraform depends_on property without overwriting user changes.
To help avoid issues when Terraform-managed devices are deleted, externally_owned defaults to true, but you can override it in your configuration. This release makes it easier to automate and standardize device management as part of your infrastructure-as-code workflows.
REST API Updates
-
Get groups: When you’re searching for groups, sometimes you want to narrow the timeframe to when the group was created. But what if you don’t have an exact time? Using the new search parameters of
createdAfter,createdBefore,createdFrom, andcreatedTo, you can bring back only the groups created in the timeframes you specify. -
Get a person (by ID): When users are imported into xMatters from an external system, they will have an internal xMatters user ID assigned to them. But their identifier from the other system is also imported and set as the
externalKeyfield. We’ve expanded the GET /people/<personID> endpoint to include external identifiers. You can now search for individual users using their UUID, target name, or the value of theexternalKeyfield.
Feature Spotlight on the Inbox
Keeping track of incident notifications can be overwhelming if you don’t have a central place to manage them. The xMatters Inbox acts as your hub for everything related to incident notifications, making it easier to access and organize alerts, along with options to expand details, view attachments, and respond directly from the Inbox. You can also use the sort options to focus on the most recent or most active alerts, helping you prioritize what matters most to you.
Support notes (week of Sept 8 - 12)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-132368 |
Messaging - Attachments (usability fix): Improved the layout and positioning of some page elements when working with attachments. |
| COR-131264 | Subscription Form: Fixed an issue that caused some subscriptions to not work properly when the subscribers included both groups and services. |
September 1 - 5, 2025
Editing incident details
To make it easier to quickly target and update individual incident details such as the description and properties, from the Incident Console you can now hover over the detail you want to update and click Edit.
Feature Spotlight on the on-call group interface
Managing on-call groups is easier when you have everything you need in one place. The xMatters on-call group interface gives you a clear, organized view of a specific group so you can quickly see details about the people involved, how shifts are structured, and which services the group is responsible for.
The Overview tab provides a snapshot of your on-call group. You can see details about the group admins, observers, and members, including which members are currently on call, and whether any temporary replacements are scheduled. It also highlights any services the group owns and any active incidents impacting those services.
From here, you can use the Schedule tab to view or edit group shifts in a day, week, month, or list view. The People tab gives you a detailed look at the group’s members, admins, and observers, including their contact devices and availability.
Support notes (week of Sept 1 - 5)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-130294 (SUP-30720) |
Groups - on-call escalations: Fixed an issue where inactive groups were not being properly indicated in the Members list for a shift. |
| COR-130292 (SUP-30720) |
User Schedule - rotations: Fixed an issue where some shift rotations were not being properly displayed on the User Schedule page. |
| COR-130261 (SUP-30604) |
Groups - inactive shifts: Fixed an issue where some inactive shifts were being incorrectly targeted for notification. |
| COR-130294 (SUP-30720) |
Flow Designer: Ensured connectors were properly applied when a flow step is dropped between two existing steps. |
August 25 - 29, 2025
Feature Spotlight on status pages
It’s crucial that stakeholders are provided with accurate and up to date status information when an incident is occurring. But if incident commanders or resolvers are spending time sending manual updates, then their focus is distracted from identifying, mitigating, and resolving the incident itself. To help keep everyone updated about service status, disruptions, or recent activity, you can create Status Pages where teams can view information about their organization’s services from a centralized location. For example, you can create a status page just covering your internal systems or one for services that your customer facing teams need to monitor.
Support notes (week of Aug 25 - 29)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-130294 (SUP-30720) |
Groups - on-call escalations: Fixed an issue where inactive groups were not being properly indicated in the Members list for a shift. |
| COR-130292 (SUP-30720) |
User Schedule - rotations: Fixed an issue where some shift rotations were not being properly displayed on the User Schedule page. |
| COR-130261 (SUP-30604) |
Groups - inactive shifts: Fixed an issue where some inactive shifts were being incorrectly targeted for notification. |
| COR-130294 (SUP-30720) |
User Schedule - shift duration: Fixed an issue where some 24-hour shifts were displayed as lasting 48 hours on the user's schedule. |
August 18 - 22, 2025
Feature Spotlight on off-duty members (on-call scheduling)
Sometimes you don’t want everyone in an escalation timeline to be notified every time there’s an incident. To give resolvers a break, you can add off-duty members to your on-call schedule rotations. Once configured, off-duty members automatically rotate when on-call and vice versa following your shift rotation rules. This gives greater control over your scheduling process and eliminates the need to use the '9999’ workaround.
Support notes (week of Aug 18 - 22)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-130294 (SUP-30720) |
User Schedule: Fixed an issue that caused users to view incorrect shift durations. |
August 11 - 15, 2025
Feature Spotlight on owned services
Assigning a group's owned services lets you identify which team in your organization is responsible for specific services and who to contact if there's an issue. The group who owns the service is responsible for it—they're the point of contact for a resolver if the service is impacted by an incident. If the service owner is an on-call group, you can easily find out who's currently on-call for the group by viewing the service on the catalog and clicking the owner’s name.
Support notes (week of Aug 11 - 15)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-129516 (SUP-30630) |
Users - Devices: Fixed an issue that prevented properly configured iOS apps from appearing in the list of user devices. |
| COR-128496 (SUP-30523) |
Admin - User Upload: Corrected an issue that was preventing User Upload from importing users with multiple roles. |
COR-129324 |
xMatters REST API - GET /people: Fixed an issue that caused some users to experience timeout errors for their requests. |
| COR-124545 (SUP-30684) |
Admin - Live Call Routing: Corrected an issue that caused users to hear default messages when customized messages were available. |
August 4 - 8, 2025
ServiceNow Next Generation Integration
ServiceNow (Flow Designer) v2 has received certification and is now available! This powerful integration includes the new 'Everbridge Flow Designer' ServiceNow app, Incident Alerts and Actions features, a starter workflow for Flow Designer, and two new triggers to streamline custom workflows and improve automation directly within ServiceNow.
Feature Spotlight on shared user schedules
Share your xMatters on-call schedule to an external system by downloading an ICS file or creating a URL link for your user calendar. You can customize your shared calendar to include primary, primary and secondary, or all on-call shifts. Once you download the ICS file for your calendar, it can then be imported into your preferred calendar application or chat app.
Support notes (week of Aug 5 - 8)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-128871 | Incidents - Tasks: Fixed an issue that hid the task start time when "Relative" was selected from the list of due date options. |
| COR-128981 | Incidents - collaboration channels - Slack: Fixed an issue that caused stakeholder updates to trigger notifications in Slack collaboration channels. |
July 28 - August 1, 2025
Find users without Teams or Slack devices
To make it easier to find users in xMatters without a Microsoft Teams or Slack device, we've updated the Devices filter on the Users page to include 'Without Microsoft Teams Devices' and 'Without Slack Devices' options.
Add a note to an incident from Slack
If your teams use the xMatters Slack integration during your incident response process, you can now use the 'Add an Incident Note' slash command to add a note to an incident in xMatters.
The command options are /xmatters note [incident ID] [Your note]. For example:
- /xmatters note
- /xmatters note INC-258
- /xmatters note INC-258 I can add notes from Slack!
Want to add an existing message as a note? Click the message's context menu and select Add as Incident Note to append it instantly.
Updated 'Group Roster' API endpoint to 'Group Members'
To reflect changes to the user interface, we've updated the name of the 'Group Roster' API endpoint in the xMatters REST API reference to 'Group Members'. There are no changes to the parameters or to the endpoint itself—we're just bringing it inline with the newest terminology.
Feature Spotlight on group performance dashboard widget
The Group Performance widget lets you track alerts targeting a group, along with the average time it takes for the group to first respond to them. You can also track incidents in which a group is an engage resolver.
You can add multiple Group Performance widgets to your dashboard to get a clear picture of how different groups are performing. On a single screen, you’ll be able to identify groups that may be receiving too many alerts, or pinpoint groups or users who may be taking longer than expected to respond to an alert.
If you need more information on a data point, you can also access the full Group Performance Report from the widget with all the filters pre-applied so you can see what you need right away.
Support notes (week of Jul 28 - Aug 1)
| xMatters Internal Reference No. | Summary |
|---|---|
| COR-128870 | Live Call Routing - configuration: Fixed an issue that prevented users from successfully saving custom messages. |
| COR-122961 | Dashboard - Recent Alerts widget (usability fix): Corrected an issue to ensure users experience a consistent look and feel when viewing notifications from either the dashboard widget or the Alerts report. |
| COR-128945 |
Incidents - Task Lists (usability fix): Adjusted the behavior and layout of some elements to improve user experience. |
About the early access delivery process
Customers can choose to opt their non-production environments into an Early Access Program (EAP) to see new functionality before it's released. If you're considering signing up for the early access program, there are a couple of important things to know:
- Enrollment in EAP can be turned on any time through a support request.
- Exiting EAP can only be done on quarterly boundaries (you cannot opt in and out between quarterly releases).
For full details, refer to the official xMatters Deployment Process & Early Access article.
Comments
12 commentsArticle is closed for comments.
Highlights and support notes added for week of August 4 - 8, 2025.
Updates include:
Highlights and support notes added for week of August 11 - 15, 2025.
Updates include:
Highlights and support notes added for week of August 18 - 22, 2025.
Updates include:
Highlights and support notes added for week of August 25 - 29, 2025.
Updates include:
Highlights and support notes added for week of September 1 - 5, 2025.
Updates include:
Highlights and support notes added for week of September 8 - 12, 2025.
Updates include:
Highlights and support notes added for week of September 15 - 19, 2025.
Updates include:
Highlights and support notes added for week of September 22 - 26, 2025.
Updates include:
Highlights and support notes added for week of September 29 - October 3, 2025.
Updates include:
Highlights and support notes added for week of October 6 - 10, 2025.
Updates include:
Highlights and support notes added for week of October 13 - 17, 2025.
Updates include:
Highlights and support notes added for week of October 20 - 24, 2025.
Updates include: