RentSpreeProduct design · MVP launched · 2022

Agent Reviews

Helping new agents build credibility through client feedback.

New agents needed evidence of their experience to build credibility. I turned a researcher’s direction into the UX and UI for RentSpree’s first review feature, and proposed a shareable recommendation link so agents could collect feedback beyond rental applications. Both paths launched in the MVP.

Team: Research led by my UX researcher colleague. I owned UX and UI, working with the UX lead and stakeholders on the MVP.

Role
Product Designer · UX & UI
Company
RentSpree
Timeline
About 2 months
Scope
Desktop & mobile
RentSpree agent profile showing ratings, compliments, and client reviews
The shipped experience brought client feedback onto the Agent Profile. UI shown with sample content.

From a credibility problem to a review experience

My researcher colleague identified reviews as a way to help new agents establish credibility. My design task was to turn that direction into a usable collection, management, and publishing experience within the first release.

Research direction · My colleague

  • Led the research and synthesis on new-agent credibility.
  • Established reviews as a direction for the feature.

UX & UI design · My contribution

  • Compared existing review experiences.
  • Designed user flows, wireframes, and desktop and mobile UI.
  • Proposed the shareable recommendation link.
Original research synthesis connecting new-agent barriers to networking, reviews, case studies, and professional presentation.
Research by my UX researcher colleague. The reviews column connects the credibility problem to the direction I developed into the MVP.

Comparing how platforms collect and control feedback

I compared review requests, reviewer eligibility, visibility controls, and ways to share feedback. These were product choices to resolve for RentSpree, rather than a checklist of features to copy.

Comparison of review features across real estate and service platforms
My comparison at the time of the project. It documents differences in collection, reviewer eligibility, and control over published feedback.

Three decisions that shaped the MVP

The MVP needed a way to collect early feedback, a path for agents with few applications, and an agreement on what could be published. I worked through these choices with the researcher, UX lead, and stakeholders.

Decision 01 · When to ask

Ask after the application is submitted.

Renters had usually spoken with their agent and experienced offline steps such as property viewings before applying. Application submission gave us an existing digital touchpoint to ask about that experience.

Why this moment

Application volume offered opportunities to collect initial feedback without waiting for a completed lease.

What it could tell us

A review at this point described the experience so far. It could not represent the full leasing journey.

The review experience in action.
  1. 01

    Rate the experience

    Choose a rating from 1 to 5 stars.

  2. 02

    Choose compliments

    Highlight strengths such as communication or market knowledge.

  3. 03

    Add a written review

    For ratings of 3–5 stars, describe the experience in your own words.

Renter flow: submit the application, see a prompt, select a rating, optionally add written feedback for 3–5 stars, and submit. Ratings of 1–2 stars count toward the overall score without written feedback; renters can skip the request.
Application-triggered flow, reconstructed from the original design file. The recommendation link used a separate standalone page with a similar review layout.

Decision 02 · Collecting first reviews

Let agents request feedback beyond rental applications.

An application-triggered request would miss agents who worked with few renters on RentSpree. They could already have past clients and experience, yet still have few opportunities to receive a review through our product.

I proposed a shareable recommendation link that agents could send to past clients or coworkers. It shipped as a standalone page, using a similar layout to the in-product review modal.

Application request

Renters encounter a review prompt after submitting an application on RentSpree.

Recommendation link · My proposal

Agents can request feedback from existing contacts without waiting for another rental application.

The MVP allowed one review per email address, per agent. This limited repeat submissions, but did not verify the relationship or label the source of a review.

Decision 03 · The transparency tradeoff

I advocated written feedback at every rating.

What I recommended

The researcher and I advocated written feedback at every rating. Restricting negative written reviews could make the feedback less credible to people choosing an agent.

What shipped

The CEO was concerned that harsh reviews could discourage new agents. Stakeholders and the UX lead supported a launch restriction: 1–2 stars counted toward the score, but only 3–5 stars allowed written feedback.

Internal feedback exposed the gap

An ex-agent working at RentSpree questioned why the text field disappeared at 1–2 stars. After discussion, they accepted trying it in the early release. This was internal feedback, not a renter usability study.

We launched without an explanation for the missing field. I would revisit this restriction first: a feature intended to build credibility should let dissatisfied clients explain their experience too.

The review experience

  1. Leave feedback

    Renters rate their experience after submitting an application.

  2. Manage reviews

    Agents manage feedback before publishing it.

  3. Show on profile

    Clients see ratings, compliments, and published reviews.

Managing feedback

Receiving a review and publishing it are separate steps.

The management experience brings received feedback together before agents publish it to their profiles. The flow also accounts for trial or subscription access; without access, feedback remains in management.

Agent review management

How agents manage feedback before publishing it to their profiles.
Agent flow: receive and manage feedback, check trial or subscription access, then publish eligible reviews. Without access, feedback stays in management.
Agent flow. Receiving feedback and publishing it are separate steps.

Showing reviews

See the rating first, then read the reviews.

The profile shows the overall rating and compliments at the top, followed by individual client reviews.

Agent profile reviews showing the overall rating, compliments, and written client feedback
Ratings, compliments, and client reviews on the Agent Profile. Sample content, not measured project results.

Outcome & reflection

Two collection paths, from review to agent profile.

The MVP shipped with application-triggered requests, the recommendation link I proposed, review management, and publishing to the Agent Profile. My contribution covered the flows, wireframes, and desktop and mobile UI.

What we heard
Early feedback suggested agents updated their profiles after receiving reviews—the behavior we hoped to encourage.
What remains unmeasured
I left before enough data was available to assess sustained impact. Profile-completion and conversion improvements have not been established.

Measurement plan

Would a first review encourage profile updates?

I defined a hypothesis, success metric, and event-tracking requirements for the PM: receiving a first review would encourage agents to update or complete their profiles.

Target: more than 30% within three days
Of agents receiving their first review, more than 30% would update or complete their profile within three days of receipt. This was the planned target, not an observed result.

Looking back, reaching this target alone would not establish the review’s effect: some agents might have updated anyway. I would compare against a baseline and measure updates separately from completion among initially incomplete profiles.

What I would carry forward

Collecting feedback is only one part of building trust.

The recommendation link addressed a collection gap. The launch restrictions left a separate credibility problem: who could explain their rating, and what experience a review represented. I would evaluate those questions alongside review volume.

Planned follow-up work included written feedback at every rating and a second request after leasing. That response would update the earlier review, with a stage label to distinguish the two moments. These changes were not part of the version I launched.