The default trigger Notify requester of received request sends a confirmation email to the ticket requester for each ticket received. This trigger applies to all tickets created, so requesters receive the same message regardless of whether they submitted the ticket directly or an agent created a ticket on their behalf.
If you want to send a different message for tickets created by an agent on behalf of the requester, this guide will help you do that.
This tip contains the following sections:
Modifying the original trigger
The first step in creating this workflow is editing the default trigger, Notify requester of received request, so it only fires when the requester creates a ticket. To do this follow the steps below:
- Click the Admin icon (
) in the sidebar, then select Business Rules > Triggers. - Locate the Notify requester of received request trigger and click its title to open the edit page.
- Under Meet ALL of the following conditions add Requester > is > (current user).
Note: The condition Requester > is > (current user) prevents the default trigger from firing when an agent creates a ticket on behalf of someone else. - Click Save.
Creating a new trigger
Next, you'll need to clone the trigger you just updated.
- Hover your mouse over the Notify requester of received request trigger and select Clone from the context menu on the right-hand side.
- Edit the title of the trigger to something else, like "Notify requester of created request".
- Edit the condition Requester > is > (current user) to Requester > is not > (current user). If you would like, you can remove the Status Is not Solved condition as well.
Note: The condition Requester > is not > (current user) causes the new trigger to fire only when an agent creates a ticket on behalf of someone else. - Edit the email body so the message is specific to tickets created on behalf of the requester, like in the example below.
Note: Remember to include a placeholder which displays ticket comments, like {{ticket.comments_formatted}} or {{ticket.latest_comment_formatted}}. - Click Create.
Results
Example of a response when the requester creates the ticket:
Example of a response when a ticket is created on behalf of the requester:
For more information about triggers, check out About triggers and how they work, Creating and managing triggers for ticket updates and notifications, and About the Support default triggers.
8 Comments
Can I exclude some end users from receiving the Notify requester of received request?
Hi Alice,
I guess you could probably exclude users with specific tags from receiving the notification?
Just add a tag (for example "no_acknowledgement") to the user account(s) which should be excluded from the notifications and then add this as a condition to the trigger:
Thanks for helping out, Katharina!
Note that if you are using something like ChannelReply to integrate with Amazon, you need to add a condition to not trigger when the ChannelReply-specific tags are present. Otherwise every incoming email will trigger this.
How would we set the ticket created trigger, if we only want requesters notified when we create tickets? As in we do not want them notified when they send tickets in, only when we create a ticket on their behalf. Also how would set the trigger so the body of it reflects what is in the actual ticket?
Hi Mary! Welcome to the Community!
All you'll need to do here is add a condition to the trigger:
Current user > is not > (end user)
This will make it so the trigger only fires when someone other than an end user creates the ticket.
This article did not work for me. My end users still get the same email notification even if my agents create request on their behalf.
In step 4 of "Creating a new trigger", please add a note to also edit the email subject as well, and not just the body. You're doing it in the example image, but you don't write about it =)
Please sign in to leave a comment.