Recent searches
No recent searches
How do you exclude a "received at" email from an auto responder?
Posted Mar 03, 2022
Hi All.
I am having some trouble excluding an email address from receiving an auto-responder email. I have included some images below of the current rules that exist for our auto responder message.
Context: The emails included in the "Meet ANY of the following conditions" all have the same domain. The email that we are attempting to exclude is not included in that list and is onboarding@samedomain.com.
Ideally, in the "must meet ALL of the following conditions" section, I would want to be able to set a rule that says " Received at IS NOT onboarding@samedomain.com, but that is not possible.
Ask: What rules do I need to create to achieve this same result?
Any support is appreciated.
Best,
Haley W
1
6 comments
Dan Ross
Hey Haley,
I feel your pain at the lack of an IS NOT operator. Come to this thread and add your voice to the those asking for this feature!
As for the solution today, in this case, I'd create a trigger that runs before this one you're designing.
In that trigger:
Under ALL, Ticket is Created
Under the ANY section, put each received at email you want to exclude from the workflow
for the ACTION, add a tag that you can use for auto-responder exclusion (ex: tag1)
In the trigger you're building now in your post, you just need to add a condition under ALL for
Tags do not contain 'tag1'
Hope that helps!
2
Jacob the Moderator
Hi Haley,
Great question!
Triggers run sequentially, so you can take advantage of this by having a trigger above the one that sends out the auto-response, this new trigger should target the tickets you don't want to send a notification and prevent that.
For example, you could have a new trigger have the conditions:
and its action be:
Now, you can add an ALL condition to your existing trigger:
This way your tickets coming in on "onboarding@samedomain.com" will have been tagged so they no longer meet the conditions in your notifying trigger.
Best practise is to order and group your triggers by what action they perform, generally speaking in:
Notifications are the last actions you would want to perform.
Hope that helps.
2
Haley W.
Jacob the Moderator Dan Ross Thank you both so so so much! This worked wonderfully. I appreciate the step by step guide that you both provided.
Have great days! :D
1
Sanchez, Santiago
Hi,
I know this post is old, but I'm running into the same issue with wanting to exclude a few addresses from getting the auto-reply. This idea seems like a winner, and I'm almost there. I'm running into a problem with the ticket received at portion.
The values it's pulling from are our support addresses. One of the addresses I want to exclude is an MS address, the other, one of our partners. I'm unsure if adding them to the support addresses is the way to go.
Hopefully, there is another place I can pull those values from.
Thanks,
Santiago
0
Sanchez, Santiago
I think I answered some of the question. Instead of received at is there a condition that is just an email address. So I've switched it to “Requester”, but it's pulling from our list of techs.
0
Jacob the Moderator
Hi Santiago,
If you read my earlier comment, it should guide you in how to prevent notifications from going out. Basically, you want to make sure that the notification trigger is prevented from running under some circumstances -there is no received at is not condition, but you can use a contains none of the following tags condition instead, and have a trigger above your notification trigger set it for the tickets that are received at those addresses you want to exclude.
The requester field is for conditions where someone from your team is the ticket requester, and will not help with targeting support addresses.
I hope this helps.
0