---
title: "My Customer Went Quiet: How Do I Get Them to Reply Again?"
description: "When a customer went quiet, stop sending check-ins. A six-touch re-engagement sequence, the message types that get replies, and the rule for when to stop."
topic: "Retention & Churn"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Customer Success Manager, Account Manager"
published: 2026-09-04
modified: 2026-09-04
source: https://gaintrace.com/explore/retention/customer-went-quiet-reengagement-playbook
---

# My Customer Went Quiet: How Do I Get Them to Reply?

*What to send, in what order, and when to stop*

**Short answer:** When a customer went quiet, stop the check-in cadence: a check-in costs nothing to ignore. Send one message that gives them something from their own data, then change the person before the channel, make one specific ask with a date, and finish exec to exec. Six touches over three weeks. If usage is steady and they still do not reply, stop and move the account to a lighter tier.

**Key takeaways**

- Delete "just checking in" from your vocabulary. Every message in the sequence either gives the customer something or asks for one specific, dated thing.
- Diagnose the quiet before you chase it. Quiet with steady usage is a working customer; quiet with falling usage or a missing champion is a risk event.
- Change the person before the channel. A second stakeholder replies more often than the same champion on a new medium.
- Six touches, two people, two channels, 21 days, then stop. Chasing past that point costs you credibility and buys nothing.
- Set the silence rule at kickoff so the first escalation to a sponsor is a promise kept, not an ambush.

You did the work, and the customer went quiet anyway. Clean onboarding, a check-in cadence, adoption gaps flagged early, QBRs on the calendar. Then nothing for six weeks. The check-ins go out and come back as silence, the QBR gets pushed, and the next time you hear from the account it is two weeks before renewal, something has broken, and they are suddenly very available and very unhappy.
This page is for the CSM or account manager whose sequence is already running and not producing replies. It explains why check-ins get ignored, how to tell which kind of quiet you are dealing with, the six-touch sequence we would run instead, and the rule for when to stop.

## Why do my check-ins get ignored?

A check-in asks the customer to do work for your benefit: report status, confirm things are fine, find a slot. It carries no cost if ignored and no reward if answered. From the customer's side it is another vendor email, and they get dozens. The thread in our corpus that describes this best was written by someone who had done everything right.

> "You do everything right. Solid onboarding, regular checkin emails, flagging adoption gaps early, scheduled QBRs. Then radio silence for weeks or months. Until something breaks or renewal is two weeks out and suddenly they're very responsive and very unhappy."
>
> — r/CustomerSuccess, 2026

One detail from the evidence explains why the standard advice does not help. Of 3,628 public G2 reviews of the three most-reviewed customer success platforms, only 7 mention an unresponsive or ghosting customer at all. Reviews are written by the people who configure the software. The problem lives in the CSM's inbox, which is why 16 of the 946 r/CustomerSuccess threads we read are about it and the software reviews are not. Automated cadences, the thing the platforms are good at, are what the customer is ignoring.

> "Health score drops, you flag it, you reach out, you maybe get a oneline reply saying things are fine. Then three months later they're in churn conversations acting surprised. The problem is that customers don't feel urgency from a health score the way we do internally. To them it's just another email from their vendor."
>
> — r/CustomerSuccess, 2026

The fix is to make every message either worth reading on its own or impossible to ignore without a small decision. That is a different sequence from the one most teams run, and it starts by switching the current one off.

## How do I work out why the customer went quiet?

