Settingsbeginner

What is the Slack integration

Connect a Slack workspace to Atender to receive notifications about assignments, customer replies, SLA breaches, and new conversations in a Slack channel.

4 min read

What is the Slack integration

The Slack integration connects an Atender tenant to a Slack workspace. Once it’s connected, Slack can be used in two ways: as an inbound conversation channel for customer messages, and as an internal surface for team notifications and side-channel updates.

That means your team can receive and handle Slack-originated conversations in Atender, while also getting pinged in Slack when conversations need attention — without anyone having to keep Atender open in a separate tab.

What you can be notified about

The integration supports seven 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
  • New incidents — when a new status-page incident is created
  • Incident updates — when an existing incident gets a new update
  • Resolved incidents — when an incident moves into resolved

Each event becomes a Slack message in the channel you picked. You choose which events to enable; the others stay silent.

A new connection starts with all events off, so nothing posts until an admin turns an event on.

Each incident post shows the incident title with a link, the status, the severity, the affected components, and the update text. Internal incidents post too. A move into resolved posts once.

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 only the channels the Atender app has been invited to, whether they’re public or private. You can then decide how those channels should work in Atender.

How Slack channels work

Inbound support channels are configured under Settings → Channels → Slack, while notifications are configured under Settings → Integrations → Slack notifications.

Slack channels where the Atender bot is a member can be used for different purposes:

  • Support channels — messages in the channel create conversations in Atender. The channel can use the Agent Stack you choose, or it can be humans-only so no Agent Stack responds automatically.
  • Incidents channel — one Slack channel can be selected for publishing status-page incident updates. Incidents-channel setup lives in Settings → Incidents → Slack.

Direct messages use a workspace-level Agent Stack instead of a per-channel stack. You can control whether people can DM the bot with the Allow direct messages toggle.

Slack membership controls access for private invite-only channels. To use a private channel with Atender, the Atender bot must be invited to that channel in Slack.

Controlling which channels appear

Atender only shows Slack channels the bot can access. To make a channel available in Atender, invite the Atender bot to that channel in Slack. To remove a channel from the available list, remove the bot from the channel.

The notification channel picker and the side conversation channel picker follow the same rule: each lists only the channels the Atender app has been invited to. If a picker is empty, it reads “No channels found. Invite the Atender app to a channel in Slack to see it here.”

If a saved notification channel is one the app has since left, a public channel keeps its name on the settings card; a private one shows as “Unknown channel”.

This keeps channel access controlled from Slack: if the bot is not a member of a channel, Atender cannot receive messages from that channel or configure it as an inbound Slack channel.

Who can connect it

The integration is configured at the tenant level, so it’s a one-time admin setup. A user with the API & integrations permission can connect Slack for notifications, toggle events, or disconnect it under Slack notifications. Support channels, Agent Stacks and Allow direct messages under Channels → Slack need the Channel settings permission. Regular agents just see the relevant conversations and notifications.

See also

Tags

Concept