A Slack message action lets an agent turn an existing Slack message into a Zendesk ticket in a few clicks, without retyping the request. The action ships with the Slack for Zendesk Support app and is available in any channel where that app has been added.
This guide walks through the flow end-to-end: prerequisites, the five clicks to create a ticket, and the limitations that typically send teams looking for a fuller integration. If you need bidirectional sync, thread attachments, custom forms in Slack, or ticket creation from DMs, ClearFeed's Slack + Zendesk integration covers those flows.
Prerequisites
- The Slack for Zendesk Support app is installed in your Slack workspace and connected to your Zendesk instance by a Zendesk admin.
- The Zendesk app has been added to the channel where the message lives.
- The person creating the ticket has a Zendesk agent seat and matching identity in Slack. Single-channel guests generally cannot access message-level app actions unless upgraded to multi-channel guests by a Slack admin.
Step #1: Hover Over the Message to Reveal Options
In the Slack channel, find the message you want to turn into a ticket and hover over it. Slack surfaces the message toolbar with reactions, reply, share, save, and the overflow menu.
Step #2: Open Message Actions
Click the More actions icon (three vertical dots) at the right of the message toolbar. The overflow menu lists every app action available for that message.
Step #3: Initiate Ticket Creation
From the overflow menu, select Connect to apps and select Create a ticket (added by the Zendesk Support Slack app). Slack opens the Create new ticket modal.
Step #4: Fill in the 'Create New Ticket' Form
The modal exposes four fields.
- Subject. A short, specific summary of the request. This is the ticket title agents see in the Zendesk queue.
- Requester (optional). Defaults to the Slack user submitting the ticket and is editable. Clicking the field opens a searchable list of Slack users; selecting someone who doesn't yet exist in Zendesk creates a new Zendesk Support end-user tied to the ticket.
- Assignee (optional). Assigns the ticket to a Zendesk group. Type to filter the group list. Individual agent assignment is not available from this form.
- Description. The body of the ticket. The text of the Slack message you converted is pre-filled here and is fully editable.
Step #5: Submit the Ticket
Click Submit. The Zendesk app creates the ticket in Zendesk Support and posts a confirmation reply to the original Slack thread with the ticket number, status, priority, and timestamp.
Limitations of the Slack action
The native Slack action is designed for single-message ticket creation, not for running full support workflows in Slack. The gaps teams hit most often:
- Single message only. Only the text of the message you actioned is copied into the ticket. Prior thread context, later replies, reactions, and files stay in Slack.
- No attachments. Files or images in the Slack message are not transferred to the Zendesk ticket.
- No bidirectional sync. Replies posted on the Zendesk ticket are not mirrored back to the Slack thread; Slack replies do not sync into Zendesk.
- No custom forms. The modal exposes Subject, Requester, Assignee, and Description only. Custom Zendesk fields, brand routing, and conditional fields are not surfaced.
- No status updates in Slack. Once submitted, the channel does not receive automatic notifications when the Zendesk ticket status changes.
- Guest restrictions. Single-channel guests cannot use message actions without being upgraded to multi-channel guests in Slack.
When to use ClearFeed instead
ClearFeed layers Zendesk ticketing onto Slack the way a support team actually works: from threads, DMs, triage channels, and forms, with sync in both directions.
- Ticket creation from Slack threads. React with a 🎫 emoji, tag the ClearFeed bot on the top-level message, run /cf-file, or turn on automatic ticketing to convert every new thread into a Zendesk ticket. Thread messages and attachments carry over to the Zendesk ticket.
- Bidirectional message sync. Replies in the Slack thread and replies in the Zendesk ticket sync both ways, and status changes (including Zendesk custom statuses) post back to Slack.
- Custom forms on Slack. Import existing Zendesk forms or build new ones with text, drop-down, multi-select, number, date, email, phone, tags, and attachment fields, plus conditional fields and brand routing via Zendesk form-brand mapping.
- Private and DM ticketing. With ClearFeed's Internal Helpdesk or Integrations editions, requesters can file tickets from personal DMs or via Slack shortcuts such as /cf-file.
- Reverse Zendesk flow. Zendesk tickets that originate outside Slack (email, Help Center, web widget) can be routed into a Slack channel for the support team to work on, with the same bidirectional sync.
- CSAT sync. ClearFeed can collect CSAT responses in Slack and write them back to the linked Zendesk ticket, supporting 2-, 3-, 4-, and 5-point surveys.
- Fewer paid Zendesk seats. Responders can work Zendesk tickets from Slack without a full Zendesk agent seat, and Light Agent public replies can be proxied through ClearFeed so those replies still reach Zendesk.
Want to work from Slack on Zendesk tickets?
Upgrade to ClearFeed for two-way Slack ↔ Zendesk sync, custom forms in Slack, ticket creation from threads and DMs, and reduced Zendesk agent seats.
