A customer asks when work will begin but the team has a queue status rather than a dependable completion estimate.
The useful bits
- Current queue status
- Factors you may accurately share
- A useful exchange confirms current impact and a reliable next update point.
Before you write
Use this example when a customer asks when work will begin but the team has a queue status rather than a dependable completion estimate. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Current queue status
- Factors you may accurately share
- Next status review time
An email you can adapt
The subject “Queue update for request [reference]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Queue update for request [reference] Hi [name], Your request is currently [verified queue status]. We cannot yet give a dependable start or completion time because [confirmed dependency]. [Owner] will review the status again by [date] and contact you with an update. If the impact on your work has changed, please describe the specific effect so the team can reassess it under the normal priority process. We do not want to give you an unsupported estimate. Best, [sender]
Check the boundary
Avoid translating a queue position into a promised time when duration and incoming priority work are uncertain.
What a useful reply should settle
A useful exchange confirms current impact and a reliable next update point.
Reassess through the established priority process and explain any confirmed change in status.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction