Acknowledgement and holding reply email templates (UK)

How to use these

The replies that keep a customer from wondering

An acknowledgement is a short reply that confirms you have a customer's message and that someone real is on it. A holding reply does the same job a little later, when you need more time without going quiet. Neither has to solve the problem; their job is to stop the silence, name what the customer asked about, and give a realistic next step or date. The templates below are written to do exactly that, across the whole life of a ticket.

Every template uses placeholders in square brackets, such as [customer name], [reference number], [date] and [team name]. These are illustrative gaps for you to fill in before sending. They are a writing convention, not merge tags or any automated field, so replace each one by hand or paste the template into a saved reply and edit it. Keep the brackets out of the message you actually send.

Where a template points the customer to a help page, an order, or a returns policy, use descriptive link text such as read our returns policy rather than a raw web address. It reads better, it is clearer about where the link goes, and it is kinder to anyone using a screen reader. The same applies to any link back to a tracking page or a self-service article.

A quick checklist before you press send: does the reply confirm you have received the message; does it name the issue or the reference so the customer can match it; is the next step or the timeframe clear; and, if you are buying time, have you given an honest date rather than a vague soon. If all four are true, the acknowledgement is doing its job.

We have your message

We have received your message templates

Send the moment a message lands and you cannot answer it in full yet. Tone: warm, prompt and certain. The customer mainly wants to know that a person has their message and that it will not be forgotten.

Standard acknowledgement

Subject: We have your message, [reference number]

Hello [customer name], thank you for getting in touch. This is just a quick note to let you know your message has reached us safely and is now with our team under reference [reference number]. We are looking at it and will come back to you with a proper reply by [date or time, for example the end of tomorrow]. There is nothing more you need to do for now. If anything changes at your end in the meantime, simply reply to this email and it will stay with the same ticket. Thank you for your patience, from all of us at [brand name].

Acknowledgement with a response-time estimate

Subject: Thanks, we have your enquiry and will reply by [date]

Hello [customer name], thank you for writing in. We have received your enquiry about [topic] and have logged it as [reference number]. Our usual response time is [response window, for example one business day], and we are well within that, so you should hear back from us with a full answer by [date]. If your question turns out to be more involved, we will tell you what is happening rather than leave you waiting. Please keep this email so you have your reference to hand.

After-hours acknowledgement

Subject: We have your message and will pick it up [next working day]

Hello [customer name], thank you for your message. It has arrived safely, although it has reached us outside our working hours of [opening hours]. A member of the team will pick it up first thing on [next working day] and reply by [date]. We have not missed it; it is in the queue under reference [reference number] and waiting for us in the morning. If your matter is urgent, please add anything that would help us prioritise it when we reply, and we will treat it accordingly.

Give a date, not a soon

A vague we will get back to you soon invites a chasing email and erodes trust. Naming a real date or time, even a generous one, sets a clear expectation and lets the customer get on with their day. On Solves, first-response and resolution SLA timers with a breaching view surface the messages coming due, so the date you promise lines up with the queue you are actually watching.

Looking into it

We are looking into it templates

Send when you have started work but cannot resolve it in this reply, or when an earlier promise needs honouring with a progress note. Tone: reassuring, specific and honest. Tell the customer what you are doing and when the next update will land.

Work in progress update

Subject: An update on [reference number]

Hello [customer name], a quick update on your message about [topic], reference [reference number]. We are looking into it now and have [the specific step you have taken, for example checked your account and contacted our [team name] team]. We do not have the full answer for you yet, but we expect to by [date]. We would rather give you an honest update than go quiet, so this is us keeping our word. If anything new comes up at your end, just reply and it will reach the same person handling your ticket.

Holding reply when the answer needs a colleague

Subject: We are on it, [reference number] is with our [team name] team

Hello [customer name], thank you for bearing with us. Your query about [topic] needs a hand from our [team name] team to get it right, so we have passed reference [reference number] to them with all the detail you gave us. You do not need to repeat anything; we have carried it across for you. They aim to come back with an answer by [date]. We will stay across it and chase internally if it slips, so you are not the one left waiting. Thank you for your patience while we make sure you get the correct answer rather than a quick guess.

Apology and update when it is taking longer than promised

Subject: Sorry for the wait on [reference number], here is where we are

