A marketplace app product improvement

Driving increased bookings for Solv urgent care partners

Timeline
Q2 2023
Status
Live
Team
Product designer (myself), product manager, engineer
Problem
35% of unique clinic page views land on one of Solv’s non-partner clinic pages. This represents a significant portion of traffic not effectively being directed towards partner clinic pages.
Solution
Boost visibility of nearby partner clinics on non-partner clinic pages to more effectively redirect traffic and drive increased booking rates and therefore ROI for partner clinics.
Outcome
10x improvement in the number of bookings created and 35% booking conversion lift compared to the previous non-partner clinic page designs. Contributing within one quarter to a 15% increase in partners meeting Solv’s ideal ROI of <$25 cost per booking.

background

Solv Connect, urgent care’s patient acquisition solution
Solv Connect is Solv’s marketing and patient acquisition solution for urgent care clinics. Our team’s objective focuses on maximizing the value our urgent care partners receive from their listings on Solv’s marketplace.

Project overview

Problem
According to Solv’s internal data gathered from Mixpanel reports, 35% of Solv’s consumers land on a non-partner clinic details page as opposed to a Solv-partner clinic details page (internally referred to as “CDP”), while searching for nearby urgent care appointments.

This is significant because these clinics are not affiliated with Solv, therefore we do not have insight into their scheduling software making their pages appear as un-bookable to consumers.

This creates a negative experience for consumers who are eager to find care and are instead faced with a non-bookable option. As well as results in a missed opportunity for effectively funneling potential patients towards Solv’s bookable partners.
Solution
Identify opportunities across the non-partner clinic pages to boost visibility of nearby partner clinics and redirect traffic towards those clinics.
Objective
Our overall objective was to increase ROI for our Solv Connect partners. One of Solv’s 2023 OKR’s was to reach 60% of Solv Connect partners meeting an average monthly ROI of <$25 cost per booking. At the end of Q1 2023, before the project kickoff, we were pacing at 41%. This project initiative aims to boost that percentage by redirecting patient traffic to increase partner booking rates and therefore ROI.
Outcome
In the first 30 days after release, we saw a
10x improvement in the number of bookings created and 35% booking conversion lift compared to the previous non-partner clinic page designs. Contributing within one quarter to a 15% increase towards our OKR goal of partners meeting Solv’s ideal ROI of <$25 cost per booking.

process

User personas
Due to the nature of Solv as a two-sided marketplace, with any changes to our consumer-facing product we must be conscious of potential impacts to personas on both the consumer and supply sides. These objectives would serve as a backdrop to many of the design decisions made.
How will changes impact our Mary personas looking for care?
  • Ensure Mary’s are seeing bookable care options as often as possible.
How will the changes impact business to our current urgent care partners?
  • Ensure that paying partners are seeing a positive return on their investment.
How will it impact conversations with future prospective partners?
  • Incentivize buy-in by communicating the value of becoming a Solv partner.
Mary
Mother, urgent care consumer
Goals
  • Eager to find reliable, quality care for her sick child ASAP
Solv’s role
  • Go-to resource to find same-day, next-day urgent care appointments
Chris
Urgent care CEO/Owner, decision maker
Goals
  • Looking to acquire and retain patients
  • Maximizing profitability
Solv’s role
  • Drive new patients and patient loyalty (Solv Connect marketplace product)
  • Optimize clinic operations and workflow efficiency (Solv Experience software product)
