Assign ticket to first agent who replies

It is very common to have a lot of agents responsible for the customer support inside a company. And with a lot of tickets coming in, it may be hard to specify which agent should be the responsible for each ticket manually. An alternative is to assign a ticket to whichever agent replies to it first automatically and this article will describe how to do it.

First of all, log into your Help Desk instance, and open the Settings page using the left navbar. Now, find the “Triggers” tab and click on that.


This is where we create actions to be done whenever a rule or an event is fulfilled. We’ll need to create a trigger for when a new comment is created. With this trigger we’ll set the comment creator to be the assignee of this ticket, but only if the ticket still has no assignee and the ticket wasn’t created for the requester either.

Let’s start creating the trigger by clicking on “new item” on the top.

New item

On the “New trigger” page, choose a name for your trigger and set it so it runs when a new comment is created.

New trigger page

Now, you should set up those conditions that we mentioned earlier. We want to affect only tickets with no assignee and we want to run this trigger only if the person who sent the comment isn’t the requester. That is easy with HelpDesk! First add the condition so the assignee e-mail of the ticket is empty. Make sure you put the empty ‘’ on the right.

First condition

Then add the condition so the comment didn’t come from the requester.

Second condition

You can even validate your conditions to make sure everything’s right.

Validate condition

Next thing is adding the action that will set the assignee properly. Add a new action pressing “add action”.

Set assignee

This will be a “Set field” action. Set it so HelpDesk will change the “Assigned To” field to {{Comment.From.Email}}. This way it will assign the ticket to the agent who replied to it.

Set field

And this is how you can automatically assign tickets to the first agent who replies to it. This can be done in both SharePoint Online and SharePoint 2013/2016/2019/SE.