Recent searches
No recent searches

Michael Ciraco
Joined Feb 06, 2023
·
Last activity Feb 06, 2023
Following
0
Follower
1
Total activity
2
Votes
0
Subscription
1
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Michael Ciraco
Michael Ciraco commented,
Features we need to be able to implement this. We are a LARGE enterprise, and have been waiting for this flexibility for many years and appreciate the movement forward, but it has gaps preventing reasonable implementation.
- custom ticket statuses must be able to be tied to forms, roles, groups, and or custom field we use called "brand field" so custom statuses only appear on certain forms or based on this custom field. Preferable all of the above. Having users have to select from a list as long as we would use to eliminate more than 100+ automations and triggers that use custom tags to simulate what we were missing to this point is not viable.
- triggers and automations that can use "less or equal" like functions on status checks within a status category. Better yet, let us rearrange all statuses to our desire in a priority order.
- remove the requirement for use of agent workspace. Though we'd like to get there, our org is so complex this would take substantial effort and retraining of thousands of staff and adjustments to countless integrations.
- allow us to set an icon and ticket color unique to each status. even if it was just 3 characters it would be sufficient.
- return the status of closed, preserving the last status of solved as indicated above, or, allow custom solved statuses we can use automations to set specifically.
View comment · Posted Feb 06, 2023 · Michael Ciraco
0
Followers
20
Votes
0
Comments