'Send a Conditional Message' Event

What is a 'Send a Conditional Message' event? 

An event that looks at previous events for completion and/or compliance and then runs logic and sends a message to a select recipient based on the defined logic. 

  All of the logic functionality for 'Send a Conditional Message' event can also be done using 'Add Logic' event types.  Use whichever event is more intuitive to you when configuring participant messaging! 

What are the 'Send a Conditional Message' use cases? 

1. Send a participant a survey reminder
2. Send a message to a participant based on a previous device upload (weight, steps, etc.)
3. Send alerts to study staff or support partners 
4. Look at a previous survey response and send a tailored tip based on the response (formerly known as 'Survey Lookback') 

How do I set up an 'Send a Conditional Message' event? 

1. Typically, you should build the event that the 'Send a Conditional Message' event is going to look at prior to building the 'Send a Conditional Message'. 
   1. Example 1: if you want to send a message based on step count from the previous day, first build the 'Fitbit daily steps' event.  
   2. Example 2: if you want to send a reminder to a participant to complete their midpoint survey, first build the 'Midpoint survey' event.
      
      
2. From the Manage Study drop-down, select 'Study Arms'. Then select 'Manage Event Schedule' for the arm where you want to add the 'Send a Conditional Message' event. 
   
   
   
   
3. Click the blue '+ New event' button and select 'Send a Conditional Message' type.
   
   
   
   
4. Name the event.
   
   
   
5. Indicate when the event should begin and any repeats. 
   1.  You can choose for the event to begin:
      1. Immediately at participant start 
      2. Same day as participant starts
      3. After participant start (day 7)
      4. After participant start by day of the week (2nd Monday) 
      5. 
   1. See typical windows and repeats in the examples below!
      
      
6. Click the blue 'Define Logic' button to set up the logic criteria for the messaging. 
   
   
   
   
7. Determine the event that the 'Send a Conditional Message' event logic should look at.
   1.  Tips: 
      1. Want to send a survey reminder? Choose 'previous event's completion and/or compliance'
      2. Want to send a message if the participant met their goal the previous day?  Choose 'previous event's completion and/or compliance'
      3. Want to send a message based on a participant's previous answer to a survey question? Choose 'participant's survey answer'
      4. Want to send a message about a participant's weekly point balance? Choose 'Achievement'
      5. Want to send an alert to project staff about participant non-adherence?  Choose 'previous event's completion and/or compliance'
      

'Send a Conditional Message' Use Case Examples:

Example 1: Send a message based on step count from the previous day

1. First, build the 'Daily steps' event that the 'Send a Conditional Message'  is going to look at. Build any logic into the Daily Steps event.  (See Typical 'Collect Data' Event for more details!)
   1. For this example, the participant will be marked as compliant if they walked over 7,000 steps that day. 
      
      
      
      
2. Now we are ready to build our 'Send a Conditional Message' event! (See adding new event above)
   1.  Tip! For a 'Send a Conditional Message' event that sends daily messages, there are a couple of points to keep in mind
      1. Generally, the event begins 1 day after the event that it's looking at. So here, the 'daily steps' event begins on Day 0, the 'Send a Conditional Message' event should start on Day 1. 
      2. For daily messaging, we usually recommend scheduling it for 11 am
      3. Daily logic should repeat for the length of the intervention.  
         
         
         
         
3. Once you define the new 'Send a Conditional Message', you are ready to build the messaging logic! In this example, we want to send a participant a message for 2 scenarios:
   1. They met the goal of 7000 steps the previous day
   2. They didn't meet the goal of 7000 steps the previous day 
      
      
4. Click the 'Define Logic' button.  Once on the logic page, select 'Specify Condition'.
   
   
   
   
5. Select 'Previous Event's Compliance' and the Daily Step Count' event for the 'Send a Message Event' to look at.  Then enter the event criteria. For message 1 (they met the goal), enter the following: 
   
   
   
   
6. 'Send Message' will already display for the 'Then' criteria.  Select the recipient and type the notification into the message box, including any variables listed below and the notification preference. 
   1. This will allow you to send the message only to those who met the goal of 7000 steps the previous day. 
      
      
      
      
   2.  Tip! Want to tell participants the goal that they should have reached?? You can set up Custom Variables! This will tailor the message for each participant!
      
      
      
      
