How do you keep ticket ownership clear when requests come from everywhere?

[-]

Hairy-Marzipan6740@reddit

we landed on a pretty simple rule internally: people can ask wherever they want, but ownership only gets decided in one place. at ClearFeed, we use a dedicated Slack triage channel as that “one place.” anything that comes in (Slack channels/DMs, emails, etc.) becomes a request and shows up there, where you can set assignee, status, priority, and link it to Jira if it needs engineering follow through. the stuff that keeps it from turning into another messy inbox: * auto assignment on day one. either first responder grabs it automatically, or we round robin across a Slack group so there’s always a named owner quickly. * nudges beat dashboards. we rely on digests to surface what’s still open, plus personal DMs that remind each person what’s sitting with them. * follow ups are automated. if someone says they’ll get back and it’s still hanging, commitment reminders bring it back up without someone playing traffic cop. the only “process” we really push is: if it matters, drop it into the intake channel or forward it so it lands in triage. once people see that’s the fastest way to get something owned, they start doing it naturally. :)

Reply

[-]

FrameOver9095@reddit

Three things that actually work: 1. Train your team to say "no ticket, no work" period. Give them a canned response with the portal link. 2. Set up email-to-ticket automation so lazy users can still email but it creates proper ownership. 3. Use something like monday service that pulls requests from Slack/Teams automatically and assigns ownership

Reply

[-]

mattberan@reddit

Tell people why the ticket is valuable. If you can't communicate and convince them of that - then it's probably NOT.

Reply

[-]

Familiar_Network_108@reddit

so quick context we had this wild scatter of requests from slack to sticky notes in our last company sprint and it messed up our on call rotation bad, for us mondayservice helped us channel everything in one place assign owners and keep the noise down nobody fighting over who owns what you might wanna stick with one intake spot for sanity

Reply

[-]

4thehalibit@reddit

We Freshservice, when we foreward from email or teams it creates a ticket based on the from field. When they call I make them wait two minute while I start one or have them email support while I start looking into it. No ticket no worky.

Reply

[-]

ElBargainout@reddit

I see this constantly. You have a perfect dashboard in Jira or Zendesk, but the real work is happening in DMs and hallway conversations. The moment you "accept the chaos" is the moment you lose control of your SLAs. Here are three quick ways to force alignment without being the "ticket police": 1. **Slack Actions:** Set up a workflow where a specific emoji reaction (like a ticket emoji) automatically pushes that Slack message into your ticketing system. 2. **"No Ticket, No ID":** Configure an auto-reply for email/Slack channels that says "Request received. Your Ticket ID is X. Tracking won't start until this is generated." It trains users to look for the ID. 3. **Keyword Triage:** Use basic automation rules to scan for keywords like "urgent" or "access" and auto-assign them to a specific owner immediately, rather than letting them sit in a general inbox. I actually work on a tool called [AiLog](https://app.ailog.fr/fr/landing), that helps automate this "intake chaos." We build the layer that sits between your users and your ticketing system. We can ingest those Slack requests, check them against a Knowledge Base to see if we can solve it instantly with AI, and if not, route it to the right person with clear ownership. **I would love to help you map out a better flow:** I can offer a free 15 to 30 minute audit of your current intake channels. If it looks like a fit, we could run a 4 to 6 week pilot where we deploy a Slack Intake Bot for your team. * We seed it with your current documentation. * It deflects the easy questions automatically using your KB. * It formats the complex ones into proper tickets. We typically see a significant drop in "informal asks" and a clear improvement in time-to-assignment because the bot enforces the process for you. Let me know if you are open to a short chat to see how we can reduce the noise for your team.

Reply

[-]

lectos1977@reddit

Make a ticket from the outside communications and say "ticket from slack" and put the requester as who messaged or called you. Easy.

Reply

[-]

Uncl3J@reddit

If it's not a ticket, it's not real.

Reply

[-]

crankysysadmin@reddit

Our sysadmins have been trained to not work on anything that comes in via slack. They provide the person messaging them with a link to the ticketing system.

Reply

[-]

oddball667@reddit

Sounds like your team doesn't know how to make a ticket

Reply

[-]

ExceptionEX@reddit

Create a workflow that all things originate with the owner of the ticket putting a request into the system. The core of this is, one system for tickets, you can create many ways for a user to create a ticket, but none of them (outside of execs which will always be special case) should be with the IT personal creating the ticket for the user. People won't like it, people will always catch IT staff for help real quick, and that is fine, but the tech should know that once a ticket rises beyond a single time quick fix, to tell them "Hey I need you to open a ticket" and if that user gives the tech shit, the tech should tell their manager, and that manager should talk to that persons manager.

Reply

[-]

Eddit13@reddit

No ticky no worky. No. Heres the link to the system. here is the phone number to the helpdesk that can open a ticket for you. Love ya! Buh Bye

Reply

[-]

BoilingJD@reddit

use CRM as ticketing solution - users feel like they talking to a specific person, but all conversations are properly funnelled and assigned agains fake "projects" on the back end.

Reply

[-]

themastermonk@reddit

If it's not in a ticket it never happened. Everything starts and finishes in a ticket, you will get pushback at first, but the key piece is to get management buy-in that it allows for proper tracking of issues so that nothing gets lost in the cracks. Any attempts to open issues through other means should be met immediately with hey make a ticket for that.

Reply

[-]

AdeelAutomates@reddit

Its a cultural thing you need to shift: Ticketing System is the only system. No more slacks, no more teams, no emails, no hey buddy as they walk by, etc. Only time walk ups/phone calls are allowed is when accessing to a computer is not possible. Every request is submitted to helpdesk. T1s pick them up. Determine if they can resolve it or triage it. Before escalation/triage, helpdesk need to fill notes on what they discovered and what needs to be done. If they fail, escalations teams can/should return to T1 to make the add their notes more clearly. Only time calls/walk bys are allowed is if submitting a ticket is not possible (computer not working, etc). Then its the helpdesk who generates the ticket and fills out all the fields) That's really it. Get leadership to enforce this behaviour across the org. Get your techs to tell people to submit via the ticketing portal. And over time the culture will shift.