Silence means different things depending on what else moved. Before you send anything, look at usage, the champion and billing. The [early warning signs of churn](https://gaintrace.com/explore/retention/early-warning-signs-of-churn-scattered-data) page shows how to read each source; the table below is the short version for this situation.

| What you see | What it usually means | What to do |
| --- | --- | --- |
| No replies, usage steady or rising | The product works and they do not need you. This is the good kind of quiet. | Do not run the sequence. One finding message a quarter, and a renewal-timeline notice at 120 days. Move to a lighter tier. |
| No replies, usage falling against their own baseline | A decision is being made without you. The classic pre-churn pattern. | Run the full sequence now, starting at touch one. Escalate internally at touch four, not touch six. |
| No replies, champion has changed role or left | Nobody owns you inside the account. The silence is structural, not a choice. | Skip to touch three: find the new owner. Write to the sponsor and the most active user in parallel. |
| No replies, seats removed or invoice late | Contraction has already started. Renewal is in play whether they say so or not. | Skip the sequence. Go exec to exec this week with the renewal date in the first line. |
| Quiet since kickoff, never engaged | An onboarding problem, not a re-engagement problem. Value was never established. | Restart onboarding with a new first milestone. See [onboarding complete but the customer churned](/explore/onboarding/time-to-value-onboarding-complete-but-churned). |

> "Some accounts are quiet because everything genuinely works. Silence from a power user who onboarded cleanly is not the same as silence from a champion who used to loop you in."
>
> — r/CustomerSuccess, 2026

## What does the re-engagement sequence look like?

Six touches, two people, two channels, 21 days. Each touch is short, and none of them says "checking in". Day numbers are a default; compress them if renewal is inside 90 days.

1. **Day 0: switch off the cadence.** Remove the account from every automated check-in, adoption nudge and newsletter for 30 days. If the next thing they receive from you is another template, nothing below will land.
2. **Day 1: the finding.** One message, three sentences, no ask. Something from their own account: "Your team ran the same weekly report 31 times last month. It can be scheduled; here is the two-minute setup." The customer should be able to act on it without replying. This is the message that gets read.
3. **Day 4: the outcome reminder.** Reference the goal they stated at kickoff, in their words, and ask one yes-or-no question about it. "At kickoff you said the target was closing month-end in three days instead of eight. Are you there yet?" A yes-or-no question gets a one-word answer, and a one-word answer reopens the thread.
4. **Day 8: change the person.** Write to a second stakeholder, ideally the executive sponsor or the most active user, and copy the champion. Say what you sent the champion and why it matters to the sponsor's number. This is the touch we would bet on, and the one most CSMs leave until last because it feels like going over someone's head.
5. **Day 12: change the channel.** Phone, an in-app message, a 60-second video, a LinkedIn note. The content is the finding from day one, shortened. Do not introduce anything new; the aim is to make the same message unavoidable.
6. **Day 18: one specific, dated ask.** "Fifteen minutes on Thursday at 2 to walk through the scheduled reports before your renewal window opens on 1 October." A specific slot, a specific reason, a date that belongs to them. Offer one alternative, not a link to your whole calendar.
7. **Day 21: exec to exec.** Your head of CS or founder writes to their sponsor. Three lines: what the team has seen, what it means for the renewal, and a request for a 20-minute call. If there is no reply to this, you have your answer and it is time to apply the stop rule.

## Which message type should I send, and what is each one for?

The sequence above uses seven message types. Each does one job. Mixing jobs inside one email (a finding plus a meeting request plus a renewal reminder) is the fastest way to make it look like a check-in again.

| Message type | What it is for | What good looks like |
| --- | --- | --- |
| The finding | Proving you looked at their account, and giving them something to act on with no reply required. | Three sentences. One number from their data. One thing they can do in two minutes. |
| The outcome reminder | Reconnecting the product to the goal they set, in their own words. | Quote the kickoff goal. Ask one yes-or-no question. |
| The second-stakeholder note | Finding the person who owns you when the champion has gone quiet or gone. | Addressed to the sponsor, champion copied. Explains what the sponsor's number is at stake. |
| The channel switch | Making the same message unavoidable without adding new content. | Same finding, half the length, different medium. Never a new topic. |
| The specific ask | Converting attention into a slot. | One time, one alternative, one reason tied to a date they own. |
| The renewal-timeline notice | Putting the date in front of them before it is an emergency. | Sent at 120 days regardless of engagement. States the date, the process and the one decision they will need to make. |
| Exec to exec | Escalating with a peer relationship the CSM does not have. | From your leader to theirs. Three lines. A request, not a warning. |

Two things are missing from the table on purpose. "Just checking in" is not a message type; it is the absence of one. And the breakup email ("I will assume you are no longer interested") is for prospects. A customer under contract does not need permission to close, they need a reason to open.

## When should I stop reaching out?

> **The silence clock:** The silence clock starts when the account stops replying, not when you notice. Two weeks of silence from a champion who used to answer in a day is a bigger signal than a low health score, and the clock decides which of the message types you send and when to stop sending them.

The sequence has an end because chasing has a cost. Every unanswered message after the sixth makes the seventh easier to ignore, and the time is better spent on an account that will reply.

> **Stop rule:** Stop after six touches to two people over two channels in 21 days. If usage is steady and renewal is more than 90 days away, move the account to a lighter tier, keep the quarterly finding, and set a tripwire at 120 days before renewal. If usage is falling, the champion is gone, billing has moved, or renewal is inside 90 days, do not send a seventh touch. Escalate internally and treat the account as a forecast risk.

> **Worked example:** An account at $24,000 ARR, 25 seats, renewal in five months. Last reply from the champion was nine weeks ago. Seats are unchanged, but weekly active users fell from 19 to 11 against a 90-day baseline of 18. That is the second row of the table: run the full sequence. Day 1, the CSM sends a finding about the six users who lost access after a permissions change (the likely cause of the drop). Day 4, the outcome reminder gets a one-word "yes". Day 8, the note to the sponsor gets a reply: the champion has moved to another team and the sponsor did not know the tool was still in use. The sequence stops at touch three because it worked. The account is now a renewal with a new owner, which is a different playbook: [renewal call prep](https://gaintrace.com/explore/playbooks/renewal-call-preparation-checklist).

## Why is the sequence still not getting replies?

When a team runs this and still gets silence, one of these is usually why.

- Every message asks for a meeting. A meeting is the most expensive thing a customer can give you. Ask for it once, at touch six, after five messages that cost them nothing.
- The finding is about your product, not their account. "We launched a new dashboard" is marketing. "Your team exported 400 rows by hand last week" is a finding.
- You only ever write to the champion. The person who went quiet is the least likely to reply. The second stakeholder is the touch that works.
- The renewal notice is buried in an automated 90-60-30 sequence the customer has learned to skip. One thread in our corpus describes zero opens on four follow-ups, then three panicked replies the day the contract expiry finally reached them by voicemail.
- You are chasing accounts that do not need chasing. The first row of the table above is a working customer. Six touches will make them like you less, not more.
- The tone is apologetic. "Sorry to bother you again" tells the customer the message is a bother. State the finding and stop.

> "More engagements doesn't mean great relationships with a customer, as you normally connect more with those customers at risk."
>
> — Customer Success Manager, enterprise SaaS, public G2 review

## How do I make silence a risk signal before it happens?

The sequence works better on accounts where the rules were set at kickoff. Three things to build into onboarding so the next quiet account is a promise kept rather than an ambush.

- Name two contacts and a sponsor before go-live, and put them in the CRM. A single-threaded account cannot be re-engaged when the thread goes quiet.
- Agree the silence rule out loud: "If we do not hear from you for 30 days, we will write to [sponsor] to check the rollout is still on track." Customers agree to this readily at kickoff and almost never object when it happens.
- Put the renewal date in front of them at 120 days as a routine notice, not a sales touch, so the first mention of renewal is never two weeks out.

One of the threads we read asked exactly this: whether to "set expectations at onboarding that silence gets treated as a risk signal". In our experience it is the single change that most reduces the number of accounts that need the sequence at all. If your QBRs are the meeting the customer keeps skipping, [QBRs stopped being useful](https://gaintrace.com/explore/playbooks/qbr-template-when-qbrs-stop-being-useful) covers the shorter format that gets attended.

## How does GainTrace handle a customer who went quiet?

GainTrace reads inbound volume, usage, champion changes and billing together, so a quiet account is classified before anyone writes to it: working customer, falling usage, missing owner or contraction. [Product signals](https://gaintrace.com/platform/product-signals) surface the finding for touch one from the account's own data, and [rescue playbooks](https://gaintrace.com/solutions/rescue-playbooks) run the sequence above with the stop rule built in, so the seventh touch never goes out and the escalation reaches the right sponsor with the reason attached.

## Frequently asked questions

### What should I write to a customer who has gone quiet?

Send a finding, not a check-in: three sentences with one number from their own account and one thing they can do in two minutes, with no request to reply. Follow it four days later with a yes-or-no question about the goal they set at kickoff. Save the meeting request for the sixth touch, after the customer has received five messages that cost them nothing.

### How many times should I follow up with an unresponsive customer?

Six touches across two people and two channels over about three weeks, then stop. If usage is steady, move the account to a lighter tier and set a tripwire at 120 days before renewal. If usage is falling or billing has moved, do not send a seventh message; escalate internally and treat the account as a forecast risk.

### Should I go over my champion's head when they stop replying?

Yes, at touch three, and copy the champion so it is transparent. Address the sponsor with what you sent the champion and why it matters to the sponsor's number. Practitioners in the threads we read list a second stakeholder among the few moves that shifted the dynamic, and it is the one CSMs delay longest because it feels uncomfortable.

### Is a customer going quiet always a churn risk?

No. Quiet with steady or rising usage is a customer the product works for, and chasing them costs goodwill. Quiet with falling usage against their own baseline, a champion who has changed role, or seats removed at true-up is a risk event. Check those three things before you send anything.

### How do I re-engage a customer before renewal when they have ignored me for months?

Compress the sequence to ten days and start with the renewal-timeline notice: the date, the process and the one decision they need to make. Then send the finding and go to the sponsor within a week. Inside 90 days of renewal, silence is a forecast problem, so tell your manager at touch three rather than touch six.

### Why do customers ignore health score alerts and check-ins?

Because the alert is urgent to you and invisible to them. A health score is an internal number; to the customer, an email about it is one more vendor message. Messages get replies when they contain something from the customer's own account, ask one small question, or arrive from a peer of the person receiving them.

## How this was researched

We read 1,328 threads from r/CustomerSuccess, r/SaaS, r/sales and r/startups and pulled every thread about customers who stop replying (22, of which 16 are in r/CustomerSuccess), then read the full text and replies for what practitioners say worked and what they ruled out. We also searched 3,628 public G2 reviews of the three most-reviewed customer success platforms for the same situation and found it mentioned in only 7. The sequence, the message-type table and the stop rule are our synthesis; the worked example uses illustrative figures.

## Sources

- [r/CustomerSuccess: How do you handle customers who ignore your outreach until something breaks?](https://reddit.com/r/CustomerSuccess/comments/1udcl52/how_do_you_handle_customers_who_ignore_your/)
- [r/CustomerSuccess: How early do you escalate a customer who has gone completely dark?](https://reddit.com/r/CustomerSuccess/comments/1u0ww1o/how_early_do_you_escalate_a_customer_who_has_gone/)
- [r/CustomerSuccess: How do you handle customers who ignore health score warnings until it's too late?](https://reddit.com/r/CustomerSuccess/comments/1v1h23t/how_do_you_handle_customers_who_ignore_health/)
- [r/CustomerSuccess: Clients treating their inbox like a suggestion box is destroying my Q2 metrics](https://reddit.com/r/CustomerSuccess/comments/1t82vso/clients_treating_their_inbox_like_a_suggestion/)
- [r/CustomerSuccess: The earliest churn signal I trust isn't usage dropping, it's the customer going quiet](https://reddit.com/r/CustomerSuccess/comments/1vddre0/the_earliest_churn_signal_i_trust_isnt_usage/)

## Next steps

Know which kind of quiet you are dealing with before you write, and never send the seventh touch. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).