Carrot
-
Total activity18
-
Last activity
-
Member since
-
Following0 users
-
Followed by0 users
-
Votes2
-
Subscriptions6
Activity overview
Latest activity by Carrot-
Carrot created a post,
Setting a ticket to the agents default group when reassigned
Current Configuration: We have two triage groups. We'll call them Triage 1 and Triage 2. Some agents are in Triage 1, and some are in Triage 2, depending on the team they are on. We then have group...
-
Carrot commented,
Hi Ahmed, I was running this for the year. It did give me the data I needed so thank you for that.
-
Carrot commented,
This sort of works, but the output was a giant 50k line list of each agent and each requester. Then I added the average total to the very bottom. I was hoping for something cleaner.
-
Carrot created a post,
Reporting on same agent support
I'm looking to build a report that would show how often an agent is supporting the same member(continuity of care). For example Member 1 contacts support 10 times, of those 10 times how often did t...
-
Carrot commented,
This worked perfectly!
-
Carrot created a post,
Reporting on end-users with multiple requests of the same type
I'm working on a report that would allow us to show requesters with <= 4 tickets with the same request type. I've tried using IF ([Ticket tags]="ticket_type_1")<=4 THEN "Follow Up" ENDIF and IF ([f...
-
Carrot created a post,
End users with multiple tickets in buckets
I am looking to build a report that places all the active end-users who have created tickets into buckets of: __% of them have 1-10 tickets __% of them have 11-20 tickets __% of them have 21-30, et...
-
Carrot created a post,
Show all data even with a 0 value in all columns
Our goal is to show a solved ticket count per agent daily (columns = closed ticket count / % one touch / %two touch, rows = agent list). We want to show a full list of agents, even if an agent has ...
-
Carrot commented,
This was exactly what I needed. Thank you very much.
-
Carrot created a post,
Report on previous assignee of a ticket
We recently did an overhaul of our groups, during this update a decent amount of tickets were assigned to the wrong agent. Unfortunately, no one caught this error until after the weekend when most ...