Our organization relies heavily on Slack for IT support, but an audit showed that more than 90% of conversations where agents helped users never resulted in a ticket—over 1,000 missing tickets per quarter. The support channel has more than 2,000 members, and messages are retained for only 90 days, so undocumented work and historical context are being lost. We are considering restricting the channel so users can submit a structured form, then sending the form data to our ticketing system through an HTTP POST or API workflow. What approaches have worked for turning Slack requests into tickets while also changing user and agent behavior?
5 Answers
The biggest issue sounds cultural rather than technical. Send a clear company-wide message that users must submit requests through the help desk instead of privately contacting IT, and make sure managers reinforce it. Since the support channel already became the default entry point, converting it into a form-based intake channel and removing general posting permissions is a reasonable middle ground. It preserves the familiar place to ask for help while ensuring every request creates a durable record.
The basic rule should still be “no ticket, no work.” Slack is convenient, but it is not a reliable system of record. Users and technicians need to understand that resolving an issue only counts when the request and resolution are documented in the ticketing system.
You can also use a webhook to announce newly created tickets in a Slack channel, giving technicians visibility without making Slack the source of truth. Keep the ticketing portal as the official record, and make the Slack workflow create the ticket immediately rather than relying on agents to remember afterward.
A structured intake channel can work well. Restrict posting outside threads, have a workflow open a form, and use the submission to populate the ticket through the service desk API. Post a confirmation in the channel and give the requester a link to the ticket or thread so they have a receipt. I would avoid trying to synchronize every Slack message with ticket work notes, since that usually becomes difficult to maintain.
Check whether your ticketing platform already has a Slack integration, or use an automation service such as Power Automate, Zapier, or another iPaaS tool. A custom Slack app using the Events API is another option. One lightweight workflow is to have agents add a specific emoji to a message when it needs to become a ticket, which triggers ticket creation. Automation alone probably will not fix the problem, though—you will also need training, clear expectations, and accountability for agents who resolve work without creating a record.
If a full form changes user behavior too abruptly, integrations for systems such as Jira or Azure DevOps can let technicians create a ticket directly from an existing Slack message. It is less structured, but it may be a useful transition for teams accustomed to free-form requests.