Skip to content
Help Center
Submit a request Sign in

Connect and manage Slack

The Slack integration connects one Slack installation to a Supportbench account. It supports the enabled messaging and case-conversation workflows while showing the connected workspace and granted capabilities.

Applies to: Supportbench Core. Location: Settings → Integrations → Slack. Requires Administer all integrations.

Before you begin

  • You need Administer all integrations and authorization to connect the intended provider organization. Obtain credentials through your approved provider process; keep them out of screenshots and support messages.
  • Identify the intended Slack workspace and operational channel, and the supported Supportbench workflow or Case conversation that will use it. This settings page verifies the installation; it does not synchronize customer tables.
  • Choose approved test records and people before sending messages, creating engineering work or making calls. Record the current connection identity and enabled options so the test has a clear expected result.

Configure and verify

  1. Open Settings → Integrations → Slack. If disconnected, choose Install Slack and authorize the intended workspace through the provider flow.
  2. After returning, verify the read-only Workspace, Default channel and Installed. Those installation details are not editable text fields on this page.
  3. Choose Test connection and review Granted capabilities and Credential: Secure credential stored or Credential missing. Resolve Needs attention before relying on delivery.
  4. Set Slack messaging active when the valid token and required mapping allow it, then choose Save Changes.
  5. Test the intended supported message/workflow surface with a controlled channel and Case. Verify actual delivery and context; connection success alone does not prove every optional surface is enabled.
  6. To disconnect the saved routing, choose Remove Slack only after reviewing dependent workflows and conversations. It removes Supportbench’s saved workspace connection/routing, not the provider’s installed Slack app.

Settings reference

Connection and operating controls

SettingWhat it controlsHow to choose
Install SlackStarts the provider installation when no connection exists.Authorize the intended workspace.
Workspace / Default channel / InstalledRead-only installation summary.Confirm the workspace and channel after returning from Slack.
Test connectionChecks an installed connection.Resolve a Needs attention status before relying on delivery.
Slack messaging activeControls messaging availability for a valid installed connection.The switch may be unavailable when the token or mapping is missing or invalid.
Granted capabilities / CredentialShows the connection’s capabilities and credential status.Review scope without copying credentials.
Remove SlackRemoves Supportbench’s saved workspace connection and routing. It does not uninstall the app in Slack.Review dependent workflows and conversations before removal.

Behavior to know

  • Workspace and channel are installation details, not editable text fields on this page.
  • The displayed capabilities include channel/workflow messages, case creation/assignment, threaded case conversations and secure file links where the associated surfaces are enabled.

Recommended use

  • Use a channel whose membership is appropriate for the support information being sent. A working connection does not make every Case detail suitable for every Slack channel.
  • Give the integration and each sending workflow a named owner. Verify actual delivery and thread context after changing the workspace, messaging state or related workflow.
  • Inspect Granted capabilities for the specific message/file operation that fails. Avoid repeatedly reinstalling a healthy connection when the missing capability or application surface is the actual constraint.

Worked example: verify an escalation reaches the intended support channel

  1. Illustrative situation: a B2B support team coordinates urgent equipment incidents in its approved Slack channel #equipment-support. The name is an example; use an actual authorized channel and a clearly labeled test Case with no private customer attachments.
  2. Review Workspace, Default channel and Installed after Install Slack returns. Confirm this is the support organization’s workspace rather than an unrelated personal workspace. These read-only installation details are evidence, not fields to type over.
  3. Choose Test connection, inspect Granted capabilities and Credential, then save Slack messaging active when permitted. Identify the particular enabled workflow or Case conversation that sends the test message; installation alone does not send it.
  4. Run one approved test through that supported surface. Have an authorized participant inspect the actual Slack channel and, where the surface uses a conversation thread, the expected thread. Confirm the Case reference and message context are useful without disclosing unnecessary customer information.
  5. If the connection is healthy but the message is absent, inspect the sending workflow, active state, destination and relevant capability. If an optional file or conversation action is unavailable, establish whether that surface is supported/enabled before changing the installation.
  6. Record the verified destination and the owner of failed-delivery follow-up. Keep customer commitments and Case ownership in the normal support process; a Slack message does not by itself prove that the customer received an update or the escalation was resolved.

Troubleshooting

ProblemWhat to check
Slack messaging active is unavailableUse Test connection and inspect token/mapping and capability status. The switch needs a valid connection.
Workspace or Default channel cannot be editedThey are read-only installation details. Review the authorized workspace/installation rather than typing over them.
The connection is valid but an action is missingThe associated Case, workflow or file surface must also be supported and enabled. Check the specific capability.
Slack still lists the app after removalRemove Slack clears Supportbench’s saved connection/routing; it does not uninstall the app from Slack.
A message did not arriveInspect connection status, active setting, intended channel and the specific sending workflow.
  • Integrations → Use the data synchronization log
  • Organization → Configure agent roles and division access

Was this article helpful?