On-Call Alerting Without the Bloat: Introducing JAMS Incident Management

We’re excited to announce the public launch of JAMS Incident Management!

We built this tool for ourselves. As a customer of other incident management products, we felt the pain of a feature-bloated tool with overdone AI hype at a price that wasn’t worth it. What we wanted was simple: a tool that would reliably alert the right human, every time an incident occurs, at a reasonable price. Our pain isn’t unique, and we think a lot of you feel the same way. So we built the solution, and now we’re making it available to everyone.

Sign up here for our free tier, or start a free trial with no credit card required. Paid tiers start at $6/user/month.

So what does JAMS Incident Management do?

JAMS Incident Management ingests alerts and turns them into multi-channel notifications delivered over voice, text, push, email, Microsoft Teams, or Slack. It keeps escalating through your on-call rotation until someone acknowledges the alert, then tracks the incident through resolution.

It can integrate with almost anything.

JAMS Incident Management accepts alerts from any system that can send an email, hit a webhook, or call an API. Most teams connect their monitoring, scheduling, and ITSM tools. Today we have pre-configured integrations with Azure Monitor, ServiceNow, Zendesk, and JAMS Scheduler, with more on the way! For example, JAMS Scheduler users can restart a failed job directly from the phone call or the text message.

It is reliable at its core.

From our experience, incident management products provide the most value by enabling alerting via voice and SMS. Because of that we built JAMS Incident Management to utilize two service providers (Twilio and Azure) to ensure resiliency and reliability. If one has an outage, delivery fails over automatically and your alert still gets through.

Built for people like us (and you)!

We built JAMS Incident Management for people like us. A service desk team using Zendesk that needs an on-call schedule and escalation path for human team members. A batch processing team that needs to know when a critical job fails or when it’s about to miss its SLA. A DevOps or SRE team that needs to know an outage has happened and that someone is already on it.

It works for us, and we hope it works for you. Check it out and let us know what you think: jamsscheduler.com/incident-management