What is the Slack integration
The Slack integration sends notifications from Atender into a channel in your Slack workspace. Once it’s connected, your team gets pinged in Slack when a conversation needs attention — without anyone having to keep Atender open in a separate tab.
What you can be notified about
The integration supports four event types, each toggled independently:
- Assignment changes — when a conversation is assigned, reassigned, or unassigned
- Customer replies — when a customer sends a new message on an existing conversation
- SLA breaches — when a conversation crosses one of its SLA targets
- New conversations — when a new conversation arrives in the inbox
Each event becomes a Slack message in the channel you picked. You choose which events to enable; the others stay silent.
How it connects
The integration uses Slack’s standard OAuth flow. You sign in to Slack from inside Atender, approve the connection in Slack, and Atender stores a tenant-scoped token for the workspace you picked. One Slack workspace per Atender tenant.
Once connected, Atender lists the channels your Slack workspace has — public channels by default, private channels if Atender’s app has been added to them — and you pick one as the notification channel. You can change the channel later without reconnecting.
What it isn’t
The Slack integration is one-way: Atender posts into Slack, but Slack messages don’t come back into Atender as conversations. If you need two-way support — customers chatting with you via Slack — that’s a different shape of feature and isn’t covered here.
It’s also separate from any other Slack-related features in your tenant’s product. This is a tenant-internal notification channel, not a customer-facing connector.
Who can connect it
The integration is configured at the tenant level, so it’s a one-time admin setup. Any user with the Manage integrations permission can connect, change the channel, toggle events, or disconnect. Regular agents just see the notifications in Slack.