Replying when you don't have the answer yet: an honest holding email
A customer asks something you cannot answer today. How to write a holding reply that is honest, sets a real next date and keeps the customer from writing again.
On this page(10 sections)
Every support inbox gets questions that cannot be answered on the spot. The cause might be a bug you need to reproduce, a policy nobody has decided, or a colleague who knows the answer and is out until Thursday. The pressure in that moment is to say something quickly, and that is where replies go wrong. People write "We're looking into it" and then nothing happens for a week.
A good holding email buys time honestly. It tells the customer what you know, what you do not, and exactly when they will hear from you again. This post shows how to write one, and how to keep the promise it makes.
Why "we're looking into it" fails
That sentence has three problems. It says nothing about what you are doing, so the customer cannot tell whether anyone has started. It gives no date, so the customer has to guess when to chase. And it quietly creates a promise that nobody owns.
The result is predictable. The customer writes again after a few days, now frustrated, and the second message costs more to handle than the first. A short, specific holding reply usually prevents that second message.
The four parts of a good holding reply
- Say what you understood. One sentence that restates the problem proves a person read it. "You were charged twice on October 3 and only one invoice shows in your account."
- Say what you do not know yet. Be plain about it. "I cannot yet tell whether the second charge was a duplicate or a separate renewal."
- Say what happens next, and who does it. "I am checking the payment records today and asking our billing contact to confirm."
- Give a date for the next message. Choose a day you can keep, and write it. "You will hear from me by end of day Thursday, even if I only have an update."
That last promise matters most. It also gives you something to schedule. See waiting on someone else: tracking pending threads in a shared inbox for a way to mark the thread and set a check date.
An example
Hi Priya,
Thanks for the details. You exported a report on Monday and the file only contains half of your rows. I can see why that would worry you.
I do not yet know whether the export stopped early or the filter you used removed the rows. I am reproducing it with your settings today, and if it is a fault I will pass it to engineering with your example.
You will hear from me by end of day Wednesday either way. If you can tell me which filter was active, that will speed things up.
It is short, it has no apology theater, and the customer knows what to expect. It also asks for one useful thing instead of five.
Choosing a date you can keep
The date is a commitment, so pick it like one.
- Use the time you need to find out, not the time that sounds comfortable. If you must ask a colleague who replies within a day, say "tomorrow".
- Add a little margin. A promise kept a day early builds more trust than one kept at the deadline.
- Promise an update, not a resolution. You can control whether you write back on Wednesday. You cannot always control whether the fix is ready.
- Name business days when it matters. "By Friday" is clear. "In two days" over a weekend is not.
If you are not sure how long something will take, say that too: "I will write back by Friday with either an answer or a firm estimate." For help setting response targets that match what a small team can actually do, see email SLA targets for small support teams.
Words to avoid
Some phrases sound reassuring and say little.
| Instead of | Try |
|---|---|
| "We're looking into it" | "I am reproducing this with your settings today" |
| "As soon as possible" | "By Thursday afternoon" |
| "I will get back to you shortly" | "I will write back tomorrow morning" |
| "Unfortunately" at the start | Start with what you understood |
| "I'm sorry for any inconvenience" | "I am sorry the export was incomplete" |
An apology is fine when it is specific. A general one reads as a template.
When someone else holds the answer
Often the answer sits with another team or a single colleague. Keep the customer's thread and the internal question connected:
- Ask the colleague in an internal note on the same thread, so the question and the customer's message live together. The approach is described in escalation paths for email support.
- Ask a closed question. "Was the second charge on Oct 3 a renewal or a duplicate?" gets a faster answer than "Can you look at this customer?"
- Tell the colleague your promised date, so they know the real deadline.
If you need more detail from the customer, ask once and ask for everything at the same time. The guide to asking customers for screenshots, logs and files by email covers how.
Keeping the promise
A holding email is a debt. Treat it as one:
- Put the date where you will see it. Use a label, a note on the thread or a calendar reminder.
- If you have nothing new on the day, write anyway. "I do not have the answer yet. The engineer is still testing. Next update Friday." That is a real message, and it keeps the trust you built.
- If you cannot make the date, say so before it passes. A message sent the day before is a courtesy. A silence after is a failure.
- Close the loop when you resolve it. Say what happened, what changed and whether the customer needs to do anything. Our post on following up after a fix ships shows the shape.
What about AI drafts?
An AI assistant can write a holding reply quickly, but it does not know what you will actually do or by when. If you use one, read the date and the promised action before sending. In Koltrix, drafts are never sent without a person clicking send, so the check is yours. Fill in the real next step yourself; a draft that promises something nobody agreed to is worse than a plain one.
A short checklist
- Restate the problem in one sentence.
- Say plainly what you do not know.
- Name the next step and who is doing it.
- Give a specific date for the next message.
- Ask for at most one useful piece of information.
- Mark the thread so the date does not get lost.
- Write on the date, even with no news.
Key takeaways
Customers do not need an instant answer to every question. They need to know that someone has the problem, what is being done and when they will hear next. A holding reply that says those three things, followed by an update on the day you promised, takes two minutes to write and saves the angry second email.
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.
