Zendesk and Slack, Without the Noise
Two jobs, one integration: telling a channel that something happened, and turning a Slack message into a real ticket. The second one is where the value is.
What it does
Notification patterns that survive
Every Slack integration starts useful and ends muted. The ones that survive follow two rules.
Notify on action required, not on activity. A channel that pings on every ticket update gets muted within a week, and then you lose the escalation notification too.
One channel per meaning. A channel for breaches, a channel for VIP customers, a channel for outages. Merging all three into a general support channel means all three get ignored equally.
The internal duplicate problem
Here is the pattern that catches teams out. Someone in sales messages the support channel about a customer issue. An agent creates a ticket from it. Meanwhile the customer has emailed support directly about the same thing.
Two tickets, one problem, and they look completely unrelated: one from the customer address, one created internally from Slack with a different requester and different wording.
This is the duplicate type manual review almost never catches, because nothing about the two tickets looks alike except the underlying problem.
Frequently asked questions
Can you create a Zendesk ticket from a Slack message?+
Yes, that is one of the main features and the one worth setting up first.
Should agents reply to customers from Slack?+
Sparingly. It works for speed and it hides the conversation from anyone working in Zendesk, which is how two agents end up answering the same thing.
Catch the tickets Slack creates twice
Internally raised tickets and customer emails about the same problem look unrelated. Content matching finds them anyway.
Start free trial14-day free trial. No credit card required.