Identifying opportunities within the user flow
Using Mixpanel data, I mapped out the landscape surrounding the non-partner clinic details page (CDP) experience, capturing common entry-points and available user actions. Each of the downstream actions provided an opportunity to funnel traffic towards bookable Connect partners. I highlighted potential design intervention opportunities to help inform where to begin ideation. (see diagram below)
Competitor Analysis
I wanted to dig into what solutions other two-sided marketplaces employed for their partner vs. non-partner pages. Among others, a few examples I analyzed included Zocdoc (one of Solv’s main competitors), OpenTable, and DoorDash. Here were some of the common themes:
A means to continue their search
Zocdoc’s non-partner provider page had a search bar within the header to promote their search experience. Partner provider pages did not have a search bar to keep the focus on booking with that partner. OpenTable utilized a sticky footer with a “Find similar restaurants” CTA on non-partner pages.
“Notify me” or “Request” CTA
OpenTable and DoorDash both had some version of a “Notify me” CTA so customers could receive a notification if that business became available on the platform. I found this idea interesting as it could also measure high-interest engagement with these non-partner businesses and could be used in sales pitches.
Various levels of assertiveness
Zocdoc’s non-partner provider page had a search bar within the header to promote their search experience. Partner provider pages did not have a search bar to keep the focus on booking with that partner. OpenTable utilized a sticky footer with a “Find similar restaurants” CTA on non-partner pages.
Ideation
During the ideation phase, I wanted to explore several diverging approaches; all informed by the main question: How might we funnel Mary’s who land on non-partner CDP’s to bookable partner clinics? Several design critiques, product reviews, and reviews with marketing and SEO team members helped to converge on a design direction. Below are some of the concepts I proposed and the feedback received.
Exploration 1:
"Notify Me" CTA
Rationale
  • Serves a purpose to users who may be loyal to this clinic location, aligning with Solv’s motivation to promote patient loyalty
  • Captures user interest in a location, can be used by sales team as a selling point
Feedback
  • Team likes this idea and the opportunity to function as selling point for sales
  • Concerns that the added CTA may ultimately distract from overall goal of booking at partner locations
Exploration 2:
Search bar
Rationale
  • Universal search bar funnels users away from non-partner page to search results page
  • Indicates to Mary’s who may be unfamiliar with Solv that she can continue her care-seeking journey here
  • Pre-populated search fields allow Mary to get to results with just one click
Feedback
  • Emphasizing search experience introduces additional steps before booking completion, leading to more drop-off opportunities
  • May be a higher engineering lift given our timeline
Exploration 3:
"Nearby clinics" module
Rationale
  • Display up to two alternative locations with instant-book timeslots, indicates clinic availability, immediately initiates booking flow
  • Option A displays results as close to the top of the page as possible
  • Option B aligns with existing patterns
Feedback
  • Likes immediate visibility of timeslots
  • Concerns that Option A may be bad for SEO, conflicting with Google’s experience guidelines
  • Concerns that Option B may not be visible enough, users may not scroll that far
Exploration 4:
"Nearby clinics" popup
Rationale
  • More aggressive approach
  • Would need to be cautious this is not classified as an “intrusive interstitial” by Google
  • Option A: popup with timed trigger
  • Option B: requires manual action to expand
Feedback
  • Likes Option A, more aggressive approach may help us reach OKR faster
  • Could be used in tandem with in-line modal
  • Requires testing for Mary’s coming from outside Solv (ie: Google) to ensure it won’t negatively impact SEO
A/B/C testing mobile designs
Collaborating with the product manager and engineer, we set up an A/B/C test to inform which mobile design to move forward with. Specifically, we were monitoring potential impacts on SEO performance, click-through rates, and conversion rates of each option.

We anticipated option A to have the least negative SEO impact but potentially lower performance due to its page placement. Options B and C were used to test two different popup triggers. B activated the popup upon a content-switching event, when a user scrolled upward after having scrolled down on the page. While C employed a time-based trigger, activating the popup 5 seconds after the page load.

30 days post-release of the A/B/C test, the data revealed that the popups had a 55% conversion lift compared to the in-line design. And of the two popups, the time-based trigger outperformed the scroll-based trigger by about 15%. Consequently, we decided to proceed with option C.

solutions

post-launch

Impact
In the first thirty days of rollout:
  • The redesigned “Nearby clinics” booking module’s click-through-rate outperformed the old module’s by almost ten-fold (see '1' in the figure below)
  • ~35% booking conversion lift and 10x the number of bookings created (see '2' in the figure below)
  • Project helped boost Solv’s OKR of Connect partners meeting an average monthly ROI of <$25 cost per booking from 41% to 56% in Q1 2023, pacing towards our overall 2023 goal of 60%
Takeaways
Ultimately, it was exciting to see such tangible results and be able to trace OKR improvements back to this project effort. However, beyond just business impact, these design changes helped 10x more patients find the care they needed.

Moving forward, I’d love to be able to identify more design opportunities such as these to help move the needle with our OKR’s. Some of the other design explorations done during ideation left a lot more room for further discovery. I’d be curious to validate if it may be worth following up with any of those designs in the future.