Customer story · Resident

How Resident uses Rippit to find what’s costing it customers after the sale

Surveys told Resident where customers were unhappy. Rippit showed why, from returns to delivery, and pointed to the policies to change.

By Rippit Team · Last updated Oct 29, 2026

With Rippit, Resident
  • Fixed its biggest source of unhappy customers

    Found the one step in its returns process causing friction, then changed that policy and retrained every agent on it

  • Found a hidden retention risk

    Found the top reason customers were upset about delivery, and is changing its claims process to resolve it faster

Overview
Industry
DTC ecommerce
Company size
More than 550 employees
Trial and warranty
365-night trial and a forever warranty

Resident, a direct-to-consumer mattress and home goods brand, uses Rippit, the Growth Data Platform, to read every customer conversation alongside its order data. It found the one step in returns causing friction, the top complaint about delivery and a slow approval process, then changed the policy and process behind each to protect retention, future sales and referrals.

The stakes

Why does every step after the sale matter to Resident?

Resident competes on a generous offer: a 365-night trial and a forever warranty on mattresses and home goods bought online. That offer only works if the experience around it does. When a return or a delivery goes wrong, customers cancel, ask for refunds and stop recommending Resident, and the trial that wins customers starts costing them.

“Understanding where the journey falls apart and how it impacts customers is eventually going to impact retention. It’s going to impact future sales, referrals, loyalty, all of these things,” said Michelle Zimmerman, Senior Quality Data Analyst at Resident.

Resident’s executives wanted more than stories. They wanted to know how often each problem happened and what it did to the value of a customer over time.

The problem

Why couldn’t Resident see where the journey broke down?

Satisfaction surveys came back from about 20% of customers. They showed where customers were unhappy, but not why. Returns produced more bad ratings than anything else, and nobody could say which part of returns was the problem.

“Returns specifically were our highest number of DSATs. It was a significant percentage of our overall DSAT score, but we didn’t know what about returns,” said Michelle.

Agents tagged each contact with one label that tried to capture the reason, the solution and the outcome at once. It was a lot to get right in the middle of a conversation, and the tags were often wrong. Without reliable data, Resident couldn’t size a problem or trace it back to where it started.

The shift

How did Resident connect conversations to its business data?

Michelle Zimmerman started at Resident as a support agent and doesn’t call herself technical. When Rippit arrived, she saw it as more than a way to review conversations.

This is our data platform. The more data we can get in, the more we can learn about every part of the customer journey.
Michelle ZimmermanMichelle ZimmermanSenior Quality Data Analyst, Resident

Resident’s data team already knew where each customer was in the journey from their orders. Michelle brought that data into Rippit next to every conversation, so Resident can see why each customer got in touch and what stage they were at.

For the first time, Resident could see which problems were big, which were painful and which were both, measured against satisfaction, volume and cost.

Related use case: Taxonomy Builder →

How Resident uses Rippit

Returns, delivery and operations from the same customer data

Use case 1: Returns and retention

How Resident found the one step in returns causing friction

Returns brought in the most bad ratings, so they looked like the biggest problem. The data told a different story: most returns went well, and customers liked the process. One step in the return lifecycle was causing the frustration.

Returns on the surface have a lot of volume. But once we used AI, we could say, actually, returns are extremely successful, and customers are really happy with our return process. There was just one part of it causing the friction.
Michelle ZimmermanMichelle ZimmermanSenior Quality Data Analyst, Resident

Resident changed the process and policy for that step, retrained every agent on the new approach, and now tracks sentiment, satisfaction and whether customers accept the solutions they’re offered.

“It’s not training the agents to be better. It’s training the agents on a new process, because we made the process better,” said Michelle.

Use case 2: Delivery

How Resident is getting customers a faster fix when delivery slips

Delivery problems weren’t the most common reason customers got in touch, but they were among the most painful. Customers may have already gotten rid of their old mattress when a delivery date slips.

A closer look showed the top reason by far: customers weren’t getting a solution right away. Resident’s transit team checked the data and found that claims were resolved well within a certain window and poorly after it. Resident is now changing how it handles claims with its delivery partners so customers get a solution sooner.

In the long run, it might improve retention, because that person’s not canceling. They’re not escalated. They’re not calling back five other times checking on the status. We’re just providing a solution.
Michelle ZimmermanMichelle ZimmermanSenior Quality Data Analyst, Resident
Use case 3: Operations

How Resident made the case to cut handle time in half

For one type of request, most agents needed a lead’s approval before they could offer a solution, which meant waiting on Slack while the customer waited too. Agents already authorized to handle it on their own took half as long. That gave Resident a clear case to train and authorize every agent.

Workforce management uses the same data. When volume spikes beyond the forecast, they can see why, and whether it’s a real problem or a seasonal one.

Across the company

How did customer insight reach teams beyond support?

Each finding went to the team that could act on it. The executive team gets the numbers with customers’ own words. The transit team gets delivery evidence, and workforce management gets the reasons behind volume changes. Support and sales leaders helped define the reasons for contact, and team leads run Michelle’s prompts on their own teams’ conversations.

“Being able to quantify all of these things, tie it back and prove that these insights are driving these changes is really what matters,” said Michelle.

What’s next

What does Resident want to do next?

Next, Resident wants to see which solutions work best for each kind of problem. It is also exploring a satisfaction measure based on every conversation, alongside surveys from the 20% who answer them, and plans to bring in sales conversations to see whether expectations set before purchase lead to returns or delivery problems later.

“There are many use cases for seeing the whole customer journey, so we can pinpoint where it broke down and improve retention in the long run,” said Michelle.

Related use case: Predictive CSAT →

Results

What results has Resident seen with Rippit?

Resident now knows which step of the journey hurts customers, not just that something does. It fixed the step in returns, is changing how delivery claims work, and has the evidence to halve handle time on one of its slowest requests. Measuring the full effect on retention will take a full 365-night trial cycle.

Returns

1 stepThe returns friction, found and fixed

Returns turned out to go well most of the time. Resident changed the policy for the one step that didn’t, and retrained every agent.

Delivery

#1 issueA faster fix when delivery slips

The top delivery complaint led Resident to change how it resolves claims with its delivery partners.

Operations

½ the timeA case to halve handle time

Agents allowed to resolve one request on their own took half as long, building the case to authorize every agent.

FAQ

Frequently asked questions

What is Resident?

Resident is a direct-to-consumer mattress and home goods brand. It offers a 365-night trial and a forever warranty.

How does Resident find where the customer journey breaks down?

Rippit reads every conversation alongside Resident’s order data, showing why each customer got in touch and where they are in the journey, next to satisfaction, volume and cost. That shows which problems are big, painful or both.

What did Resident change in its returns process?

It found that most returns go well and one step causes the friction. Resident changed the process and policy for that step and retrained every agent on it.

How does Resident use its order data in Rippit?

Its data team already knew where each customer was in the journey from their orders. That data sits next to every conversation in Rippit, so every problem can be tied to a stage of the journey.

Does Resident still use satisfaction surveys?

Yes. Surveys still matter to its executives, and Rippit adds a view of every conversation, not just the 20% of customers who answer.

Find your next edge

Connect a source, set a growth goal and launch an agent that keeps working toward it. Your competitors are already copying. Start building what they can’t.

Start in Rippit

Create an account, write a goal like “Tell me which accounts are at risk, and why,” and Rippit guides you the rest of the way.

Try Rippit free →

Start from your coding agent

Copy this line into ChatGPT, Claude, Gemini or your coding agent. It takes it from there.

Set me up: rippit.com/setup.md