Activating custom ticket statuses

Return to top

52 Comments

  • Aran Liu

    Hi Dane, we also need to differentiate between Solved and Closed tickets. Just tagging you to make sure I'm in the loop. Can you keep me updated on this?

    Also, I think having different ticket statuses for different groups of agents is a good idea.

    0
  • Scott Burnham

    So this would be great, but as it replaces the search bar with: sort:desc custom_status_id:4242552 custom_status_id:4242572
    Instead of actual human identifiable words, it's a big N O P E for us. 

    1
  • Ashley

    is it possible to make the status move to draw more attention to it, for example I want ticket stus NEW to shake or bounce 

    0
  • bill cicchetti

    Scott Burnham:  Where are you seeing the custom statuses showing as the field ids?

    1
  • bill cicchetti

    Can you confirm whether these custom statuses still  can't be used in Explore to determine the duration a ticket has been in this particular custom state?

    0
  • Timothy Bogart

    I don't see yet anywhere the caveat that once you have implemented Custom Ticket Statuses, you lose views based on them when you create a sandbox.  It seems that support thinks this should be obvious because Agent Workspaces are NOT turned on by default in a sandbox so that when I opened a ticket on this I was sent here.

    Strikes me that having to recreate views manually is an oversight.

    -1
  • Timothy Bogart

    ?

    1
  • Philippe B.

    Hi!

    We loved the idea, but since it is not possible to restrict to specific groups within our organization, it is sadly 100% useless.

     

    We would love the possibility to :

    - Assign custom statuses to specific groups only.

    - Customize the colors of statuses

     

    Would it be a near future possibility, or should we not expect further improvement?

    2
  • Andrea Rijna

    Does anyone know how to include custom statuses in automations and triggers?

    Only the main statuses are visible. But we want to build automations for different on hold statuses we built, to make sure we have a different approach per status.

    0
  • Timothy Bogart

    Should look for a Ticket status - not Status Category.

     

    3
  • Hess

    I like the idea of these, but we won't be implementing them for now. The biggest thing I am missing is the ability to customise form conditions based on these custom statuses. 

    We currently do this manually with a "stage" drop-down field, that we then map triggers & form conditions to.

    0
  • Alexan

    i have just activated CTS and I noticed that once a ticket is closed, there's no longer the option to "create followup ticket" like we had prior to activating CTS. 

    I get that Closed tickets now is shown as "Solved" in the View bucket with a new icon shown, however we have now lost ability to followup on a closed ticket when needed. 
    Was this intended or am I missing a setting when I activated CTS?

    0
  • Alexan

    Adding on to the above, perhaps it may be a cache issue.
    1. i activated CTS yesterday and this morning, i noticed all my closed tickets did not show the option for creating a followup ticket.

    2. somehow, when i was chatting with your support, I refreshed the page again, and voila, the followup option appeared




    0
  • Thomas Lang

    Being able to set the color for statuses would be cool. Any plans for this?

     

    0
  • Andrea Rijna

    Thanks Timothy, this solved it for me!

    0
  • Timothy Bogart

    Splendid!

    0
  • Dan R.
    Community Moderator

    This feature is a big step forward, but is not possible to use for us because we cannot tie a status to a form or group. Different teams have different functions and thus different status requirements. Expecting agents to sort through a list of statuses irrelevant to their task is asking for input errors. Additionally if workflow rules require a certain status to be applied, we don't want to see them kicked off accidentally if a user selects a status not relevant to their ticket type. 

     

     

    0
  • Gaurav Parbat
    Zendesk Product Manager

    Hey Dan,

    Thank for your input. We are working on an enhancement Workflow based statuses that restrict these ticket statuses to specific forms/groups. 
    For all, if you can share your use cases in this survey, it will help us expedite this enhancement. 
    Form link 

    Thanks,

    Gaurav Parbat

    2
  • Dan R.
    Community Moderator

    Thanks Gaurav Parbat for coming back and sharing that update! I've submitted my responses to the form, excited to see what improvements the future holds.

    0
  • Alexan

    since enabling CTS, we wanted to automate ticket status whenever a customer replies on the ticket (email/messenger/social media)

    I tried with this condition to set ticket status = OPEN , however, we noticed when we initiate the ticket (sending an email out), after some time, the ticket automatically changes to OPEN without any customer response. 

    Any idea how we can achieve to set a CTS condition where the ticket changes to OPEN once we get an update from customer (not internal user)

    0
  • Yiota Michalopoulou

    Hello Colleen Hall Dane

    my question (which I think has already been made) is about being able to apply custom ticket statuses to a certain team/group with the same organisation. 

    We have several teams under our organisation but we want to be able to apply the custom ticket statuses and their respective automations just to one group. 

    Is this something you have in planning? 

    If so, is there an ETA?

    Thank you in advance, 

    Yiota

    0
  • Jani Oksanen

    I'm giving my vote also to make custom statuses for different groups. I can't use the custom status now as it would be shown for all agents which I do not prefer.

    0

Please sign in to leave a comment.

Powered by Zendesk