Damon Timm

+1 for this!  

Our use case is a "snooze" function for on-hold tickets — not being able to clear the original date when the automation runs (or via a trigger) is kind of a shocker.  I thought I was doing something wrong until I found this thread.

Many email providers support "plus addressing" or "subaddressing".

For example: our receiving email address of `support@example.com` can also receive messages at `support+foo@example.com` and `support+bar@example.com`.  

Our organization has used this feature for many years to filter incoming messages (especially those from automated sources we interact with).

We are requesting a feature where we can leverage the subaddress information when creating trigger conditions.  Currently, the `Ticket -> Received at` condition does not allow us to specify a subaddress.  This conditional field could be updated to allow users to type in a subaddress (based on the registered domains) or a new conditional field could be created.

Thank you