How to Reply When Customers Compare You to Competitors

A customer writes, "Competitor X does this for half the price." Or a one-star review says, "Switched to Y, it actually works." It's tempting to get defensive or to list every feature you have.

Here's what usually works better:

1. Thank them and acknowledge the comparison without arguing.
2. Find out what they actually need. The comparison is often a stand-in for one specific problem.
3. Answer with verifiable facts about your product. Don't make claims about the competitor.
4. Be honest about gaps. If the other tool fits them better, it's fine to say so.
5. Give one clear next step, like a workaround, a roadmap note, or a polite goodbye.

The rest of this guide covers each step, gives hypothetical templates for common cases, and explains the extra rules for public app store replies.

Why customers bring up competitors

The points below are analysis, not research findings. In a support conversation, a comparison usually means one of these things:

• A missing feature: "X has dark mode / SSO / CSV export."
• A price worry: "X is cheaper."
• Frustration: "X would have fixed this by now."
• Leverage: "Match X's price or I'll leave."
• Real evaluation: they're still choosing and want help deciding.

Each one needs a different reply. That's why step 2 (finding out what they need) matters more than any template.

Step 1: Acknowledge without getting defensive

Start by showing you read the message. Don't open with a rebuttal. Something like "Thanks for telling me how we compare to X, that's useful" shows you're listening and calms things down.

Avoid replies that question the customer's judgment, such as "X isn't really comparable." Even if it's true, it reads as dismissive.

Step 2: Ask what actually matters to them

If the message is vague ("X is just better"), ask one specific question:

• "Which part of your workflow does X handle better for you?"
• "Is it mainly price, or is there a feature you need?"

One question works better than a list. You'll get a concrete need you can address, and the customer feels heard instead of interrogated.

Step 3: Compare on facts about your own product

Stick to things you can check: your pricing, your features, your limits, your roadmap status. Point to your docs or pricing page when you can.

There's a good reason not to describe the competitor's product. Your knowledge of it may be out of date, and a wrong claim in writing can hurt your credibility.

In the US, the FTC's Statement of Policy Regarding Comparative Advertising actually encourages truthful comparisons that name competitors. It also says disparaging statements are allowed "so long as it is truthful and not deceptive." The test it applies is whether a claim has "a tendency or capacity to be false or deceptive." A support reply isn't always an ad, but the practical takeaway is the same: only claim what you can back up. Rules differ by country, so get advice if you plan to make formal comparisons in marketing.

Step 4: Be honest about gaps

If the competitor really does something you don't, say so. Hiding it rarely works, because the customer already knows.

Then explain what you can offer:

• A workaround you've actually tested
• The real roadmap status ("planned, no date yet" is a fine answer)
• What you do differently on purpose, and why

If you can't solve the problem today, the approach in how to reply when you don't have a fix applies here too.

Step 5: Give a clear next step, even if it's "goodbye"

Not every customer is a good fit. If another tool clearly suits their needs better, helping them leave gracefully protects your reputation and saves both of you time. Make cancellation or data export easy, and keep the door open.

Hypothetical reply templates

The exchanges below are hypothetical examples. Adapt them to your own voice and facts.

"Competitor X is cheaper"

Thanks for flagging this. Price matters, especially for a small team. Our Pro plan is $[price] and includes [specific things you include]. If [the feature they use most] is what you need, the Starter plan at $[price] might cover it. Which features do you use most? I can tell you which plan fits.

If they ask you to match the price, treat it as an exception request. How to reply when customers ask for policy exceptions covers how to say yes or no consistently.

"Competitor X has feature Y and you don't"

You're right, we don't have [feature Y] right now. It's [on our roadmap with no fixed date / not something we plan to build, because …]. Many people handle it by [tested workaround]. If Y is essential for you, I'd rather tell you that clearly than have you wait for something that isn't coming soon.

"I'm switching to X"

Thanks for letting me know, and sorry we didn't fit your needs. If you have a minute, I'd like to know what tipped the decision. It helps us decide what to work on. You can export your data from [location], and your account will stay [active until / available for] [date]. You're welcome back anytime.

"X's support answers faster"

That's fair feedback. We're a [two]-person team, and we usually reply within [your real typical window]. For [urgent issue type], [fastest route] is the quickest way to reach us. Now, about your issue: [actual answer].

The last line matters most. Solving the problem is the best answer to a complaint about support speed.

Public app store replies: extra rules

When a comparison shows up in an App Store or Google Play review, your reply is public and the platforms have rules about it.

• Apple says responses should be concise and respectful and "don't include personal information, marketing language, or spam." It also recommends personalized replies over generic ones. The reviewer is notified and can update their review, and you can edit your response later (Apple: Ratings, reviews, and responses).
• Google Play requires replies to "directly address the user's comment in a clear, valuable, and truthful manner," bans dismissive content and promotions, and warns that breaking these rules can lead to suspension (Google Play Console Help).

In practice:

• Don't turn the reply into a sales pitch against the competitor.
• Address the specific complaint behind the comparison.
• Keep it short, and invite the person to continue by email if it needs detail.
• If you ship a fix later, Apple suggests replying to related reviews to tell users about it.

A hypothetical public reply:

Thanks for the honest review. You're right that sync was unreliable in version 2.3. Version 2.4 fixes the conflict issue you described. If it still happens, please email us at [address] and we'll look into it directly.

What to avoid

• Badmouthing the competitor. Even true criticism makes you look insecure, and it's easy to get facts wrong.
• Feature dumps. Ten bullet points don't answer "does it do the one thing I need?"
• Promises without dates you can keep. "Coming soon" without a plan comes back to bite you.
• Matching price on the spot without a consistent policy.
• Generic copy-paste replies. Customers notice, and Apple specifically recommends personalizing.

For more general pitfalls, see 5 common support reply mistakes.

Turn comparisons into product signals

Comparisons are free market research. A simple habit helps: tag or log every message that mentions a competitor, along with the feature or reason given. After a few weeks you'll see whether people mostly leave over price, a specific feature, or support speed. That's more useful than guessing.

You can also add a short "competitor comparison" section to your support reply checklist: Did I acknowledge it? Did I ask what matters? Are my claims verifiable? Did I avoid describing the competitor?

Where an AI drafting tool fits

If you use AI to draft replies, comparison messages are a good place to review carefully before sending. A model might make confident claims about a competitor that aren't accurate. SupportMe, for example, is built so nothing sends without your approval, and it learns from the edits you make to its drafts. Once you've written a good, factual answer to a common comparison, later drafts can build on it. Your judgment on what's true about your product still has to be the final check.

Conclusion

When a customer compares you to a competitor, they're usually telling you about one specific need. Acknowledge it, ask what matters, answer with facts about your own product, and be honest about gaps. Keep public replies short and in line with platform rules. Handled this way, comparisons build trust even when the customer chooses another tool, and they show you what to build next.

References

• U.S. Federal Trade Commission. Statement of Policy Regarding Comparative Advertising (1979).
• Apple Developer. Ratings, reviews, and responses.
• Google Play Console Help. View and analyze your app's ratings and reviews.