Our organization relies heavily on Slack for IT support, but a recent audit showed that more than 90% of conversations involving agents never result in a ticket—over 1,000 missing tickets per quarter. We need a reliable way to change that behavior and preserve an audit trail, especially since message retention is limited.
We're considering converting the help channel into a structured intake workflow where users complete a form, and the submission sends an HTTP POST request to our ticketing system. Another possibility is allowing agents to create tickets directly from messages. Has anyone implemented a similar process? I'd appreciate advice on workflow design, integrations, user training, and changing the culture around informal support requests.
4 Answers
You may need to treat this primarily as a process and culture problem. Send users back to the helpdesk portal, communicate that direct messages and chat requests might not be worked, and make the official intake path obvious. A channel that only posts ticket confirmations can still be useful, but it shouldn’t replace the ticketing system.
Given the volume and the limited message-retention period, restricting who can post and replacing free-form requests with a form is a reasonable transition step. It creates a paper trail without requiring everyone to abandon chat immediately.
The simplest policy is still “no ticket, no work.” Slack is useful for quick communication, but it shouldn’t become the system of record for support requests. Make it clear that issues need to be submitted through the official helpdesk, and reinforce that agents shouldn’t receive performance credit for resolving work that has no documented ticket.
Look for an existing integration before building a custom app. Many ticketing systems can create tickets from Slack, and automation platforms can connect a form or webhook to your service desk. A lightweight option is to let agents add a specific emoji to a message when it needs to become a ticket, then use the events API or an automation workflow to create one.
That should be paired with training for both users and agents. If people are rewarded for helping in chat without recording the request, the informal process will continue.
A structured request channel can work well. Restrict posting outside threads, have a workflow open an intake form, and use the submission to populate the ticket fields through the service desk API. Post a confirmation in the channel and give the requester a link to the ticket or thread for follow-up.
For less structured conversations, integrations with tools such as Jira or Azure DevOps often let a technician select a message and choose something like “create ticket.” That’s easier for users who won’t adapt to a form, although the resulting tickets may need more cleanup.
Our current tool requires users to type a slash command. I’m considering a small app that makes the API request, but I’m hoping there’s a maintained integration or automation connector that avoids having to build everything ourselves.