August 20, 2019

Highlights (7.2)

  • Who sent what?

  • Change to survey links to improve SMS deliverability

  • Tabs added to the advanced configuration page

  • New enrollment logic action: Mark participant as declined or unenrolled

  • Survey and conversation form display updates

Platform-Wide Updates

Who sent what?

The SMS inbox will now show which of your team members sent which messages. You will be able to see who sent messages manually and which messages are system generated.

Change to survey links to improve deliverability

We sent a prior email informing you that some wireless providers have begun blocking text messages with survey links from W2H. We discovered that changing the formatting of survey links from the shortened version to the long version can increase deliverability, so we’ve implemented that as an option on variable configuration. If your project is experiencing deliverability issues due to carrier violations, contact your implementation lead to update the build with long survey links.

 

Tabs added to advanced configuration page

Vertical tabs have been added to the advanced configuration page under Manage Study>Settings. This page has A LOT of setting configuration sections on it, so we added some tabs to make navigating this page a little easier.

 

New enrollment logic action: Mark participant as declined or unenrolled

During enrollment, you can now set up an automated action to mark a participant as declined or unenrolled. Previously you could only mark participants as ineligible so this gives you more flexibility with tracking enrollment drop-off.

Survey and conversation form display updates

Check out our survey and conversation editors! We updated the forms with new colors and drop down menus.

Study Specific

Hey PUSH! We added access groups to the transactions report in W2H to make your payment reconciliation a little easier!

Behind the Scenes

  • Updates to our survey tool through an upgrade of surveyjs

  • We updated emails sent during enrollment (including contact verification)to come from the study's email instead of the W2H email.

  • Store Variable Params in variable history ledger

  • We are prepping the code in the background for custom incident types