In this guide
Define states in plain languageName the next dependencyAvoid unsupported deadlinesClose with the specific resultA status update should describe what is known now and what happens next. “Done” can be misleading if it means only that a request was sent. Define a small set of states that match the evidence and keep payment state separate from account-action state.
Define states in plain language
Requested means the intended action has been recorded. Awaiting information means a specific required answer is missing. Submitted means the request reached the relevant party through the chosen route. Confirmed completed means the responsible party has confirmed the action’s result. Use your actual workflow; do not imply a technical delivery guarantee from a chat’s sent mark.
Name the next dependency
A useful update says what is pending and who is responsible. For example: “The order reference is recorded; we are waiting for provider confirmation of the resulting account date.” This is an illustrative wording pattern. Avoid “almost ready” when you do not have evidence about remaining work or timing.
| Less useful | More precise |
|---|---|
| Payment done | Payment reference received; seller confirmation pending |
| Renewal sent | Renewal request submitted for the named account |
| All fixed | Provider confirmed the stated action; customer observation still requested |
Avoid unsupported deadlines
Give an estimated time only when there is a reliable applicable source and explain its status. Do not turn a past fast response into a universal promise. If a promised update time is your own commitment to communicate, distinguish it from the provider’s completion time.
Close with the specific result
Record what changed, which account it concerned and what confirmation supports it. If the customer reports an unresolved symptom, keep that issue open rather than using the completed order state to erase it. Clear states let a colleague continue the case without guessing whether another action is needed.
Questions about this guide
Can I tell a customer that a provider will reply within my own update interval?
Only if that provider deadline is actually established for the case. You can commit to sending your own progress update at a stated time, but that is a separate promise. Keep the distinction clear so the customer knows which event is expected.