Reply

[-]

patmorgan235@reddit

Everything goes in the ticketing system, everything. Most ticking systems have email integrations so you just forward an email to create a ticket, many have IM/Teams/Slack integrations that make creating tickets from chats easy. No ticket no work.

Reply

[-]

shikkonin@reddit

Ignore everything not raised through a ticket. Assign tickets. Done.

Reply

[-]

Brainrants@reddit

And this needs to be communicated as policy by management and enforced as policy by the entire IT team, especially management. No calling the IT manager to skip the line of the ticket system. Phone calls are for “there’s smoke coming out of my PC” or “your team did a great job”. Everything else is a ticket.

Reply

[-]

Expensive_Plant_9530@reddit

And even with calls, if it’s urgent enough for a phone call, the technician answering the phone should be creating a ticket immediately on call for the person calling in. Everything, and I really do mean everything, should circle back to a ticket.

Reply

[-]

Snowywowy@reddit

Acknowledge the problem, but tell the user you will probably forget it by the time you reach your desk so they should also put in a ticket. And then never think about it again till there is a ticket.

Reply

[-]

magfoo@reddit

No ticket -> no problem

Reply

[-]

imadam71@reddit

Second this.

Reply

[-]

Expensive_Plant_9530@reddit

“Did you open a ticket?” Because if not, it’s not an issue. Your team needs to be firm about this. You need manager buy in. If someone calls? Open a ticket for them over the phone. If someone sends a slack message or an email, reply and tell them to open a ticket. This only works if your manager backs you up.

Reply

[-]

i8noodles@reddit

no formal ticket? no action. problem solved. the issue is you are allowing actions to be taken before a ticket is created. if a ticket is created, then actions occur that change ownerships, then it is easy to track. ticket, then actions.

Reply

[-]

ErrorID10T@reddit

Tickets should primarily come in through an email or channel, and immediately be turned into a ticket if it's not already. Workflows can do some of the work, the rest is just training your team to create the ticket with all of the relevant information.

Reply

[-]

accidentlife@reddit

I work for an MSP. We have a dedicated dispatcher whose job it is to assign tickets to resources. Any method for creating a ticket (email, phone, etc) leads to the dispatcher. The dispatcher can then take the opportunity to ask follow up questions, get any necessary scheduling info, and assign the ticket to the right person based on skills and availability. ___ The other thing is to make sure your service meets your customer’s needs, even if they are just “internal” customers. Try and have Level 1 techs be available immediately to handle simple issues. People are much more patient when they know their issue was worked on immediately(even if they are waiting for an L2/3). It also helps that by doing this, most of your issues get resolved within 15 minutes, which gives you trust when issues take longer to resolve.

Reply

[-]

OneSeaworthiness7768@reddit

