JAMS launches incident management for on-call teams

JAMS Software has launched JAMS Incident Management, expanding its automation portfolio into on-call alerting and incident escalation. The new product is designed for IT operations, service desk, engineering, DevOps, and SRE teams that need alerts to reach an available person and continue escalating until someone responds.

The launch is also relevant to service organizations managing after-hours coverage, SLA-sensitive work, and operational incidents, although JAMS positions the product as incident management rather than field service management software.

Key takeaways

JAMS Incident Management receives alerts through email, webhooks, REST APIs, and supported integrations, then distributes notifications through voice, SMS, push, email, Microsoft Teams, and Slack.
Alerts can follow an on-call rotation and escalate until a team member acknowledges the incident.
Two-way integrations are available for Azure Monitor, ServiceNow, Zendesk, and JAMS Scheduler.
JAMS Scheduler users can automatically create an incident when a scheduled job fails and can restart that job from a phone call or text message.
A free plan supports up to five users, while paid plans start at $6 per user per month when billed annually.

From system alert to human response

The central workflow behind JAMS Incident Management is straightforward: an external system identifies a problem, sends an alert into JAMS, and the platform attempts to reach the appropriate on-call person.

Alerts can enter through email, webhook, or REST API. JAMS then sends notifications across multiple channels including voice calls, SMS, push notifications, email, Microsoft Teams, and Slack. If the first person does not acknowledge the incident, the system can continue through the configured escalation path.

This focus on acknowledgement is important for operational environments where generating an alert is only the first step. Teams also need to establish who has taken responsibility for the issue and maintain visibility until it is resolved.

Integrations connect alerts with operational systems

JAMS Incident Management includes two-way integrations with Azure Monitor, ServiceNow, Zendesk, and JAMS Scheduler. According to the company, acknowledgements and resolutions recorded in JAMS can synchronize back to the system that initiated the incident.

Its integration with JAMS Scheduler adds another automation layer. A failed scheduled job can automatically trigger an incident, while the person receiving the notification can restart the affected job from a phone call or text message. JAMS says Incident Management and JAMS Scheduler remain independent products, so organizations do not need one to use the other.

Why this matters for field service

JAMS Incident Management is not being positioned as field service management software. Its primary audiences are IT operations, service desks, engineering teams, DevOps teams, and SRE functions.

However, the workflow has clear parallels with field service operations.

Service organizations frequently need to determine who is responsible when an urgent issue appears outside normal working hours. That may involve an on-call technician, a specialist, a dispatcher, a remote support team, or another escalation level. Simply creating a ticket is not enough if nobody acknowledges it.

The concept becomes particularly relevant in environments where monitoring systems, IT systems, connected equipment, or automated processes can identify failures before a human reports them. In these situations, the operational challenge moves from detecting the issue to routing it to an available person and ensuring ownership is established.

For field service teams, the broader point is that automated escalation can complement scheduling and dispatching when work does not follow a predictable appointment-based model. Emergency maintenance, infrastructure incidents, SLA breaches, and overnight support can all require a different workflow from standard planned service visits.

Pricing and availability

JAMS Incident Management became generally available on September 1, 2026, following an early-access period that began August 1. The APAC announcement confirms availability across Australia and New Zealand, with voice and SMS coverage also available in the United States and United Kingdom. Other regions can request voice and SMS availability, while email, push, Teams, and Slack notifications are available more broadly.

The free plan supports up to five users and includes one alert flow and one on-call schedule.

The Starter plan costs $6 per user per month when billed annually and supports up to 25 users. It includes unlimited alert flows, schedules, and escalation policies.

The Professional plan costs $16 per user per month when billed annually for teams of up to 50 users and adds integrations including Azure Monitor, ServiceNow, and Zendesk. Enterprise pricing is available separately.

JAMS also offers a 14-day trial with all features enabled and no credit card requirement.

FSM News perspective

The launch reflects a broader operational challenge that extends beyond traditional IT incident management: automation is most useful when it connects an event with a clear next action.

In field service, that can mean automatically creating work from equipment data, finding the appropriate technician, escalating an SLA risk, or ensuring an after-hours issue reaches somebody who can act.

JAMS is addressing a narrower part of that process—on-call alerting, acknowledgement, and escalation—but the underlying principle is familiar to service operations teams. Automated workflows need mechanisms for exceptions and human intervention when an issue cannot wait for the next normal scheduling cycle.

For FSM buyers, the distinction remains important. Organizations looking for technician scheduling, mobile field workflows, route optimization, parts management, or dispatching would still require dedicated FSM capabilities. JAMS Incident Management instead addresses the incident-routing layer that can sit alongside other operational systems.

FAQs

What is JAMS Incident Management?

JAMS Incident Management is an on-call alerting and incident management application from JAMS Software. It receives alerts from other systems and distributes them across channels such as voice, SMS, push, email, Microsoft Teams, and Slack while managing acknowledgement and escalation.

Does JAMS Incident Management integrate with ServiceNow?

Yes. JAMS lists ServiceNow among its prebuilt two-way integrations, alongside Azure Monitor, Zendesk, and JAMS Scheduler.

Is JAMS Incident Management field service management software?

No. JAMS positions the product for IT operations, service desk, engineering, DevOps, and SRE teams. However, its on-call scheduling and escalation model can be relevant to service organizations managing urgent or after-hours operational incidents.