7. For those who didn't meet the goal of 7,000 steps, you want to send a different message.  Set this up as an 'Otherwise' criteria. 
   
   
   
   
8.  Tip! Want to send a different message for those who did not send any step count data? 
   1. Set up a new Logic Set.  
   2. Select 'Previous event's completion' and the 'Daily Step Count' 
   3. Leave the 'Then' consequence blank and set up message as an 'Otherwise' consequence. 
      
      

Example 2: Send a survey reminder

1.  First, build the 'Midpoint Study Survey' event that the 'Send a Message Event' is going to look at. Build any logic into the survey event.  (See Survey event for more details!)
   
   
   
   
2. Now we are ready to build our 'Send a Conditional Message' event! (See adding new event above) 
   1.  Tip! For a ''Send a Conditional Message' event that sends survey reminders, there are a couple of points to keep in mind
      1. Start sending the reminders a few days after the survey opens.  In this example, the survey opens on Day 15 so the reminders start on Day 17. 
      2. Set up repeats on the event- either daily or weekly.  
         
         
3. Once you add your new 'Send a Conditional Message' event, you are ready to build logic! Click 'Define Logic'. For survey reminders, we only want to send a participant a message if the DID NOT complete the End of Study Survey.
   
   
4. Once on the new page, select 'Previous Event's Completion'.
   
   
   
   
5. Select 'Midpoint Study Survey' for the 'Send a Conditional Message' event logic to look at.  And enter the following completion criteria. 
   1.  Be sure to change the event logic to look at open events as the survey event is still open!!
      
      
      
      
6.  IMPORTANT: For the next step, be sure to leave the 'Then' criteria blank.  Instead select 'Add a consequence' to the 'Otherwise' criteria, and select 'Message'
   1. Why? We only want to send the reminder to those who did not complete the survey, not those who did.  With this set up, once a participant completes the survey, they will stop receiving reminders.
      
      
      
7. Click the 'Save logic' button. 

Example 3: Send a non-adherence alert to a participant's support partner (could also be set up for study staff)

1. First, build the 'Daily medication' event that the 'Send a Conditional Message' is going to look at. Build any logic into the Daily Steps event.  (See Typical 'Collect Data' Event for more details!)
   
   
   
   
   
2. Now we are ready to build our 'Send a Conditional Message' event! (See adding new event above)  
   1.  Tip! For a 'Send a Conditional Message' that sends non-adherence alerts, there are a couple of points to keep in mind.
      
      1. Think about when you want to start sending notifications to the partner.  They are usually scheduled to start a few days after the device event starts and they repeat daily.
         
          
3. Once you define the criteria for your new 'Send a Conditional Message' event, you are ready to build the messaging logic! 
   
   
4. Click the blue 'Define Logic' button.  Once the logic page loads, select 'Previous event's completion' and select 'Daily Step Count' for the messaging logic to look at.
   
   
5. Decide how often you want to send notifications to the partner by choosing how many of the last 'daily medication' events the reminder should look at and how many the participant had to miss. 
   1. Example: If the participant synced 1 of their last 2 days, then don't send an alert to the partner, otherwise send the alert.  This means that the participant missed syncing both of their last 2 days. 
      
      
      
      
6. Leave the 'Then' criteria blank as you only want to send the partner alert to participants who haven't synced at least once in the last 2 days. 
   
   
7. Select 'Message' for the 'Otherwise' criteria.  Type the notification into the message box, including any variables listed below and the notification preference. 
   
   
   
   
8. Click the 'Save Logic' button. 

Example: 4: Send a tailored tip based on a response to a previous survey

1. Once you define the scheduling, you are ready to build the 'Send a Conditional Message' event! (See adding new event above). Click the 'Define Logic' button. 
   
   
   
   
2.  Click the 'Select condition' drop down and 'Participant's previous survey answer'. 
   
   
   
   
3. Select the survey. 
   
   
4. Select the appropriate question for the tailored tip. 
   
   
   
   
   
5. Select the answer choice that will trigger the tip. 
   
   
   
   
6. Set up the tailored tip message that you want to send all participants who said 'yes' to having high cholesterol. 
   
   
   
   
7. Click the blue 'Save Logic' button. 
   
   
8. Your newly added tailored tip event will now display in the Overview schedule page! 
   
   
   
   
9.  Tip! You can also use this same feature to send a group of participants information about where to go for a study weigh in

   Example: If a participant indicated in their screening survey that they work at HUP, then send them a message with weigh-in location details. Participants who work at CHOP can be sent a message with a different weigh-in location.