@amhernandezccisd Thank you for submitting your question to our community! 
Just to clarify, their assigned location is different from the requested location and you are trying to catch tickets where this they do not match?
Do you have a custom field asking for the location within the existing tickets?
No, their Location and Requested for Location are the ones that match. I apologize for not including the headings. So in the picture from my original post, the first column is Location, second column is Location Details, and the last column is Requested for with their name and assigned location.
Normally, their Location and Requested for match. It’s the Location Details, they put the actual location they are at, because they’ve noticed their location is not correct. At times, they put it in the description and that I’m just going to have to watch like a hawk.
No, we do not have a custom field within a majority of the tickets. We do have a custom field for tickets that don’t generally need for anyone to go out. Hope this makes sense. Let me know if you need any more information.
@amhernandezccisd Thank you for clarifying. Best practice would be for the agent to adjust the ticket location upon ticket creation since it will default to their assigned location.
One way to catch these tickets would be to add a custom field. This custom field could ask something like “Did you confirm the location of the ticket matches the location you are serving at?” with the selected answer of “yes” & “no.” This would be one way to making sure the agent when submitting the ticket is double checking that location.
