{"id":21073,"date":"2023-08-24T13:56:11","date_gmt":"2023-08-24T13:56:11","guid":{"rendered":"https:\/\/help.kanidesk.com\/en\/docs\/admin-guide\/designing-ticket-forms-and-fields\/understanding-ticket-statuses-in-desk365\/"},"modified":"2026-03-16T11:10:30","modified_gmt":"2026-03-16T11:10:30","slug":"understanding-ticket-statuses-in-desk365","status":"publish","type":"docs","link":"https:\/\/help.desk365.io\/en\/articles\/understanding-ticket-statuses-in-desk365\/","title":{"rendered":"Understanding ticket statuses in Desk365"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t
\n Available with:<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Standard<\/span>\n <\/span>\n \n |<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Plus<\/span>\n <\/span>\n \n |<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Premium<\/span>\n <\/span>\n<\/div>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

A support ticket will go through multiple teams and support agents during its lifecycle. Each of the teams and agents working on the ticket perform multiple operations on the ticket, from replying to the customer to adding additional notes and updating ticket properties, before assigning the ticket to another agent.<\/p>

Given that this ticket might go through many agents and teams, it\u2019s important to have a property that accurately captures the stage of the lifecycle that the ticket is in.<\/p>

In Desk365, ticket statuses are a vital component for efficiently managing support operations. They help track the journey of a ticket from creation to resolution.<\/p>

By default, tickets can have one of four statuses: Open, Pending, Resolved, or Closed. Additionally, Desk365 allows you to create custom ticket statuses<\/a> tailored to your specific requirements.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t

What are the default ticket statuses in Desk365?<\/h2>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

By default, every ticket in Desk365<\/a> is in one of the 4 statuses:<\/p>

Open – <\/strong>This is the default status of a ticket when a ticket is created in Desk365 helpdesk. These are tickets that your support team should start working on. Whenever a customer replies to a ticket that has a resolved status, it always moves back to open so that you can take a look at it again and fix any issues, if necessary.\u00a0<\/p>

Pending<\/strong> – An agent can set the status of the ticket as “Pending” when he\/she has replied to a ticket and is waiting to get more information from the customer. Sometimes, the agent might need additional information or might need some more time to work on the issue, fix, and confirm the solution for it. It can also be used with tickets that are on hold because of any third-party vendor’s dependencies that are not in control of the support agents.<\/p>

Resolved<\/strong> – When your agents are pretty confident that they have provided the right solution to a customer, they mark the ticket status as “Resolved.” Once the customer confirms that the issue has been fixed, the agent can update the ticket status as “Closed”.<\/p>

Closed<\/strong> – An agent marks the ticket status as “Closed” when a customer confirms that the issue has been resolved completely. However, even if the ticket has been marked as closed, it will move back into the open status if the customer replies to the same ticket again.<\/p>

Note<\/em>: Default ticket statuses cannot be deleted but can be renamed for contacts if needed.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"author":13,"featured_media":0,"parent":20969,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-21073","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21073","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/comments?post=21073"}],"version-history":[{"count":60,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21073\/revisions"}],"predecessor-version":[{"id":35776,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21073\/revisions\/35776"}],"up":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/20969"}],"next":[{"title":"Customizing ticket statuses in your Desk365 helpdesk","link":"https:\/\/help.desk365.io\/en\/articles\/customizing-ticket-statuses-in-your-desk365-helpdesk\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/24375"}],"wp:attachment":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/media?parent=21073"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/doc_tag?post=21073"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}