SLA Monitor logo SLA Monitor

Track Slack response SLAs before they slip.

Monitor external messages in the channels that matter most, receive pre-SLA alerts, and keep every workspace accountable to response-time commitments.

Add to Slack Install in minutes. No bot clutter in channels.
SLA Monitor app icon

What SLA Monitor does

SLA Monitor helps your team stay on top of response-time agreements in Slack. Choose the channels you care about, set an SLA (for example, 6 hours to reply, or 0.5 for 30 minutes), and choose the days, hours, and time zone for that channel. We watch for messages from people outside your workspace, and from any teammates you choose to include, that do not receive a timely reply.

Key features

Channel-level SLA rules

Set the reply window on each channel, in hours. 0.5 is 30 minutes. 0.25 is 15 minutes.

People outside the workspace

Track Slack Connect members and guests. A reply from a guest does not pass the SLA.

Members to include

Also track full members you choose, such as a client who belongs to your workspace. Their replies do not clear an SLA.

Operating hours and time zones

Set the days, start and end time, and time zone on each channel. A New York channel and a Manila channel can keep different hours. Messages outside the window are not tracked.

Pre-SLA alerts

Warn teammates before a deadline so someone can still reply in time.

Flexible notifications

Notify through Slack DM, email, and webhooks when alerts or failures are triggered.

Actionable failed list

Review missed messages in the Home tab with direct links and quick cleanup actions.

Workspace-safe setup

Install once and manage monitored channels and alert recipients without extra clutter.

How it works

  1. Add a channel and set its SLA in hours. Set the days, start and end times, and time zone, and optionally choose internal members whose messages should also be tracked.
  2. Add the SLA Monitor app to those channels.
  3. Configure optional pre-SLA alerts and who should be notified.
  4. SLA Monitor tracks new messages from people outside your workspace, and from the members you included, when they arrive inside that channel’s operating hours.
  5. If a full member of your workspace who is not on the include list replies in the thread within the SLA, the message passes. Otherwise it fails, the right people are notified, and it appears in “Messages that failed the SLA”.

Frequently asked questions

How much does SLA Monitor cost?

$15 per active channel per month. An active channel is one that received at least one tracked message in that paid month. The trial starts the first time a message is tracked, lasts 7 days, and is not charged. Workspaces already using the app when billing launched stay free until billing is turned on for them. Details are on the pricing page.

What types of alerts do you support?

SLA Monitor supports Slack DM alerts, email alerts, and webhook notifications. Pre-SLA alerts fire before the deadline. A separate list of members can be notified by DM when a message fails.

How do operating hours work?

Operating hours decide whether a message is tracked. They do not pause the clock. If a channel is set to Monday–Friday, 09:00–17:00, a message at 08:59 is ignored and a message at 09:00 is tracked. The deadline is the send time plus the SLA hours, including nights and weekends. The start time is included and the end time is not. Messages sent on a day you did not select are not tracked.

Can each channel use a different time zone?

Yes. The time zone belongs to the channel, not the workspace. A channel used by a team in New York can run 09:00–17:00 America/New_York, and a channel used by a team in Manila can run its own hours in Asia/Manila. Each team keeps the operating window that matches the people who have to answer.

Who is tracked, and whose reply passes the SLA?

Messages from people outside the workspace are tracked, including Slack Connect members and guests. You can also include full members of your workspace, and their messages are tracked the same way. A passing reply has to be in the thread, from a full member who is not on that include list. A guest reply, an emoji reaction, or a new message outside the thread does not pass the SLA.

What information is stored in your database and why?

We store workspace and team identifiers, installation data, channel settings (SLA hours, operating days, hours, time zone, and included members), alert configuration, and the message snippets needed to time an SLA and send notifications. A pending message is kept only while it is being timed. For billing and refunds, we also keep a log of each tracked message after that pending record is deleted. The log stores the workspace, channel, message timestamp, sender id, snippet, SLA hours, and when the message was tracked, so a monthly charge can be checked against the message that counted the channel. We store Stripe customer, subscription, and invoice ids. We do not store card numbers.

Questions or feedback? Email support@sla-monitor.com.