How to keep customers updated after they reach out
Three short texts answer the question every customer has: did anyone get this? Send one when the request arrives, one when a person takes it, and one when it is resolved, with a rating link on the last. Say who has it, keep each text to a line or two, and do not invite replies to a number nobody reads.
The three moments that matter
- Received: “We got your request. Our team has it.” It stops the second call.
- Taken: name the person who has it. A name turns a queue into a promise.
- Resolved: confirm it is done and ask whether everything is working.
Keep them short and plain
Start with your business name, so the text is recognized. Say what happened in one sentence. Leave out reference numbers and internal status words the customer never sees.
Do not invite replies you will not read
If nobody watches the number, say so: end each update with “Please do not reply to this text.” A reply that goes nowhere is worse than no text at all.
Ask for a rating at the end, once
Ask how it went only when the work is resolved, with one link and one question: is everything working? A low answer is a reason to call back, not just a number.
Do not send a text you would not stand behind
Some requests resolve in a way the customer should hear about from a person. Let whoever resolves the request see the text first and skip it when a call is better.