← All writing

The Abandoned Cart Email That Asks Why You Didn't Buy

Learn how a simple abandoned cart email can reveal why shoppers leave, uncover checkout problems, and help you improve more than one sale.

Jordan Glickman·November 19, 2026·5 min read
DTC

An abandoned cart email can do more than bring back a sale. It can tell you why the sale did not happen.

That is what I learned when I used a plain-text email from me as the founder. The goal was simple: ask what stopped the person from buying, then make it easy to reply.

The answers gave me things an order report could not. People raised payment problems, discount-code issues, slow pages, and doubts about the product. These were useful clues about the buying process.

A lost sale is a result. A customer's reason can show you what to fix.

What Should You Ask in an Abandoned Cart Email?

Ask one clear question: What stopped you from placing your order?

Give people a few possible reasons, then leave room for their own answer. Some people will choose a quick option. Others will explain a problem you had not thought to ask about.

Here is an example you can adapt. It is a new sample, not the exact email I sent:

Hi, I'm Jordan, the founder.

I noticed you did not finish your order. Was there something we could have made clearer or easier?

Was it the price, delivery, a payment issue, or something else?

Just reply to this email. I'd like to understand.

Keep the message honest. If you say the founder will read replies, make sure that happens. If a team handles them, say so. The email should feel like a real chance to help, because it is one.

Why Ask Instead of Offering a Discount?

A discount only solves some problems.

It will not fix a broken payment step. It will not explain a product claim. It may not help someone who needs delivery sooner than you can offer it.

Offering money off before you understand the problem can hide the cause. It can also reduce the profit on an order that did not need a discount.

This does not mean discounts are always wrong. It means they should have a job. Ask whether the customer needs a lower price, more trust, a clearer answer, or a working checkout.

Those are different needs. They call for different responses.

Discount email vs a question
Offer a discount
  • Helps when price is the real concern
  • Will not fix a broken payment step
  • Can hide the cause and cut profit
Ask what stopped them
  • Surfaces payment, code, delivery, and product doubts
  • Shows what to fix for the next buyer
  • Keeps discounts for when price is the problem

What Did I Learn From Customer Replies?

I learned that people can get stuck in ways the business does not see from inside.

A page may work when your team tests it. A customer may use a different phone, payment method, or code. A product detail may seem clear to you because you explain it every day. A first-time buyer does not have that background.

In my case, replies exposed both technical friction and missing information. That made the email useful even when a person did not come back and buy.

I did not run a split test on this approach. I cannot claim it produced a certain sales lift. The lesson I can share is narrower: asking people directly gave me issues worth checking.

How Do You Turn Replies Into Useful Changes?

Start with a small log. You do not need a complex survey tool.

Customer's concernWhat to checkPossible next step
Payment failedPayment logs and the checkout stepsFix or explain the failed step
Code did not workOffer rules and code settingsMake the rules clear or repair the code
Delivery was unclearWhere timing and cost appearShow both before checkout
Product felt uncertainRepeated questions and page copyAdd a clear, supported answer
Price felt too highValue, total cost, and fitReview the offer before cutting price

Give each issue an owner. Keep the customer's report separate from the confirmed cause. "The page felt slow" is a clue. It is not yet proof of why the page was slow.

Then check what happens after a fix. Do similar complaints fall? Do fewer people fail at that step? Can your team repeat the problem?

How Much Weight Should You Give Each Reply?

Listen closely, but do not treat every reply as a market survey.

People who reply are a small group. Their views may differ from those who stay silent. One person asking for a feature does not prove that most shoppers need it.

Look for patterns. Combine replies with support tickets, site data, and direct checks. If three sources point to the same issue, you have a stronger reason to act.

Sometimes one report is enough to investigate. A failed payment deserves a check even if nobody else has reported it.

FAQ

Should a founder send the abandoned cart email?

A founder's name can make the message personal, but the response must be real. Use a sender who can listen and help. Do not make a false promise of personal attention.

Should every email ask for feedback?

No. Give each email one main purpose. A feedback message can sit within a broader cart flow. Avoid sending repeated requests to someone who has already answered or bought.

Is plain text better than a designed email?

Not in every case. Plain text suited the conversation I wanted to start. Test what works for your audience instead of treating one format as a rule.

How should I measure success?

Track useful replies, verified issues, fixes made, and recovered orders separately. A useful reply and a sale are different results. Do not add them together as revenue.

The bottom line

The lesson for me was simple: I knew a lot about the people who bought. I had much less insight into those who almost did.

An honest question helped close that gap.

Before you write another discount email, ask what you still do not understand about the sale you lost. The answer may help the next customer as much as the one who replies.

Keep reading

Pieces I've written on related topics that pair well with this one:

Keep reading
Subscribe to the newsletter

Get every post in your inbox.

New writing every two weeks. No fluff. Unsubscribe anytime.

Subscribe