The /zendesk create_ticket command lets an agent open a Zendesk ticket from any Slack channel without having to react to an existing message or copy a conversation into Zendesk. It ships with the Slack for Zendesk Support app and works in every channel where the app is installed and authorized.
This guide walks through the command end to end: prerequisites, each form field, submission, and the limitations you should know before standardizing on it. If you need bidirectional sync, forms on Slack, attachments from threads, or ticket creation in personal DMs, ClearFeed's Slack + Zendesk integration covers those flows.
Prerequisites
- The Slack for Zendesk Support app is installed in your Slack workspace by a Zendesk admin.
- The channel where you want to run the command has been added to the app.
- The person running the command has a Zendesk agent seat and matching identity in Slack.
Step #1: Initiate Ticket Creation
In any channel where the Zendesk Support app is active, type /zendesk create_ticket and press Enter. Slack opens a Create new ticket modal.
Step #2: Fill Out the Ticket Form
The modal exposes four fields. Only Subject and Description are required.
Subject
A short, specific summary of the request. This is the title agents see in the Zendesk queue, so lead with the customer or problem rather than a generic label.
Requester
Defaults to the Slack user submitting the ticket and is editable. Clicking the field opens a searchable list of Slack users. If the selected user does not exist in Zendesk, the app creates a new Zendesk Support end-user tied to the ticket. Agents filing on behalf of someone else can pick that person from the list or create a new end-user inline.
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. Everything typed here is visible to anyone permitted to view the ticket in Zendesk. Attachments and prior thread context cannot be added from this modal.
Step #3: Submit the Ticket
Click Submit. The Zendesk app creates the ticket in Zendesk Support and posts a confirmation message with the ticket link back to the same Slack channel.
Limitations of the /zendesk create_ticket command
The native command is designed for one-off ticket creation, not full support workflows. Teams that lean on it heavily typically hit the following gaps:
- No thread context. The command creates a standalone ticket; it doesn't pull the Slack thread's messages, attachments, or reactions into the ticket description.
- No bidirectional sync. Replies posted on the Zendesk ticket aren't mirrored to the Slack thread, and Slack replies aren't synced back to 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 personal-DM ticketing. The command runs in channels where the Zendesk app has been added; it does not create tickets from direct messages.
- No status updates in Slack. Once submitted, the channel does not receive automatic notifications when the Zendesk ticket status changes.
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 two-way sync.
- Ticket creation from Slack threads. React with a 🎫 emoji, tag the ClearFeed bot, 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 custom statuses) post back to Slack.
- Custom forms on Slack. Import your 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.
- 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, private and DM ticketing, and reduced Zendesk agent seats.