Hello [customer name], I am sorry this is taking longer than we said it would. I want to be straight with you about where your query, reference [reference number], stands. We are [the honest current status, for example waiting on a supplier to confirm stock]. The realistic next step is [next step], and I expect to be able to update you properly by [revised date]. I am sorry to have kept you waiting; I will personally make sure you hear from us by then, whether or not we have the full answer.

A holding reply is not a non-answer

A good progress note names the specific step you have taken and the next date the customer will hear from you. That single detail, what you actually did, is the difference between a holding reply that reassures and a stock phrase that frustrates. Keep a saved reply as a skeleton and fill in the real status each time.

We need more detail

Requesting more information templates

Send when you cannot move forward until the customer tells you something. Tone: helpful and specific. Ask for exactly what you need, explain why, and make it as easy as possible to reply.

Asking for one or two specific details

Subject: A quick question so we can help with [reference number]

Hello [customer name], thank you for your message. We would love to sort this out for you, and to do that we just need a little more detail. Could you let us know [the specific thing you need, for example the order number and the email address used at checkout]. With that in hand we can [what you will then do, for example locate your order and check its status] and reply with a full answer. There is no rush, but your ticket will sit on hold under reference [reference number] until we hear back, so a quick reply means a quicker resolution.

Asking for a screenshot or example

Subject: Could you show us what you are seeing, [reference number]

Hello [customer name], thank you for letting us know about [the problem]. To get to the bottom of it, it would really help to see exactly what you see. When you have a moment, could you reply with [what you need, for example a screenshot of the error and the page or screen you were on when it happened]. The more we can see, the faster we can pin down the cause rather than ask you to try things at random. Reply to this email with anything you can share and we will pick it straight back up under reference [reference number].

Gentle reminder when a reply is outstanding

Subject: Still here when you are ready, [reference number]

Hello [customer name], we wrote a little while ago to ask for [the detail you requested] so we could move your query forward. We have not heard back yet, which is no problem at all; we know life gets busy. Your ticket, reference [reference number], is still open and waiting for you. Whenever you have a moment, just reply with [the detail] and we will get straight on with it. If your question has since sorted itself out, a one-line reply to say so means we can close it tidily and not chase you again.

Resolved

Issue resolved templates

Send when the matter is sorted. Tone: clear, friendly and complete. Confirm what was done, what the customer can expect now, and leave the door open in case anything is still off.

Standard resolution

Subject: Sorted, [reference number] is resolved

Hello [customer name], good news, your query about [topic] is now resolved. Here is what we did: [the action you took, in one or two plain sentences]. As a result, [the outcome the customer can expect, for example your refund of [amount] will reach your account within [timeframe]]. We have closed your ticket, reference [reference number], but it is far from final; if anything still looks wrong or you have a follow-up question, simply reply to this email and it will reopen with all the history attached. Thank you for your patience while we put it right.

Resolution with a next step for the customer

Subject: All done on our side, one small step left for you

