SLA Monitor
Guide
How to track SLAs in Slack Connect
To track SLAs in Slack Connect, measure the time between a message from outside your workspace and the first thread reply from a full member of your own workspace. Slack does not time that gap. SLA Monitor does: you pick the shared channel, set the hours allowed for a reply, and invite the app into the channel. Messages from the other organization, and from guests, start the clock. A qualifying reply clears it. If the reply is late, the message is marked failed and the people you chose are notified.
Track reply times in the Slack Connect channels your clients already use.
Add SLA Monitor to SlackWhat a Slack Connect SLA actually measures
An SLA here is a reply-time promise: after someone outside your company posts in a shared channel, your team has a set number of hours to answer in that thread.
Slack Connect is the feature that puts people from two organizations in one channel. Client support, onboarding, and vendor channels are the usual places. The message that matters is rarely one of yours. It is the client’s. The reply that matters is yours, in the thread, before the deadline.
The clock is a straight number of hours from the moment the message is sent. It does not pause at night, on weekends, or outside the hours you chose. Those hours do a different job, covered below: they decide whether the message is tracked at all.
You can set the window in hours, including fractions. 0.5 is 30 minutes. 0.25 is 15 minutes. 4 is four hours. Use up to two decimal places.
Why Slack does not track this for you
Slack is a conversation tool. It can remind someone, save a message, or post a workflow message. It does not score a Slack Connect thread against a reply-time target.
- Saved reminders and scheduled messages depend on a person remembering to set them.
- Workflow Builder can post a prompt. It does not know whether a member of your workspace has already replied in the thread.
- Channel notifications fire for activity, not for a missed deadline.
- Analytics and message exports can show volume. They do not mark a specific client message as passed or failed.
A spreadsheet filled in after the fact has the same gap. The timestamp you need is the first qualifying reply, and someone has to notice that the reply never came. That is the job of a tracker sitting in the channel.
Who counts as outside your workspace
SLA Monitor treats a sender as external when they are not a full member of the workspace where the app is installed. In a Slack Connect channel, that is most of the people from the other company.
| Who sent it | Starts an SLA? | A reply from them clears an SLA? |
|---|---|---|
| Someone from the other organization in a Slack Connect channel | Yes | No |
| A single-channel guest or a multi-channel guest | Yes | No |
| A full member of your workspace | Only if you add them to the include list | Yes, unless they are on that include list |
| A bot | Only if you turn on messages from bots | No |
Guests are members of your workspace in Slack’s directory, but they are not full members. SLA Monitor tracks them the same way it tracks Slack Connect users. A reply from a guest does not count as your team answering.
What clears an SLA, and what does not
A message passes when a full member of your workspace replies in the thread before the deadline, and that person is not on the include list. The reply has to be a thread reply. A new message in the channel, even from the right person, does not close the original message.
These do not clear it:
- Another message from the client, or from anyone else outside your workspace.
- A reply from a guest.
- A reply from a teammate you added to “Include messages sent by these Slack members.” Those people are being monitored, so their replies are not treated as the team answering.
- An emoji reaction.
- A reply posted after the deadline. The message has already failed.
Only messages sent after you add the channel are tracked. Editing the SLA later does not rewrite messages already on the clock. The new hours apply to messages sent after the change.
How to set up SLAs in Slack with SLA Monitor
This is the setup for any channel, shared or not. The Slack Connect steps in the next section add the invite and the question of who is external.
- Open Add SLA Monitor to Slack and install the app in the workspace that owns the support process. Each workspace that installs it has its own channels and history.
- In Slack, open SLA Monitor and go to the Home tab.
- Choose Add channel.
- Select the channel and enter the SLA in hours. For example,
8for a business day,1for an hour, or0.5for 30 minutes. - Set the operating days, the start and end time, and the time zone. Messages sent outside that window are not tracked. The label under the days field says the same thing. The end time is exclusive: a window of 09:00–17:00 includes 16:59 and does not include 17:00.
- Optionally choose full members of your workspace whose messages should also be monitored.
- Leave “Include messages from bots” off unless a bot is standing in for a client.
- Optionally choose who should get a direct message when a message fails.
- Save the channel. On the Home tab, use Add app to channel, open the channel, and type
/invite @SLA Monitor. The app does not join by itself. Until it is in the channel, it cannot see new messages.
From then on, a qualifying message is stored as pending. If a qualifying reply arrives in the thread in time, it is cleared. If the deadline passes with no such reply, it moves to Messages that failed the SLA on the Home tab, and the failure notification goes out if you set one.
Install it in the workspace that has to answer.
Add SLA Monitor to SlackHow to set up SLAs in a Slack Connect channel
A Slack Connect channel already has people from at least two workspaces in it. You install SLA Monitor only in your workspace. The other company does not install it, and they do not see your SLA settings, your alerts, or the failed-message list.
- Confirm the channel is a Slack Connect channel and that your team is the one responsible for the reply time. If both sides owe a response, each side needs its own tracker in its own workspace.
- Follow the setup above and select that shared channel. Public channels and private channels can both be monitored. For a private channel, the app can only be invited after someone in the channel adds it.
- Invite
@SLA Monitorinto the shared channel with/invite @SLA Monitor. People in the other organization will see that an app was added, the same way they see any other app in a shared channel. They will not see the SLA. - Do not add the client’s Slack Connect accounts to the include list. They are already external. Their messages start an SLA on their own.
- Add a full member of your workspace to the include list only when that person writes messages that should be treated like a client message. A common case is a client who was invited into your workspace as a full member, rather than through Slack Connect. People on that list do not clear an SLA by replying.
- Send a test from an account outside your workspace, then reply in the thread from a full member who is not on the include list. The test message should clear. A second test with no thread reply should fail after the SLA you set.
Public and private Slack Connect channels
The rule is the same in both. The difference is visibility. In a public shared channel, any member who can post can invite the app. In a private shared channel, only people already in the channel can invite it, and the app cannot list that channel until it has been invited.
What the other company experiences
They keep using the channel as they do now. They are not asked to install SLA Monitor. A late reply is your internal signal. It is not a message posted back into the shared channel unless you build that yourself with a webhook.
Operating hours, internal members, and bots
Operating hours filter the message, not the clock
If you set Monday–Friday, 09:00–17:00, America/New_York, a client message at 08:59 New York time is ignored. A message at 09:00 is tracked. The deadline is then that send time plus the SLA hours, including hours that fall outside the window. A message at 16:00 with a 4-hour SLA is due at 20:00, not at 12:00 the next working day.
Use this when you do not want overnight or weekend messages to open an SLA. Do not use it if you expect the clock to pause. It will not.
If the end time is earlier than the start time, the window crosses midnight. If start and end are the same, the whole day is inside the window. If no time zone is saved, every message is eligible.
Full members you still want to monitor
The field is “Include messages sent by these Slack members.” It sits above operating days. Use it for people who are full members of your workspace but should be treated as the customer. Everyone else in your workspace stays off the clock, and their thread replies are what pass the SLA.
Bots
Bot messages are ignored unless you check “Include messages from bots.” Turn that on only when the bot is the client, for example a form that posts into the channel. Leave it off for your own status bots, or they will open SLAs you never meant to track.
Alerts before a message fails
A failure notice tells you the deadline has already passed. A pre-SLA alert tells you it is about to. On the channel, open Configure alerts. Each alert is a number of minutes before the deadline, delivered by Slack DM, email, webhook, or a combination.
A 30-minute alert on a 4-hour SLA fires about 3 hours and 30 minutes after the message, if it is still unanswered. Checks run every minute, so the warning lands within about a minute of that moment, while the deadline is still ahead. The failure itself lands within about a minute after the deadline.
If the alert is further out than the SLA, it never fires. A 60-minute warning on a 30-minute SLA is already in the past when the message arrives. Set the warning shorter than the SLA.
The failure DM list on the channel is separate. Pre-SLA alerts use the people, addresses, and webhook URLs on the alert. The failure DM uses “Notify these members when a message fails SLA.”
How to review messages that missed the SLA
Open the SLA Monitor Home tab and scroll to Messages that failed the SLA. Each row shows the channel, a snippet, who sent it, when it was sent, and when it failed. View message opens the original Slack message. You can copy that link or remove the row when you have dealt with it.
Removing a row only removes it from this list. It does not delete the Slack message, and it does not change the fact that the reply was late.
A workable SLA policy for client channels
Pick one number your team can actually hit, then make the exception list small.
- Use a short SLA, such as 1 hour or 30 minutes, on channels where a client is blocked.
- Use a longer SLA, such as 8 or 12 hours, on channels that are questions rather than incidents.
- Set operating hours to the shift that is staffed. Remember the clock still runs straight through once a message qualifies.
- Put one pre-SLA alert far enough ahead that someone can still reply, and not so far ahead that it is noise.
- Name the people who get the failure DM. An empty notify list still records the failure. It just does not tell anyone.
- Keep the include list for real exceptions. If everyone on the team is on it, nobody’s reply will clear the SLA.
Mistakes that make a good SLA look broken
- The app is not in the channel. Adding the channel on the Home tab does not invite it. Run
/invite @SLA Monitor. - The reply was not in the thread. A follow-up in the channel is a new message. It does not close the first one.
- A guest replied. Multi-channel guests and single-channel guests are external. Their reply does not pass the SLA.
- The person who replied is on the include list. Those replies are ignored on purpose.
- The message was outside operating hours. It was never tracked, so it will not show as failed either.
- The test came from a full member who is not on the include list. That message is ignored. Test from a Slack Connect account or a guest.
- You changed the SLA and expected old messages to move. Only messages sent after the change use the new hours.
Questions people ask
How do you track SLAs in Slack Connect without asking the client to install anything?
Install SLA Monitor in your workspace, add the shared channel, and invite the app there. The other organization keeps posting as they already do. Their messages start the SLA because they belong to a different workspace.
Can one SLA cover every channel?
No. Each channel has its own hours, time zone, include list, and alerts. A client incident channel and a general shared channel should not share one number.
Does a reaction or a “we’re looking” message from a guest count?
A reaction does not count. A guest’s message does not count as your team’s reply. Someone who is a full member of your workspace has to reply in the thread.
What if both companies owe each other a response?
Each company tracks its own side. SLA Monitor in your workspace measures your replies to their messages. It does not grade the other company’s replies to you.
Where do failed Slack Connect messages show up?
On the Home tab of SLA Monitor, under “Messages that failed the SLA,” with a link back to the Slack message. They are not posted into the shared channel.
Add the channel, set the hours, and invite the app. The next external message starts the clock.
Add SLA Monitor to Slack