Zendesk’s official Slack app is what most teams mean by a Zendesk Slack integration. It creates tickets from Slack, posts ticket updates into channels and carries approval requests. In a Slack Connect channel it does less than most support leads expect, and the Zendesk articles don’t describe how much of a customer conversation it carries.
This page is written by Weft, which sells a Slack-native support inbox, so read the last section with that in mind. The facts come from Zendesk’s two Help Center articles and its pricing page, and from Slack’s help article on Slack Connect, all read on 2026-11-10. Zendesk’s install article carries no last-updated date or version number, so treat every statement here as a snapshot as of the read dates and recheck before a rollout. For the basics, see Slack Connect and customer support in Slack Connect.
What the app does in a shared channel
The usage article lists four ways to create a ticket from Slack: the /zendesk global shortcut, a Slack action that converts a message into a ticket, the Zendesk app in the sidebar, and the @zendesk mention. The shortcut and the action work only in channels where the app has been added. For a customer in a Slack Connect channel, the mention is the path that matters, because the article says users from external workspaces can’t use the global shortcut.
Updates travel the other way through triggers. The article says ticket updates show up in Slack channels “if your Zendesk administrator has configured triggers for Slack”. What lands in a channel is whatever your trigger conditions select. The article doesn’t say that a customer message nobody mentions becomes a ticket.
Approval requests are the one place with two-way behaviour the article spells out. Comments and responses sync in real time. Only comments added to the approval thread in Slack are recorded, an edited Slack message keeps only its original text, and a deleted message is not removed from Zendesk. Comments over 400 characters aren’t recorded in the approval request at all. Keep approval comments short and put the detail in the ticket.
Agents can’t close tickets from Slack, can’t edit ticket fields there, and can only assign a ticket to a group, not a person. So the case still closes in Zendesk, whatever the thread shows.
Internal notes need a rule of their own. The article says only other Zendesk agents can view a ticket’s internal notes, and that a note can be added from the Slack notification or by converting a reply in the thread into a comment. It doesn’t say how a note appears in the thread. Until you have tested that, keep internal discussion out of shared-channel threads.
Plans, admin rights and installation
The install article lists Support on Team, Professional or Enterprise, and Customer Service Suite on Team, Growth, Professional, Enterprise or Enterprise Plus. Employee Service Suite has a separate installation article, so check which product you run before you read further. The installer needs administrative privileges in Zendesk Support and permission to add apps in the Slack workspace.
On the Slack side, the integration cannot be installed on a shared Slack workspace, meaning the kind you join as an external guest. Check that before anyone starts the install. The same article warns that if the Slack Approve apps permission setting is off, the integration can potentially break, and recommends turning it on. It also says approval requests work with only one Slack workspace, so a second workspace can’t take approvals.
Enterprise Grid needs a separate check. Multi-workspace channels are supported, but organization-shared channels aren’t, and the article applies that limit to Slack Enterprise Grid plans only. If your shared channels are organization-shared, the integration won’t cover them.
The pricing page lists these as per agent per month list prices. Support Team is $19 billed annually and $25 billed monthly. Suite Team is $55 billed annually and $69 billed monthly. Suite Professional is $115 billed annually and $149 billed monthly. As a worked example, twelve agents on Suite Team are billed twelve times $55 a month on annual billing, or twelve times $69 on monthly billing, before tax and discounts. I couldn’t confirm from the pricing page which plan includes side conversations, which the install article says agents use to start and join Slack threads from a ticket. Ask Zendesk before you buy a plan for that.
Reinstalling keeps your settings, but you must re-add the app to each channel. The failure mode is a channel you forgot. The docs don’t say what a mention does in a channel without the app, so after any reinstall, post a test mention in every shared channel and check for a ticket.
External people in a Slack Connect channel
The usage article says internal and external users in a Slack Connect channel can create tickets with the @zendesk mention. External users don’t see the Assignee field in the new-ticket form. The requester defaults to the Slack user who made the mention and can be changed. The ticket is created in Support and added as a reply to the Slack thread. Mention-created tickets don’t get the created_from_slack tag, which the article says is added to tickets created in Slack.
Only the mention is documented for external people. The article doesn’t say that a plain customer message becomes a ticket, so someone on your side has to watch for messages nobody mentions. The article also doesn’t say whether an external person can see a ticket’s status in Slack. I didn’t find that answer, so don’t promise a status view until you have tested it.
If the mention is your entry point, the customer needs to know it. Put this in the channel topic or the first message: “Mention @zendesk in this channel with your question and we’ll open a ticket for it.”
Slack’s help article says external people join with either “Can post & invite” or “Can only post” permission, and that admins can restrict who can invite external people. Zendesk’s article doesn’t say which level the mention needs. Test with a Can only post guest, because that’s the customer who can’t bring in colleagues.
Two Slack limits shape the design. A Slack Connect channel can host up to 250 organizations, including your own, and external people can’t be added to #general or #all-companyname. Use a dedicated channel per customer or per group.
Reply sync and the test to run
The documented cases are trigger notifications, internal notes and approval comments. The usage article doesn’t describe an ordinary reply from a Zendesk agent appearing in the Slack thread, or a customer reply typed in the thread appearing on the ticket. That gap decides whether this works for your traffic, and a vendor’s claim about two-way sync doesn’t close it.
Run the test in a sandbox channel with a second Slack account you control, not in a live customer channel:
- From the second account, post “test 1: can you see this?” and mention @zendesk. Note the ticket number and the time.
- From Zendesk, send a public reply: “test 2: agent reply from Zendesk”. Note whether it appears in the thread and how many minutes it took.
- From the second account, reply in the Slack thread: “test 3: customer reply from Slack”. Note whether it appears on the ticket and how long it took.
- Attach a file to the Zendesk reply. The usage article says comment attachments aren’t included in the Slack notification, so expect none.
- Repeat test 1 from an account with Can only post permission.
Take the pass line from your own SLA. If you promise a first response in 60 minutes, a reply that takes longer than 60 minutes to reach the thread fails.
Decision rule: if tests 2 and 3 pass, you have seen the behaviour once in your workspace. The docs don’t commit to it, so pilot one channel for two weeks before you move more customers. If test 2 or 3 fails, write replies in Zendesk and treat the Slack thread as a notification feed.
Worked example: a team runs 40 shared channels and gets 300 customer messages a week. Suppose 180 of them need an answer in the channel itself. That’s 180 of 300, more than half of all traffic. The test decides whether Zendesk can carry that share. One passing day doesn’t settle it, so repeat the test after a month of real traffic.
Ticket and thread links, and reporting
The usage article describes a mention-created ticket as a reply posted into the Slack thread. It doesn’t describe the thread as a way to reply to the ticket. Give each open request one owner in Zendesk, and treat the thread as the place the customer sees the conversation, not where your team works it. Decision rule: if a customer message in the thread has no matching ticket update within your first-response target, assign the request to a group in Zendesk and post the ticket number in the thread so the next person sees it.
Reporting needs a fix. A Zendesk report filtered on created_from_slack undercounts Slack Connect tickets created by mention, because the tag isn’t added to them. Build a second count with a tag that a trigger adds, and confirm the trigger fires on a test mention before you trust the number.
The four documented creation paths don’t include a plain customer message, so check every shared channel for customer messages with no ticket at an interval no longer than half your first-response target. For a one-hour target in business hours, that means checking at least every 30 minutes. With hourly checks, a message posted just after a check can sit unticketed for almost two hours before the next check finds it, which breaks the target. With checks every 30 minutes, the worst case is about 30 minutes unticketed, which leaves room to open the ticket inside the hour. An unticketed customer question older than your first-response target is a missed request, not a backlog item.
When to stay on Zendesk and when to look elsewhere
Stay on Zendesk if most shared-channel traffic is alerts, approvals and handoffs, and customer replies already go out of Zendesk. Don’t switch because of the channel. Log who mentions @zendesk and when for a month, so you know the real entry rate before you decide anything.
Look at a Slack-native inbox if most shared-channel messages are customer questions that need a direct reply in the channel, and the reply test fails. That is the edge case. Weft is one product built for that case: a Slack-native support inbox for shared Slack Connect channels. If your traffic is mostly coordination, Zendesk is the right tool, and you don’t need to change it.