Skip to main content

Had an interesting bit of learning today: I submitted a ticket on behalf of a colleague, and the agent posted a comment/question and flipped the “Mark as ‘Waiting on requestor’” button. The ticket languished … and when I was scrolling through IIQ stuff, I saw that IIQ was awaiting a response from me, rather than the person on whose behalf I submitted the ticket.

 

If I were an AA submitting a ticket on behalf of my principal, this behavior might make sense: principal can’t always be expected to deal with ticket stuff. But a peer (me for my colleague, or a media specialist doing first-tier support before escalating to a ticket and IT support), I’d expect the nudge/flag to be for the customer.

 

I’m curious as to what guidance/clarity people are using around this schism right now, and I wonder whether IIQ might evaluate either some UX change to accommodate these two workflows … or, to be honest, my request: flip to focusing on the customer rather than the requestor, or at least make that a toggle in the site settings.

Our agents are instructed to make sure they move the ticket to the name of the actual Requestor (and often leaven the original person as a follower). Of course human error happens so this isn’t a perfect solution. Not sure how else it could be done though?


Thank you for your post, @EstonMelton. Incident IQ does this to allow the agent who submitted the ticket to be notified in case the user the ticket was submitted on behalf of is unable to access the site. For example, if a teacher is creating a ticket on behalf of a student or a user who does not have district access to the site, etc. Your UX change and/or site setting suggestion would be a good addition to our idea exchange. https://community.incidentiq.com/ideas

In the meantime, @bclark is correct. The best option if you do not want to see the 'Waiting for you to Respond' message is to edit the requestor once the ticket is created and remove yourself as the ticket submitter.


We do the same as @bclark and instruct our agents to remove themselves from the “on behalf of” and set the end user as the requestor as well.


Reply