FAQ — Low CSAT response rate

Industry-typical response rates for post-resolution CSAT are 10–25%. If yours is below ~10%, something specific is dragging it down. Six levers, in order of impact.

1. Match the survey channel to the conversation channel

If a customer talked to you on chat and got an email survey, they’re less likely to complete it. The strongest signal you have is they were already comfortable on this channel. Use it.

• Web chat — In-app (inline in the chat widget at close)
• Email — Email
• SMS / WhatsApp — SMS / WhatsApp
• Voice — Email or SMS depending on what’s on file

Atender’s CSAT system supports per-channel delivery — see Configure and deliver a CSAT survey for the setup.

2. Survey in the customer’s language

A Norwegian customer who got Norwegian support and an English survey often skips it. Localizing the survey is the highest-impact single change for non-English-default tenants.

See Localize CSAT surveys. And don’t trust machine translation alone — wording matters here more than in most product copy.

3. Time the send right

The delay between resolution and survey delivery matters:

• 0 minutes — too fast. The customer hasn’t confirmed the issue is actually fixed; they may be back in touch with a follow-up before answering, which makes the survey feel premature.
• 3 hours — common sweet spot. Long enough to confirm the fix held; short enough that the conversation is still mentally fresh.
• 24+ hours — too late for most. The customer has moved on; opening the email feels like work.

If you’re seeing low response on email surveys, the most common cause is the delay being too long, not too short.

4. Keep it short

A survey with one rating question and one optional open-ended follow-up gets meaningfully higher response than a survey with five questions. Every additional question is a friction point.

If you absolutely need more questions, use conditional follow-ups so the long version only appears for low-rating responses (where qualitative depth matters most). High-rating responses should be one-click and done.

5. Don’t survey every customer after every conversation

Survey fatigue is real. A customer who contacted you three times this week and got three surveys will ignore the third — and possibly the next survey from any sender. Use frequency caps:

• Max one survey per contact per 7 days
• Skip if the customer was surveyed on their last conversation

This actually increases your response rate by concentrating sends on customers who haven’t been recently surveyed.

6. Filter out conversations that shouldn’t be surveyed

Some conversations skew CSAT in ways that don’t reflect support quality:

• Auto-replied conversations — the customer never spoke to a human; they’re rating an autoresponder
• Internal test conversations — your own team’s testing
• Spam follow-ups — customers who got resolved on day 1 but kept replying with “thanks” — surveying every reply produces multiple low-meaning responses
• Conversations resolved after weeks — the customer has forgotten the case context

Use an automation rule instead of the resolution trigger if you need to filter. The rule can have conditions excluding the above.

What “good” looks like

Industry benchmarks vary, but rough thresholds for post-resolution CSAT in B2B / SaaS support:

• <5% — Something fundamental is wrong — channel mismatch, language, length all stack
• 5–10% — At least one big lever is misconfigured — investigate top three above
• 10–20% — Healthy but improvable. Tune timing and language
• 20–30% — Good. You’re doing most things right
• >30% — Excellent or you’re surveying a self-selected high-engagement subset

The goal isn’t response rate maximization — it’s response rate plus signal quality. A 50% response rate filled with one-star drive-bys is worse than 20% filled with thoughtful feedback.