Text Review Request

Role: Product Designer & Product Manager
Status: Available for New Accounts 

Role: Product Designer &
Product Manager

Status: Available for New Accounts 

Demandforce is an Automated Marketing Communications platform which helps small medium sized businesses send appointment reminders, marketing campaigns, and manage their online reputation.

Text Review Request gives businesses the ability to send their patients or customers a link to write an online review on their behalf. Text Review Request is one of many features aimed towards gathering text message consent from our Businesses’ customers/patients, yet also providing a greater control over a business's online reputation by being selective with whom to send a link to write an online review via text. 

Why did you do this project?

Why did you do
this project?

Demandforce’s review capture process still depends on solicitation via email, which is a crowded channel. Emails yield a 20-30% open rate while text messages have a 98% open rate.¹ Texting is becoming the dominant form of communication for consumers. However, there are potential legal issues with automated review solicitation by text, which limits how we could go about generating reviews by text. Demandforce does not have a method of capturing text consent from consumers.

 ¹ Velocify study, 2016

How did you do the project?

How did you do
the project?

Product Requirements Documentation

I worked with my manager, Greg Li, to create the Product Requirements Document which defined the problem, target customers, solution, success criteria, user flow, and rollout plan. I used Jesse James Garrett’s Vis Vocab to plan the user flow in order to give a high level explanation to stakeholders of how Text Review Request would work.

TRR Flow 2

Interaction Design

Interaction Design

I was responsible for the Interaction Design for this feature. This involved documenting the use cases, competitive research. I used Sketch and InVision to create low fidelity prototypes for user testing and high fidelity mocks and design specifications for developers.

I decided the best place for this feature would be in an existing feature called “Today’s Follow Up Actions”. Originally, this section showed patients who were scheduled to visit and had a missing phone number or email address. The front desk relied on this section to know which customers they need to follow up with for missing information. This information is crucial for Demandforce’s platform to send automated communications.

I also used this opportunity to improve the usability of Today’s Follow Up Actions.

Before

Before

After

After

Collapsable Preview

Collapsing the sections only helped save vertical space but hid any important information. Users had no visibility of what was contained within. 

Now, when Today’s Follow Up Actions is collapsed, a preview of 3 customers will be shown according to the relative time. For example, if it is 12pm, the 3 closest patients within 15 minutes will be shown.

Sortable Headers

This section is originally sorted chronologically. However, one limitation of Demandforce’s platform is that we only know the beginning times of appointments. Giving users the ability to sort by Patient name gives users the flexibility to best search for a patient.

Pagination

Sections on the Dashboard had no vertical limitation and would extend the vertical scroll of the page. Since Text Review Request would apply to any patient coming into the practice, it would increase the density of information Today’s Follow Up Actions already had. Instead of just using a standard pagination, I included an input field to allow for quick access and accommodate a large number of pages since every patient/customer in a day would appear in this section. #fuckdropdowns

Sections on the Dashboard had no vertical limitation, and would extend the vertical scroll of the page. Since Text Review Request would apply to any patient coming into
the practice, it would increase the density of information Today’s Follow Up Actions already had. Instead of just using a standard pagination, I included an input field to allow for quick access and accomodate a large number of pages since every patient/customer in a day would appear
in this section.

Pagination2

User Testing

User Testing

I worked with our UX Researcher, Sean Tangco, to conduct user testing on usertesting.com and user interviews with current Demandforce customers. Sean helped analyze our findings into recommendations to improve the flow and functionality of Text Review Request.

"Iterate, Test, and Repeat"
Consent Iterations

"How would Text Review
Request work?"

Wireframes helped me explore the functionality of what was originally called "Quick Text Review", a.k.a. Text Review Request. In order for Text Review Request to work, we needed our business users to ask their patients/customers for the text message consent and capture their responses. I received feedback from internal team members and stakeholders before conducting user testing.

Wireframes

"Teach users how to
ask for consent"

"Teach Users How to Ask for Consent"

One of the key feedback I received from the wireframes is users will not know how to ask their patients /customers for text message consent. Text Review Request is a new feature which requires the user to complete a verbal task as part of completing the flow. I included a script and tested a more conversational interface and flow.

Prompt

"Are you asking me?
Or am I asking them?"

"Are you asking me?
Or am I asking them?"

When users saw the prompt in the previous iteration, many didn't understand whether Demandforce was stating the prompt to them or if it was a script for them to read aloud to their patient/customer. This third group of iterations focused on making the act of reading the script as part of the Text Review Request flow clearer. I used graphics and iconography to demonstrate what we were asking our users to do.

Conversational

Design Specification

