Automation Rules Examples

Table of Contents:

Use-case: Let's say you have an offering, where your customers can change their package level from your website. At that point you might want to send them a Transactional message confirming the package change. Here's how to implement that with any change in a list field value.

1. Rule Settings

   1. Rule Trigger: assuming this is for existing customers, you'll choose the 'Contact created or edited' option as this will be an edit.

   2. Rule Frequency: Always – as you want to send this every time a customer changes their package level.

   3. Trigger Source: Choose API call update from your Website, or from Ongage platform, in the case of manual update by customer service personnel.
      
      

2. Rule Criteria: choose the field which contains the value, and select either 'Changed To' 'any value' or 'Changed From' 'any value'.

   Open

   

   
   
   

3. Rule Action: Choose Transactional

   1. You'll typically want to check: 'Check Contact Status' (i.e., don't send to inactive: unsubscribed/hard bounced/complained) and 'Check Suppression' (i.e., check against relevant suppression lists).

 Note: Another (and somewhat more versatile) way to set such a welcome drip campaign is using our Events & Triggers (see there: 'How to Setup a Welcome Onboarding Series').

This example will send 3 emails after a contact has been created at an interval of 5 mins, 1 day and 2 days after Created Date (aka sign-up date).

1. Rule Settings

   1. Rule Trigger: select: Contact create.

   2. Rule Frequency: select: Once.

   3. Trigger Source: Currently the API call and Ongage Platform (manual add) option is available for this scenario.

2. Rule Criteria: No rule criteria needs to be selected here for setting up Drip welcome series for every contact being added into the list.

3. Rule Action: Create 3 Transactional Actions and select Delay Send as demonstrated below:

   1. Transactional Action 1 with 5 minutes Delay.

   2. Transactional Action 2 with 24 hours Delay.

   3. Transactional Action 3 with 48 hours Delay.

In order to send confirmation unsubscribe SMS Text Message, please follow the steps given below. 

1. Rule Settings

   1. Rule Trigger: select: Contact Unsubscribed

   2. Rule Frequency: select: Always

2. Rule Criteria: In ESP Select: Sinch or twilio- as this feature currently only works for those SMS vendors.
   

   
   
   

3. Rule Action:  Set up Transactional Action with an SMS type message, which will send a confirmation SMS to those contacts who unsubscribed.

Ongage has a built-in welcome message as detailed in List Settings. That setting only allows for sending a welcome message via one SMTP/SMS vendor connection. If you'd like to send your welcome messages for a given segment via a different vendor connection, here's how you can do that.

1. Rule Settings

   1. Rule Trigger: select: Contact create.

   2. Rule Frequency: select: Once.

   3. Trigger Source: Currently the API call and Ongage Platform (manual add) option is available for this scenario.
      
      

2. Rule Criteria: choose a criteria for those that you want to send via a specific vendor connection, let's say 'gmail.com'.

   Open

   

   
   
   

3. Rule Action: choose Transactional and select the desired connection

   Open

   

Notes:

1. You can use this method to implement your welcome messages instead of the built-in one in Ongage which only allows sending via one vendor.

2. You can use this in conjunction with the built-in welcome message function, if you're using there the segmented welcome, make sure not to double target the segment you're also setting up here.

To openers (or clickers) in one connection, send a follow-up transactional message via a second connection

 This setup can be used for warming up a new IP and/or Sending Domain.

The basic idea here is, that to all those who opened or clicked (i.e., engaged) on one connection (e.g., the original welcome or event/campaign connection), send them a follow-up message via a new connection. Thus the new connection will only get recently engaged contacts – which is ideal for warm-ups!

You can set that follow-up message to be sent immediately, or after x minutes, x hours, or even a day later, the choice is yours! Some marketers like to do it immediately while the recipient is already in their mailbox, others prefer to send it later on in the day, or the following day, as not to overload contacts with messages.

Automation Rule configuration to send a follow up message via a separate connection 

1. Rule Settings

   1. Rule Trigger: select: Contact opened a message.

   2. Rule Frequency: select: Once per campaign.

      Open

      

      
      
      

2. Rule Criteria

   1. Go to Behaviour Event.

   2. Select ESP Connection.

   3. Select Connection ID from which you want to capture the Opens.

      Open

      

      
      
      

3. Rule Action

   1. Choose Transactional.

   2. Select Email Message.

   3. Select Transactional Campaign ID.

   4. Select ESP Connection ID:  This will be a separate connection which you want to warm up OR improve engagement for.

   5. Add Delay (Optional).