JAMS Incident Management for MSPs and MSSPs
On-call for every client, from one partner account
Each client gets its own tenant, with its own schedules, escalation policies, integrations, and alert history. You run them all from the Partner Console. Clients never see each other.
We’ll set up your partner account and talk through how you run on-call for your clients.
Our product team helps the first partners get set up.
Client data is separated in the database layer
Import schedules with a read-only check first. Nobody gets paged during import
Each client is a separate tenant
When a client’s backup fails at 3 a.m., the page should go to the tech who covers that client, through that client’s escalation policy. Not to whoever is on call for everyone.
From the Partner Console you can:
Create a client tenant
Set notification limits per client and across your account
Suspend a client
Export usage
Switch into any client’s workspace to manage it
A noisy integration at one client can burn through voice and SMS in an hour. A per-client limit keeps one client from running up the bill for the rest.
Alerts come in from the tools you already run
ServiceNow, Zendesk, and Azure Monitor connect natively, and Azure Monitor is two-way. PSA, RMM, and SIEM tools that can send email or a webhook raise alerts too. If you need a native integration, tell us. We add them as partners need them.
Once an alert fires, JAMS Incident Management keeps calling, texting, and pushing until someone acknowledges, then escalates.
Built for a 24x7 SOC
Each client’s analysts, schedules, and escalation paths stay in that client’s tenant, so the analyst covering one client never gets paged for another.
Security tools connect like this today:
Microsoft Sentinel: a Logic App playbook with an HTTP step, or by email. It takes some setup.
Splunk: by email, or through a custom alert action. Splunk’s built-in webhook can’t post to us directly.
Anything that sends email or a custom HTTP request works the same way.
Bring your schedules with you
Import people, teams, schedules, rotations, escalation policies, and overrides. A read-only check shows what will be created first, and the import doesn’t call, text, or email anyone.
Run client batch jobs too?
Many MSPs also run scheduled jobs for clients: backups, file transfers, ETL, month-end close. JAMS Scheduler runs them across Windows, Linux, and z/OS and sends failures straight to the on-call tech in JAMS Incident Management.
Run on-call for your clients? Let’s talk.
We work with MSPs and MSSPs as partners. Tell us how you deliver on-call today, and we’ll set up a partner account and work through how you run it for your clients.
Common questions from MSPs and MSSPs
Can one MSP run on-call for many clients?
Yes. A partner account holds a separate tenant for each client, with its own schedules, escalation policies, integrations, and alert history. You switch between tenants from the Partner Console.
Can clients see each other’s data?
No. Client data is separated in the database layer, and automated tests cover that separation. Each client only sees its own tenant.
Can I cap notifications for one client?
Yes. Set notification limits per client and across your whole account.
Will it take alerts from my PSA, RMM, or SIEM?
Yes, if the tool can send email or a webhook. ServiceNow, Zendesk, and Azure Monitor connect natively. Microsoft Sentinel and Splunk connect by email or with a short setup.
How does pricing and billing work for partners?
We set up pricing and billing with each partner when we create the partner account. You can export usage from the Partner Console. Want to try it first? Start free with up to 5 users.
