{"id":18827,"date":"2023-06-06T14:56:41","date_gmt":"2023-06-06T14:56:41","guid":{"rendered":"https:\/\/vigneshkarthik.website\/helpdesk\/docs\/automations\/configuring-workflow-rules\/auto-assign-to-agent-who-responds-to-ticket-ticket-updation\/"},"modified":"2026-03-17T20:46:05","modified_gmt":"2026-03-17T20:46:05","slug":"auto-assign-to-agent-who-responds-to-ticket-ticket-updation","status":"publish","type":"docs","link":"https:\/\/help.desk365.io\/en\/articles\/auto-assign-to-agent-who-responds-to-ticket-during-ticket-updation\/","title":{"rendered":"Auto assign to agent who responds to ticket using ticket updates"},"content":{"rendered":"\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\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

One of the key challenges faced by helpdesk teams is ensuring that tickets are promptly assigned to the <\/span>appropriate <\/span>agents<\/span>. However, manually assigning tickets can be time-consuming and prone to human error. This is where automation rules come into play. <\/span><\/p>

In this<\/span> help center article<\/span>, we will explore a specific automation rule that helps streamline ticket assignment by automatically assigning tickets to agents who respond to them.<\/span><\/p>\t\t\t\t\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

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

Automation Rule: Agent responded - ticket assignment<\/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

The automation rule we will discuss focuses on the scenario where a ticket has not yet been assigned to any agent, but an agent has responded to it. By configuring this rule, you can ensure that such tickets are automatically assigned to the agent who provided the response.<\/p>

Here are the steps to configure this automation rule in Desk365<\/a><\/span>.<\/p>\t\t\t\t\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

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

Accessing automation rules settings<\/h3>\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

Log in to your Desk365 account and go to the Settings > Productivity > Automation tab. From there, click on the \u2018Create New Rule\u2019 from the Ticket Updates tab.<\/p>\t\t\t\t\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

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"creating-new-automation-rule-ticket-updates-desk365\"\t\t\t\t\t\t\t\t\t\t\t\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
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t

Creating a new automation rule<\/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

Provide a name for the rule and enter the description if you have any in the box below.<\/p>\t\t\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\t\t\t\t\t\t\"automation-rule-to-auto-assign-tickets-desk365\"\t\t\t\t\t\t\t\t\t\t\t\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
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

Ticket updates<\/a><\/span> are commonly triggered when a ticket is being updated, and the action performed will vary based on the user who is performing the update. <\/span><\/span><\/p>

S<\/span>elect<\/span> \u2018Anyone in the system<\/span>\u2019<\/span>.<\/span> This <\/span>selection<\/span> will trigger the ticket update whenever the action is executed by any agent in the system.<\/span><\/span><\/p>\t\t\t\t\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

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

Event: Agent responded<\/h3>\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

Select the event that triggers this rule when an update occurs. The trigger for this automation rule is when an agent responds to a ticket. When this event occurs, the rule will evaluate the ticket’s properties to determine the next course of action.<\/p>\t\t\t\t\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

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"auto-assign-automation-rule-defining-event-desk365\t\t\t\t\t\t\t\t\t\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

On ticket properties that match: The ticket is not assigned to any agent<\/h3>\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

Choose the type of field you want from the dropdown list (ticket, accounts, or custom). The rule checks whether the ticket is unassigned, ensuring that it hasn’t been assigned to any agent yet. If this condition is met, the automation rule proceeds to the next step.<\/p>\t\t\t\t\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

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

Ticket assignment: Matching agent is assigned<\/h3>\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

Now, configure the actions to be executed on the ticket after the specified rule conditions have been met.<\/p>

Once the rule identifies an unassigned ticket, it automatically assigns the ticket to the agent who responded to it. This action ensures that the ticket is promptly routed to the agent responsible for addressing the customer’s query or issue.<\/p>

Select the desired action from the ‘Do Action’ dropdown menu.<\/p>\t\t\t\t\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

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"create-automation-rule-to-auto-assign-tickets\"\t\t\t\t\t\t\t\t\t\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

Once you have set up all the conditions and actions, click the ‘Save Automation’ button to create your automation rule.<\/span><\/span>\u00a0<\/span>
<\/span>\u00a0<\/span>
<\/span>By configuring the “Agent Responded – Ticket Assignment” rule, you can ensure that tickets without assigned agents are promptly assigned to the agents who respond to them. <\/span>By following these steps, you can ensure that your customers receive <\/span>timely<\/span> and personalized support from the most qualified agent.<\/span><\/span>\u00a0<\/span><\/span><\/p>\t\t\t\t\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","protected":false},"author":5,"featured_media":0,"parent":18821,"menu_order":8,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-18827","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\/18827","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\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/comments?post=18827"}],"version-history":[{"count":53,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18827\/revisions"}],"predecessor-version":[{"id":36094,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18827\/revisions\/36094"}],"up":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18821"}],"next":[{"title":"Using replied content placeholders in automation rules","link":"https:\/\/help.desk365.io\/en\/articles\/using-replied-content-placeholders-in-automation-rules\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/23707"}],"prev":[{"title":"Sending ticket data to third-party tools using 'Trigger Webhook' option","link":"https:\/\/help.desk365.io\/en\/articles\/sending-ticket-data-to-third-party-tools-using-trigger-webhook-option\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/21774"}],"wp:attachment":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/media?parent=18827"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/doc_tag?post=18827"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}