Integrating SparrowDesk with Slack

Vaishali

Vaishali

May 15, 2026

If your team gets support requests directly in Slack, the Slack integration lets you convert those messages into SparrowDesk tickets without leaving the channel- so Slack stays in your team's workspace and SparrowDesk stays in the system of record.

What you can do with the Slack integration

Once Slack is connected, your team can:

  • Turn any Slack message into a SparrowDesk ticket using an emoji reaction or automatically for every message in a channel
  • Sync replies between the Slack thread and SparrowDesk conversation in both directions
  • Let non-agent Slack users participate in threads without consuming agent seats
  • Keep all ticket data, history, and assignments managed inside SparrowDesk

Before you start

Make sure you have:

  • Admin access in SparrowDesk
  • Admin access to the Slack workspace you want to connect
  • The Configure Slack Channel permission in SparrowDesk (Account owners and admins have this by default)

Note: The Slack integration is available on the Starter plan and above.

Connecting your Slack workspace

  1. Go to Settings in SparrowDesk.
  2. Under channels
  3. Find Slack in the list.
  4. Click Connect Slack.
  5. Sign in with your Slack account and authorise the required permissions.
  6. Once connected, the SparrowDesk app is installed in your Slack workspace.

Image

Image

Image

After connecting, add the SparrowDesk app to any channel where you want tickets to be created. Private channels require you to manually invite the app inside Slack first.

Note: SparrowDesk can only act in channels where the app has been explicitly added. It does not have workspace-wide access.

Connecting a channel to a brand

Each channel must be mapped to one brand in SparrowDesk before ticket creation begins.

  1. Go to Settings → Slack.
  2. Select your connected workspace.
  3. Click Add channel.
  4. Choose the channel from the list.
  5. Select the brand to map it to.
  6. Choose a ticket creation mode (see below).
  7. Click Save.

Image

One channel maps to one brand only. One brand can be connected to multiple channels. To change a channel's brand, update the existing mapping.

Ticket creation modes

Each channel is set to one of two modes when you configure it.

Mode

How it works

Every Message

Every top-level message in the channel creates a new ticket. Replies inside the thread sync into that ticket.

Emoji Reaction

An agent adds a specific emoji to a message to trigger ticket creation. Only agents with permission to create tickets can trigger this.

Every Message mode excludes bot messages- messages from Slack-native bots or the SparrowDesk bot itself do not create tickets.

Image

Emoji Reaction mode- the first valid emoji reaction creates the ticket. Removing the emoji afterwards has no effect. If the emoji is added to a threaded reply, the ticket anchors to the thread root.


Image

Select the desired mode and click connect.

Each slack channel can be configured according to your requirement.

How conversation sync works

One Slack thread maps to one SparrowDesk conversation. How that conversation starts depends on the ticket creation mode set for the channel.

Every Message mode

Every message posted in the channel creates a ticket in SparrowDesk automatically. No agent action is needed.

Image

Once the ticket is created, all replies in that Slack thread sync into the SparrowDesk conversation in order.

Emoji Reaction mode

An agent reacts to a message with the configured emoji to trigger ticket creation. Only agents with permission to create tickets can do this.

Image

The message that was reacted to becomes the ticket root. All replies in that thread sync into SparrowDesk from that point.

Regardless of mode:

  • Agent replies in SparrowDesk post back to the Slack thread automatically
  • Internal notes in SparrowDesk are not synced to Slack
  • Message order is preserved
  • Attachments and links sync as read-only metadata

Image

If a ticket is resolved and someone replies in the linked Slack thread, the ticket reopens automatically.

Requesters and Slack Participants

The requester on a ticket is the author of the message that triggered ticket creation. You can change the requester from inside SparrowDesk after the ticket is created.

Other Slack users who reply in the thread appear as Slack Participants — a non-billable participant type that does not consume agent seats. Slack Participants cannot log in to SparrowDesk but their messages sync into the conversation alongside agent replies.

FAQ

  1. Can non-agents create tickets using the emoji reaction?
    No. Only SparrowDesk agents with an active seat and permission to create tickets can trigger ticket creation via emoji reaction. Reactions from non-agents are ignored.
  2. What happens if the SparrowDesk app is removed from a Slack channel? SparrowDesk stops syncing new messages from that channel. Existing tickets remain intact with all history preserved.
  3. Can the same Slack channel be connected to more than one brand?
    No. Each channel maps to one brand only. To use a channel for a different brand, update the existing mapping for that channel.
  4. What happens if a Slack user's account is deactivated?
    The ticket remains open and the deactivated user stays as the requester. All message history and attribution are preserved.
  5. Does editing a Slack message after ticket creation update the ticket?
    No. SparrowDesk stores a snapshot of the message at the time the ticket is created. Edits made in Slack afterwards are not reflected in SparrowDesk.


Powered By SparrowDesk