CRO Test: Thank You Page

TLDR: Redesigning a thank you page to focus on next steps produced better leads, and in turn, more revenue.

Results: 15% increase in referred leads


A Place For Mom is the largest assisted living referral service. The heart of their process is getting help from a local advisor who helps families find the best option for them. Most of the communication involved takes place over the phone. Two big challenges they face are getting users to submit their phone number in a lead form, and then getting them to answer the phone when the call comes. For this test, I decided to focus on the second challenge.

Original Thank You Page


I started by having a conversation with a colleague who specializes in the post-lead experience (everything that happens after a user fills out a form). I asked a lot of questions about how the process works and what kind of success rates we have for each step. One thing I was interested to learn was that the number of users who answered the initial phone call was surprisingly low, so I started drilling into possible explanations. I found out that the timeframe between a user submitting a lead and receiving a call was less than a minute.

I thought about my own mother, and how she never answers the phone on the first call, because she never keeps her phone on her. And I speculated that a fair amount of people might not associate the ringing phone with the form they just filled out on their computer. So I decided to test preparing users to receive a call on our thank you page.

At the time, the current thank you page treatment did explain the next steps of the process and what to expect. However, there was a lot of information being presented, and it was a lot to digest. Additionally, the thank you page didn't make it clear to the user that they were going to receive a phone call right away. I hypothesized that by simplifying the thank you page and focusing on the fact that users were about to receive a call any moment, we could increase the number of people answering the call.

Early Sketches


If we educate users about the process and prepare them to receive a phone call right away, we can increase LSTF by 10%.

Left: Control, Right: Variation


My main goals in designing this solution were to simplify the content on the thank you page and draw attention to the most important next step: receiving a call.

I started by de-emphasizing the benefits section at the bottom of the page, opting for a simple bulleted list view, as opposed to a full width horizontal section with icons.

I used color to de-emphasize the completed step and emphasize the current step. I used an animated icon to draw attention to the current step, since that's the most important task at hand. I included the phone number submitted in the messaging for a more personalized experience.

I changed the main headline of the page from a generic "thank you" message to a one sentence instruction to not close the window or navigate away from the page. I also changed the main call to action on the page from "View My Listings", which took them away from that page, to a request to receive another call, in the event they missed the first call.

Finally, I made the thank you message a full page design, as opposed to the previous modal version, to make the whole thing a bit clearer and remove visual distraction and the inherent desire most users have to close a modal without reading it.

Variation Thank You Page


One challenge in this project was development. I was still getting my feet under me in terms of my jQuery and JavaScript skills, and some of the things I had designed, such as displaying the user's phone number, were a bit tricky to accomplish. Fortunately, I had experienced teammates and Google at my disposal, and I didn't spend a lot of time spinning my wheels.

Another challenge was a mental one: it was hard for me to build something that wasn't meant to be a permanent solution. It felt hacky and jury rigged: basically throw away code. Honestly, this is something I still struggle with a bit. But at the end of the day, I have to remind myself that testing is a rapid, iterative process. The goal isn't to make a polished product, it's to prove a concept. If it works, we turn it over to developers who can turn it into a more permanent solution. My job isn't to build, it's to test.