Highlights (7.0)
Personalized Setting for Default Tab in Participant Profile
⭐ NEW⭐ Participant Messaging
Text Message Conversations
Conversation Branching Logic
Keyword Responses
Business Hours, Nights and Weekends Scheduling
Variables in Conversations
Platform-Wide Updates
This new feature can’t be overlooked…
...
When you navigate into a participant’s profile, you automatically land on the participant’s general info page. This page is a good overview of some participant information, but isn’t likely used often in the day-to-day management of your participants. So we decided to put the option in your hands, you can now choose which tab will default to open when navigating to a participant’s profile! For example, If you are mostly monitoring a participant’s inbox, you can choose the sms inbox tab to be your default. This means, every time you navigate to a participant’s profile, that will be the tab that opens!
How can you utilize this feature? Go to your profile settings by logging into W2H and clicking your name in the top right corner. Here you can choose your default tab in the participant profile!
...
Okay, on to the SUPER cool stuff…
...
You will be able to schedule these structured conversations OR you can trigger a conversation based on a participant texting in a certain keyword. How do triggers work? Well, say a participant texts in “I am in pain” and pain is the keyword you determined, the conversation you created will then trigger asking the participant about their pain.
Another addition to message scheduling is the ability to easily set your business, nights and weekend hours study wide. With this new feature your responses to participants can be different depending on your business hours schedule.
Variables will also be available in your text conversations, making it easy to personalize the messages for your participants!
Check out our user guide by clicking here to learn more!
...
Behind the Scenes
Use 'display' answer in data/survey variables rather than coded value
Post failures of individual worker jobs to sentry
Race Conditions for events
Backend behavior for standard (non-conversation) response actions