JAMS Software has launched JAMS Incident Management, an on-call alerting and incident-management product for IT operations, service-desk and engineering teams. The service is designed to keep escalating an alert through the assigned rotation until a person acknowledges it.
The product accepts alerts from systems that can send an email, call a webhook or reach an API. It can deliver notifications by voice, SMS, push notification, email, Microsoft Teams and Slack, according to JAMS. Once an alert is acknowledged, the service tracks the incident through resolution.
That workflow is aimed at a routine but consequential operations failure: monitoring may detect a problem, but a notification does little if it reaches an unavailable person or is lost among low-priority messages. Escalation policies are intended to move the alert to the next on-call contact until a human confirms receipt.
JAMS Incident Management can operate independently, but it also connects natively with JAMS Scheduler. The company said a failed scheduled job can automatically open an incident and, for teams using both products, the job can be restarted from a phone call or text message. The release does not say which job types are appropriate for direct restart, so teams will need to decide where that action is safe.
Prebuilt two-way integrations include Azure Monitor, ServiceNow, Zendesk and JAMS Scheduler. The product can also connect to monitoring, orchestration and IT service-management systems through email, webhooks or a REST API. Acknowledgements and resolutions recorded in JAMS can synchronize back to the listed integrations, the company said.
For operations teams, the principal automation outcome is not automatic remediation. It is more reliable routing of an incident from a signal to an accountable responder, with a record of acknowledgements and resolutions. In the scheduler integration, the available restart control can add a remediation step, but it still requires the team to define the job-level safeguards.
The service runs on Microsoft Azure and includes an audit trail covering actions, JAMS said. It supports OIDC single sign-on, with setup guidance for Microsoft Entra ID, Okta, Google Workspace and Auth0. Those controls may matter to organizations that need on-call access to follow an existing identity model.
JAMS said the product is generally available now. Its free plan supports up to five users, while paid plans add broader alert flows, schedules and escalation policies. The launch expands JAMS beyond workload scheduling into the response workflow around failed jobs and other operational alerts.
JAMS said teams can use one alert flow and one on-call schedule on the free plan. That provides a small team a way to test the escalation model before using it for more complex support arrangements. The company did not make claims about a reduction in mean time to acknowledge or resolve, so teams should measure those outcomes in their own environment after setting policy and integrating alert sources.
Operationally, a notification plan also needs maintained schedules, tested contact methods and an escalation path for incidents that cross team boundaries. The product supplies the routing mechanism, but those organizational decisions determine whether a critical alert reaches a responder with the authority and context needed to act.