A colleague is expected to use company email but provisioning has not yet completed successfully.
The useful bits
- Verified provisioning status
- Responsible administrator
- A useful update makes the current status and temporary coordination route unambiguous.
Before you write
Use this example when a colleague is expected to use company email but provisioning has not yet completed successfully. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Verified provisioning status
- Responsible administrator
- Approved temporary communication route
An email you can adapt
The subject “Update on your company mailbox setup” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Update on your company mailbox setup Hi [name], Your company mailbox setup is still in progress, so please do not assume that [address] is ready to receive work messages. [Administrator] is checking [confirmed dependency]. Until we confirm activation, use [approved alternative] for coordination and keep sensitive information within approved systems. We will provide another update by [time]. Once setup is complete, we will ask you to confirm access without sharing your password or codes. Best, [sender]
Check the boundary
Do not send live customer information to an unconfirmed address or ask a starter to bypass access controls.
What a useful reply should settle
A useful update makes the current status and temporary coordination route unambiguous.
After activation, test the intended workflow and withdraw the temporary arrangement where appropriate.
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