Once we had a final prototype, I worked with our Visual Designer, Youngsun You, to create high fidelity design specifications in preparation for development. I worked with Youngsun to ensure the iconography and placement of copy and buttons was cohesive with our current product UI. After, I documented the various interactions for developers using Google Docs and InVision Inspect. I wrote out the Acceptance Criteria and worked with QA engineers to create test cases. 

Feature Release

I presented our final specifications for review with our CTO and Project Managers. As the product manager, I was the product expert of how Text Review Request would work. I worked with developers and QA engineers to explain and check feature functionality. I also worked with Marketing, Training, and Client Success teams prepare the necessary communications and training needed to ensure a smooth feature release.

Rollout

What did you learn?

What did you learn?

“Sometimes an Extra Click, Helps the Feature 'Click' ”

What we found from our user testing is how reducing the number of steps and clicks is not always the best UX. Functionally, our initial prototype only had 2 steps. The first screen had a prompt for our users to read to their customers. Below the prompt, we had a phone number input with a button that said "Customer Consents".

User Testing 2

What we found is that users often ignored the prompt and they would go directly the to response input. While our users understood Text Review Request would send a text message to their customers/patients, they did not understand that the “Customer Consents” CTA was capturing their customer’s consent to receive text messages.

User Testing 1

In our final version, we separated the "Customer Consents" function into a second step. Users are first presented with the prompt if the customer had not consented to text messages yet. If the customer agreed to consent, the front desk employee could advance to the second screen and submit their customer's consent and phone number. Afterwards, a confirmation screen appears to give our front desk employee feedback that they've completed the Text Review Request flow. 

Users felt they completed the task with the final version. The additional step of "What did they say?" helped users understand they were capturing their patient/customer's response.

“Copy is part of the User Experience”

We don’t have a dedicated UX writer on our team, so I reached out to our Marketing and Customer Support teams to review the product copy. Writing about the importance of TCPA compliance can be very intimidating, so we focused on how asking for text message consent is important for our businesses. Reviewing the feedback we received from our internal teams and user testing helped lead to our final solution.

“Walk-Ins are not Welcome”

Text Review Request worked for our businesses who depend on previously scheduled appointments. However, for businesses in Auto, Spa/Salon, and Animal Care businesses who have many walk-in appointments, Text Review Request does not work. This was an intentional decision due to legal compliance issues.

The appointment data Demandforce synced from a business’s Patient Management System allowed us to assume the patient/customer was in business’s office. There was no feasible manner for us to prevent a user from entering phone numbers manually to trigger a Text Review Request. One way we prevent this is with a double opt-in process where the owner of the phone number has to reply back to an initial text to confirm their opt-in. Status Notifications is another feature we have created for businesses who depend on walk-ins instead of pre-scheduled appointments.

What were the challenges?

Growing Pains of a Changing Product

The core value of Demandforce for our businesses is service of automation we provide. Our average user logs into Demandforce once a day, with an average session lasting 5 minutes. That being said, Text Review Request is not an automated feature. It requires the user to interact with Demandforce to manually trigger a text message to be sent to their customer. However, once we have text consent from a majority of our consumers receiving text messages, we can automate Text Review Request.

Growing Pains of a
Changing Product

The core value of Demandforce for our businesses is service of automation we provide. Our average user logs into Demandforce once a day, with an average session lasting 5 minutes. That being said, Text Review Request is not an automated feature. It requires the user to interact with Demandforce to manually trigger a text message to be sent to their customer. However, once we have text consent from a majority of our consumers receiving text messages, we can automate Text Review Request.

Legal Compliance

How can we convince our users to log into the portal more often? How can we convince businesses to take an active part in achieving legal compliance? Why is this feature not automated?

Without written consent from customers/patients, Demandforce is unable to send automated reminders and maintain the level of automation our businesses have grown to love. Which is why it was important that Text Review Request provided value and incentive for our customers to stay logged into the portal and help take an active part in achieving legal compliance. 

Asking manually bypasses any legal concerns about sending out automated marketing messages over text, but still allows a relatively low-friction way for businesses to start collecting reviews and to build a list of consumers who have opted-in to text messaging. Once our businesses have a comprehensive list of consumers who've opted-in to text messaging, Demandforce can explore automating Text Review Requests. 

Get in touch

Get in touch

Send me questions, comments, and concerns via email.
Podcast and music recommendations are welcomed as well. 

Reach out if you’d like to talk about a project, ask me a question, or have feedback. If you have any music or podcasts recommendations, feel free
to send them as well. 

Send me questions, comments, and concerns via email. Podcast and music recommendations are welcomed as well.