← Back to Dashboard
JAMSHelp Center

Slack

Deliver JAMS Incident Management alerts straight into Slack, where most teams already live. Alerts arrive as Block Kit messages with Acknowledge and Escalate buttons, and because each responder links their own Slack account, acknowledgements are attributed by name — the message flips to "Acknowledged by [name]" the moment someone responds, even if they acknowledged from a phone call instead.

Plan availability: Slack alerts are included on every plan, including Free, and are never counted against an allowance. See Plans & Billing.

Slack is both a notification channel (pickable per recipient, alongside email, SMS, call, push, and Teams) and a target (you can post to a whole Slack channel instead of an individual). You configure it once per tenant at /integrations/slack.

What you'll get

After setup:

  • A flow fires → linked responders get a Block Kit message in their JAMS Incident Management bot DM, or the alert posts to a Slack channel you chose
  • The message shows the alert and an Acknowledge button (plus Escalate when there's a next rung in the escalation policy, and a View Log button when a job log is attached)
  • Tapping Acknowledge flips the message to a green "Acknowledged by [name]" status and stops the escalation
  • Acknowledging on any other channel (a phone call, an SMS reply, the dashboard) rewrites the Slack message in place too — so nobody acts on an alert someone else already took

What you'll need

  1. A Slack workspace, with permission to add an app to it.
  2. A JAMS Incident Management admin to install the app and claim the workspace (the admin who installs owns the link).
  3. The JAMS Incident Management Slack app available on your environment. If the /integrations/slack page shows "The Slack app isn't configured on this environment yet," contact support — the app is provisioned per environment.

Step 1 — Add the app to Slack (admin)

  1. In JAMS Incident Management, open /integrations/slack and click Add to Slack.
  2. Approve the requested permissions for your workspace. The admin who installs claims the workspace for your tenant.

Back on the page, the Connection card should now read "Connected to [your workspace]."

Why this matters: the install is what gives JAMS Incident Management the bot token it needs to post into your Slack. Until an admin completes Step 1, the status page stays on "Not connected yet" and Slack alerts won't deliver. Always install via the Add to Slack button here — not by installing from the Slack app settings — so the connection is captured.

Step 2 — Each responder links their own account

Every person who should receive Slack alerts (and have their acks attributed by name) links their own account:

  1. In Slack, open a DM with the JAMS Incident Management bot and send it any message (e.g. "hi").
  2. Tap Connect to JAMS Incident Management on the card it replies with, and sign in.

Once linked, they appear under Linked users on /integrations/slack, with the date they connected. An admin can Revoke anyone's link from that table; the person can reconnect later from the bot card.

Why this matters: attribution is per-user. If a responder hasn't linked their account, JAMS Incident Management has no Slack identity to DM them at — they'll still get your other channels (call/SMS/email/push), just not a Slack message. Link first.

Using Slack in a flow

As a per-recipient channel

Anywhere you pick channels for a recipient, Slack is now one of the options (Call, SMS, Email, Push, Teams, Slack):

Pick Slack for a User or Group recipient and JAMS Incident Management DMs each linked person the alert message when the flow fires.

As a channel target (post to a whole Slack channel)

Instead of (or in addition to) DM'ing individuals, you can post the alert to a Slack channel — useful for a shared "#incidents" channel the whole on-call team watches.

  1. In Slack, invite the bot to the channel: /invite @JAMS Incident Management (private channels must invite it; for public channels you can also just @mention it).
  2. The bot joining (or being @mentioned) registers the channel. Reload /integrations/slack and it appears under Channels.
  3. In the flow builder or on the JAMS / Azure Monitor connection forms, pick it from the Slack Channels (post to channel) group in the recipient picker.

Channel posts are independent of the per-user channel checkboxes. A Slack (or Teams) channel target carries its own delivery — it posts to that channel regardless of which "Channels to use" boxes (Call/SMS/Email/Push/Teams/Slack) are ticked. Those checkboxes only control how the individual user/group/rotation recipients are reached. So you can, for example, post to a Slack channel and phone-call the on-call person, without Slack-DM'ing individuals.

The message

When an alert lands, responders see a message with:

  • The alert title and body (and a source tag like "JAMS Scheduler" or "Azure Monitor" when applicable)
  • An Acknowledge button — always present. For integration flows with native verbs (e.g. Azure Monitor's Close), the message shows those buttons instead.
  • An Escalate button — shown only when the notification has a next rung in the escalation policy
  • A View Log button — when a JAMS Scheduler job log is attached to the alert

Tapping a button posts back to JAMS Incident Management and runs the same acknowledge/escalate logic as the voice, SMS, Teams, and dashboard paths — so the whole escalation group stays in sync no matter which surface the responder used.

Troubleshooting

SymptomLikely causeFix
Status page says "The Slack app isn't configured on this environment yet"The Slack app isn't provisioned for your environmentContact support — the app is provisioned per environment, not from this page.
Status stuck on "Not connected yet"No admin has installed the app via Add to SlackAn admin clicks Add to Slack on the integration page (Step 1).
A responder gets calls/SMS but no Slack messageThat person hasn't linked their Slack accountHave them DM the bot and tap Connect (Step 2); confirm they appear under Linked users.
You DM the bot but get no reply / no Connect cardThe bot can't receive messagesMake sure the app's Messages tab is enabled and event subscriptions are configured (admin/support).
No Slack Channels option in a flow's recipient pickerThe bot isn't in any channel yet/invite the bot into the channel you want to post into, then reload the form.
A channel shows as a code like C0… instead of its nameThe channel name hadn't resolved at capture time@mention the bot in that channel once to refresh it.

What's next