When a customer goes quiet: following up on support without nagging
A support conversation stalls after you asked a question. How long to wait, what to write in each follow-up, and when to close the thread kindly.
On this page(9 sections)
You asked a customer for one thing, such as the error message, the order number or a quick yes. Then nothing. The conversation sits in your inbox, neither solved nor moving. Leave it and it rots. Chase too hard and you become the company that sends three reminders in two days.
This post gives a calm way to handle the quiet customer: how long to wait, what each follow-up should say, and how to close a thread without making anyone feel dropped.
First, check that the silence is real
Before you write anything, rule out your own side.
- Did your last message actually ask something? A reply that explains and ends with "let us know" gives the customer nothing to answer. A thread like that is not quiet, it is finished.
- Was the question easy to find? If it was the fourth paragraph of a long message, they may have missed it.
- Did your message arrive? If you suspect it landed in their junk folder, the checks in your important email went to spam apply to replies as well.
- Is there an out-of-office or a time difference? An automatic reply, or a customer who is asleep for your whole working day, explains a lot.
If all of that is fine, the customer is simply busy, or the problem went away, or they found another way. All three are normal.
How long to wait
There is no universal number, but a simple schedule works for most small teams. Adjust it to how urgent the problem is.
| Situation | First follow-up | Second | Close |
|---|---|---|---|
| Customer is blocked, sending is broken | Next business day | Two days later | Do not close; try another channel |
| Normal question, you asked for details | After 3 business days | After 4 more | After a further 5 |
| Idea or feedback, nothing to fix | After a week | None | Close politely |
The urgent row is different on purpose. When someone cannot work, a quiet thread is a reason to look harder, not to give up. A short phone call or a message through another channel may be better than a third email.
What each follow-up should say
Every message should be short, make it easy to answer and add a little value. Do not paste the same text three times.
The first nudge: restate and simplify.
Hi Maya, I wanted to check in. To look into the missing receipts I only need one thing: the date of the first one that did not arrive. If it is easier, a screenshot of the email list is enough.
It names the one thing needed. It makes answering cheap. It does not say "just following up", which tells the reader nothing.
The second nudge: offer a way out and a way forward.
Hi Maya, I do not want to leave this hanging. If it fixed itself, no need to reply. If not, send me the date and I will pick it up the same day. Otherwise I will close this on Friday, and you can reopen it by replying.
It gives permission to ignore the message, which makes people more likely to answer. It also says exactly what will happen and when.
The closing message: leave the door open.
Hi Maya, I am closing this conversation for now since I have not heard back. Nothing is lost: reply to this message at any time and it comes straight back to me.
Say what you did, say it is reversible, and do not guilt anyone.
Make it easier to answer
A lot of silence is friction. Small changes in the first message prevent it.
- Ask one question at a time. Three questions in one email often get zero answers.
- Offer choices. "Was it before or after Tuesday?" is quicker than "When did this start?"
- Say why you need it. "So I can find the message in our logs" makes the effort feel worthwhile.
- Tell them what happens next. "Once I have this, I will reply within one working day."
For requests that need a file, a log or a screenshot, asking customers for screenshots, logs and files by email goes into how to make the request painless.
Keep track so nothing falls through
The follow-up system fails when it lives in someone's memory. A few habits fix that.
- Mark the conversation as waiting. Use a label or a status that means "we asked, they owe us an answer", separate from "they asked, we owe an answer". Waiting on someone else: tracking pending conversations in a shared inbox describes this in detail.
- Set the date of the next nudge when you send the question. If your mail tool can snooze a thread until a date, snooze it. It will return to your list on the day you chose, so you do not have to remember.
- Review the waiting list once a week. The weekly inbox review is a natural place. Anything older than your closing date gets the closing message.
- Record what was tried. An internal note such as "nudged on the 12th, closed on the 20th" helps whoever picks it up next.
If you use an AI assistant with your inbox, it can list the conversations that have been waiting longer than a set time and draft the nudge in your voice. You review and send it; that part stays with you.
When not to follow up at all
Some quiet threads should be left alone.
- The customer said thanks. A "thank you" is an ending. Replying "you're welcome" is fine, but a follow-up is not.
- The problem was solved by your last message. You can check once, after your fix, as covered in following up after a fix ships, and then stop.
- They are angry and have stopped writing. Silence after a heated exchange is not agreement. A single, calm, short message is better than a chain of reminders. See handling angry customer emails for the tone to use.
- They asked you to stop. Respect it immediately.
A note on automation
It is tempting to automate the whole thing: send a reminder after three days, another after seven, and close at ten. A little automation helps, especially the reminder to a human that a thread is due. Fully automatic customer-facing nudges deserve caution, because they cannot tell a customer who is thinking from a customer who is gone, or one who has already replied by phone. Let the system tell you when a thread is due, and let a person decide what to send.
A short checklist
- Confirm your last message asked a clear question.
- Rule out spam folders, out-of-office replies and time zones.
- Wait the right number of days for the urgency of the problem.
- Send a short nudge that restates the one thing you need.
- Send a second message that gives a way out and a closing date.
- Close the thread kindly, and say it can be reopened by replying.
- Mark waiting conversations and snooze them to the date of the next nudge.
- Leave alone any thread that ended with thanks or a request to stop.
Key takeaways
A quiet customer is not a failure and not a signal to push harder. Check your own message first, wait a sensible time, and make each follow-up short, specific and easy to answer. Give people permission to ignore you, say what will happen next and close the thread in a way that lets them return. Keep the tracking in your tools rather than your head, and your waiting list stays small without ever turning into nagging.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