Hello [customer name], we have resolved the issue you raised under reference [reference number]. From our side everything is now in place: [what you completed]. There is one small thing left for you to do, which is [the customer's next step, for example sign in again and confirm your new details look right]. Once you have done that you should be fully back up and running. If that step does not go smoothly, or anything still is not right, reply to this email and we will jump back on it. Thank you for working through it with us.

Resolution after a problem or complaint

Subject: Putting things right, [reference number]

Hello [customer name], thank you for your patience while we sorted this out, and again, I am sorry for the trouble it caused. To put it right we have [the action taken], and [the outcome, for example arranged a replacement to reach you by [date]]. I have also [any goodwill or preventive step, if applicable]. Your ticket, reference [reference number], is now resolved, but please do reply if anything is still not as it should be; I would much rather hear from you than have you left unhappy. Thank you for giving us the chance to fix it.

Closing a ticket is not a closed door

Tell customers that replying to a resolution email brings the ticket back with its full history attached. On Solves, a reply to a resolved ticket reopens it for the team, so the customer never has to start from scratch or repeat themselves. Saying so in the email removes the worry that closed means forgotten.

How did we do

Inviting feedback templates

Send at the end of a resolution, when you would like to know how the support went. Tone: warm, brief and genuinely optional. A note on what these can and cannot do today: Solves does not yet ship a built-in rating or satisfaction score, so write these as plain invitations to reply, not as a promise of a one-click rating button.

A gentle invitation to reply

Subject: How did we do with [reference number]

Hello [customer name], now that your query is sorted, we would genuinely like to know how the experience felt for you. If you have a spare moment, just reply to this email and tell us, in as few or as many words as you like, whether we got it right and anything we could have done better. There is no form to fill in and no pressure at all; an honest line or two helps us look after the next person a little better. Either way, thank you for choosing [brand name], and please do come back to us any time.

Light feedback request after a tricky case

Subject: We would value your honest take, [reference number]

Hello [customer name], thank you for sticking with us while we worked through this one. Cases like yours teach us the most, so if you are willing, we would really value your honest take on how we handled it. A quick reply to this email is all it takes; tell us what went well and what felt frustrating, and it goes straight to the team who looked after you. We read every reply and we do act on them. Thank you again for your patience, and for helping us do better next time.

Closing with an open door rather than a score

Subject: That is sorted, and our door stays open

Hello [customer name], we are glad we could help, and your ticket, reference [reference number], is now wrapped up. We are not going to send you a long survey; we would simply rather you knew that if anything we did fell short, or if you think of something afterwards, a reply to this email reaches the same people every time. Your feedback, good or bad, genuinely shapes how we work. Thank you for your custom, and we hope the next thing you need from us is just as easy to sort.

No one-click rating, yet

These feedback templates invite a reply in the customer's own words. A built-in satisfaction score is on the Solves roadmap rather than live today, so avoid wording that promises a star rating or a one-click button. Asking customers to reply is honest, accessible, and works in any inbox right now.

Make them reusable

Turn these into saved replies in Solves

Solves does not auto-fill or send these for you. It keeps the wording one click away so your team writes once and reuses everywhere, editing the details before each send.

Paste once, reuse forever

Drop a template into a saved reply, name it clearly, such as We have your message or Resolved, and the whole team can insert it into any ticket and edit the placeholders before sending.

About saved replies

Acknowledge before you breach

First-response and resolution SLA timers with a breaching view show which messages still need that first acknowledgement, so you can send a holding reply before a target slips.

About SLA timers

Consistent across the team

Saved replies keep your acknowledgements worded the same way whoever picks up the ticket, so every customer gets the same calm, clear message.

All templates

Placeholders are a writing aid, not a feature

The square-bracket markers here are gaps for you to fill in by hand. Solves does not ship merge fields or an automation engine, so always replace each placeholder with the real detail and remove the brackets before you send.

FAQ

Acknowledgement and holding reply questions

What is an acknowledgement email in customer support?

An acknowledgement email is a short, prompt reply that tells a customer you have received their message and that a real person has it in hand. It does not have to solve anything; its only job is to stop the silence, set a realistic timeframe, and reassure the customer that nothing has fallen through the cracks. A good acknowledgement names what the customer asked about, says who or which team has it, and gives a date or window for the proper reply.

How quickly should I send an acknowledgement or holding reply?

As a rule, send the first acknowledgement well within your stated response time, ideally within a few business hours of the message arriving. The point of a holding reply is to buy honest time without leaving the customer wondering, so the sooner it lands the better. If you publish a first-response target, an acknowledgement should always beat it. On Solves, first-response and resolution SLA timers with a breaching view show you at a glance which messages are still waiting for that first reply.

Are the square-bracket placeholders a Solves feature?

No. The [customer name], [reference number] and [date] markers in these templates are illustrative gaps for you to fill in before sending. They are a writing convention, not merge tags or any automated field. Solves does not ship dynamic merge fields or an automation engine, so you replace each placeholder by hand, or paste a saved reply and edit it before the message goes out.

Can I ask customers to rate the support I gave?

You can ask in plain words at the end of a resolution email, and the closing templates below show how to do it warmly without pressure. Be aware that a built-in rating or satisfaction score is not part of Solves today; customer satisfaction scoring is on the roadmap rather than live. So treat any rating request as ordinary email copy for now: invite a reply or a short note rather than promising a one-click score button that does not yet exist.

How do I send these without retyping them each time?

Paste the acknowledgement you use most into a Solves saved reply, give it a clear name such as We have your message or Looking into it, and your team can drop it into any ticket and edit the details before sending. Saved replies keep the tone consistent across everyone who picks up the queue, and they can be scoped to one brand or shared across the organisation.

Save these as Solves saved replies

Paste the acknowledgements and holding replies you use most into saved replies, so your team writes them once and sends calm, consistent updates from one shared queue.

See saved replies Browse all templates