Why would you not have a single intake path for support tickets? The service desk serve as triage and escalate when appropriate.

Reply

[-]

kubrador@reddit

enforce a single intake path or watch your team become a bunch of cats herding themselves. we made slack autopost to tickets with a required field for priority/category, took three weeks of people complaining, then suddenly everyone stopped treating their manager's text as a production incident. the dashboard thing is a symptom not a solution. if tickets slip off it, your system isn't trusted. ours improved when we made ticket status the only source of truth and stopped answering "where is this" questions any other way. bit brutal but it works.

Reply

[-]

rickAUS@reddit

I work at a MSP and our clients are told there's 2 ways to log a ticket: 1\\ email our support@ address 2\\ call if it's urgent, but preferably after you've already done #1 so you can give us a ticket number which saves us from making one during the call which is time better spent working on your urgent issue If I worked for internal IT I'd run the same system. support@ mailbox that gets monitored by a ticket system. Same amount of effort to email the support@ address as it would be to email someone from the IT team directly or send them a teams/slack/whatever message. And if you need a certain ticket to go to a certain person because they're already working on it in some capacity, or have worked on it in the past then address it as such. Anything else isn't a ticket, has no SLA and people will get to it when they're able or remember it exists.

Reply

[-]

stuartsmiles01@reddit

Ask is there a ticket yet and ask them for one. If something is in teams, and still needs a ticket, or on call about it, put some notes in a ticket and create a ticket there and then, as part of conversation, then at least there is a ticket, ( so you can put what has happened in it and capture the information at the time, put screenshots in & not forget / move on.

Reply

[-]

Akamiso29@reddit

Yup. If you have a ticket system: “Oh wow, yeah that sounds like you’d need some help. Have you put in a ticket yet? Give me the number and I’ll make sure it’s being worked on. :)”or some similarly disarming friendly language based on your company’s culture. Remember: Purchasing would never buy something without a purchasing request. Accounting would never pay an invoice without an invoice number. Why are you expected to do work not brought up through the right way?

Reply

[-]

anomalous_cowherd@reddit

This works, you get grumbles but it works. Especially when they see that doing it with a ticket gets much better results than without. You do need to make sure that when they raise it as a ticket then it gets dealt with in a timely manner - but if you can't do that you have a different prioritisation or resourcing issue to deal with anyway.

Reply

[-]

TrippTrappTrinn@reddit

St enterprise level. All tickets start al L1. Any issue raised outside of ticketing are best effort and is not part of SLA.

Reply

[-]

DowntownSquare528@reddit

slack is great for quick asks but terrible as a source of truth. Ownership gets messy fast. tTools like Siit that turn slack requests into real tickets with clear tracking can remove a lot of friction without adding overhead.

Reply

[-]

Hobbit_Hardcase@reddit

Automated ticket creation should be able to assign it to the sender. It can take some time getting workflows right, but it's worth doing. For manual creation, you need to get the Helldesk to fill out the information properly. Which ticket system are you using?

Reply

[-]

Massive_Ad9659@reddit

The tricky part isn’t the volume, it’s lost context. One thing that worked for us was linking requests to a central tracking system as soon as they’re mentioned, even if they start in chat or email. That way everyone knows who’s responsible and nothing gets forgotten, without forcing extra manual steps.

Reply

How do you keep ticket ownership clear when requests come from everywhere?

Reply to Post

36 Comments

Hairy-Marzipan6740@reddit

FrameOver9095@reddit

mattberan@reddit

Familiar_Network_108@reddit

4thehalibit@reddit

ElBargainout@reddit

lectos1977@reddit

Uncl3J@reddit

crankysysadmin@reddit

oddball667@reddit

ExceptionEX@reddit

Eddit13@reddit

BoilingJD@reddit

themastermonk@reddit

AdeelAutomates@reddit

patmorgan235@reddit

shikkonin@reddit

Brainrants@reddit

Expensive_Plant_9530@reddit

Snowywowy@reddit

magfoo@reddit

imadam71@reddit

Expensive_Plant_9530@reddit

i8noodles@reddit

ErrorID10T@reddit

accidentlife@reddit

OneSeaworthiness7768@reddit

kubrador@reddit

rickAUS@reddit

stuartsmiles01@reddit

Akamiso29@reddit

anomalous_cowherd@reddit

TrippTrappTrinn@reddit

DowntownSquare528@reddit

Hobbit_Hardcase@reddit

Massive_Ad9659@reddit