Search
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.
Once Slack is connected, your team can:
Make sure you have:
Note: The Slack integration is available on the Starter plan and above.



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.
Each channel must be mapped to one brand in SparrowDesk before ticket creation begins.

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.
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.

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.

Select the desired mode and click connect.
Each slack channel can be configured according to your requirement.
One Slack thread maps to one SparrowDesk conversation. How that conversation starts depends on the ticket creation mode set for the channel.
Every message posted in the channel creates a ticket in SparrowDesk automatically. No agent action is needed.

Once the ticket is created, all replies in that Slack thread sync into the SparrowDesk conversation in order.
An agent reacts to a message with the configured emoji to trigger ticket creation. Only agents with permission to create tickets can do this.

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

If a ticket is resolved and someone replies in the linked Slack thread, the ticket reopens automatically.
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.
Powered By SparrowDesk