Configure a dynamic object for an MC number & Fraud Detect

@andersen Here is what I have, Ill let you know how it plays out!
 

@andersen  Im assuming that a contact thats added to a list wouldnt trigger the rule again? Even in a new conversation?  

Hey @bbay good question - I’m not entirely sure what rules you have set up on your side but I imagine you’ve got a rule in place that will quarantine flagged emails based on the information pulled in from Highway.

 

If you’ve independently verified the contact is not suspicious and should not be quarantined in the future, you can think about adding a rule condition to check a contact list of these ‘internally verified contacts’. Something like:

This will require you to maintain your own contact list, which shouldn’t be too difficult to do. You can easily add a contact to a contact list via the Contact Details plugin on the right hand side of the app. If you want to go the full automation route, you could consider creating a rule where you automatically add a contact to a contact list when you move a conversation out of the quarantine inbox.

This should be enough for you to get started but let me know if you have any additional questions!

 

That’s correct @bbay. The idea here is to create that ‘trusted’ list so all subsequent conversation from ‘trusted’ contacts wouldn’t be moved to the quarantine inbox and can remain in whatever inbox the email was sent to.

Great thank you for the confirmation. I added the rule suggestion this past; Friday. I’ll take a look Monday and see if there were enough rule executions to ensure it’s working correctly. 

@andersen The contact list method doesnt seem to be working. I created the lists as shared. Would that be the issue? Does it need to be a private list? 

Do you mean the contact isn’t getting added to the contact list or that contacts that are added to the ‘trusted’ list are still being moved to the quarantine inbox?

Can you share the rule you’ve created to quarantine conversations? @bbay 

@andersen  I apologize, I was crossed up, so many rules going! HAHA I think we’re good there. I was thinking that I could add any trusted contact and that would also stop the email detector. With the volume that comes across it makes the inboxes a bit noisey. It would be nice for the Dynamic object to only create if one of my conditions we’re true, which then fires off the Quaretine rule we have. 

Very fair comment @bbay ! It’s something I know the product team is exploring - giving users more granular control over when a dynamic object is created - so thank you for sharing your feedback. FYI @robby_p 

Good news: it turns out that you don’t have to create a separate dynamic object for every single text pattern variation that you’re seeing for MC Numbers. That said, I recommend leveraging the solution demoed within the first 4 minutes and 30 seconds of the hyperlinked video below. This solution has a huge advantage — it will not only work when just 1 MC Number appears in an email subject and/or body, but also when many different MC Numbers appear in either the subject line and/or body of an inbound email. And since you’ve already built one Dynamic Object for the mc use case (MC[Digits]), you’ll only have to build 2 more 😎 I’d recommend building those out and you can then delete the smart rule that we walked through on 1/5/24.

With 3 Dynamic Objects you can capture 6 text pattern variations

After watching the video: to reiterate, the downside of using a solution that involves leveraging 2 smart rules is that it’ll only work if you’re just dealing with 1 specific MC Number being referenced in the subject line and/or body of an inbound email. If multiple MC Numbers are listed in an inbound email, it will not trigger a Dynamic Object to be created for all of those numbers because of a limitation. (For Example, if MC#1234, MC#1236 are in the body of an inbound email, a dynamic object will only be triggered for MC#1234.) 

For that reason, I recommend creating at least 3 separate dynamic objects as the solution.

@steve_b  Thanks for the quick solution, and video walk through to boot. Took me some time, but I fiollowe your video, and made two other dyanmic variables. I went ahead and updated my rules (just in case), but turned them off.  Ill let you know if i see any issues! Let me know if you come up with anything else that may be useful! 

 @steve_b wanted me see if you had any ideas on the below. Our inboxes have become very noisy with the fraud detect we’re looking for a solution that only creates the object if there is a fraud or spoof or possibly be able to mark domains as safe, in turn not triggering a the dynamic object. 
 

@andersen  I apologize, I was crossed up, so many rules going! HAHA I think we’re good there. I was thinking that I could add any trusted contact and that would also stop the email detector. With the volume that comes across it makes the inboxes a bit noisey. It would be nice for the Dynamic object to only create if one of my conditions we’re true, which then fires off the Quaretine rule we have.