Set up launch email after securing the domain and account recovery. Provision users and role addresses, configure authentication and test the website’s notification route. Publish contact details only after receiving and replying work. Assign an owner for each inbox so launch enquiries do not arrive in an account nobody monitors.

Consistent email identity requires accurate display names, useful signatures and clear role addresses. Keep the design readable on mobile and when images are blocked. Assign ownership and update it during staff changes. The objective is recognisable, reliable communication rather than large decorative signatures or unsupported claims about response rates.

Synchronized messages on several devices are not automatically independent backups because deletion can propagate. Verify the provider’s recovery and retention scope, then decide whether separate protection is needed for the business’s requirements. Test the chosen recovery route and document what it covers, including any non-mail data exclusions.

An email-provider handover should inventory users, aliases, folders, devices and non-mail data. Run a representative pilot, plan record changes and verify destination workflows before ending the source service. Shared resources and calendar permissions may need separate work. Keep the final configuration understandable to the receiving administrator.

Email storage and archiving should reflect information needs, quota and an informed retention process. Do not invent a universal legal retention period. Check current export, restore and access capabilities before depending on them. Remove redundant data deliberately, and keep historical business information accessible to authorised people during handovers.

Reliable form email should use a sending service authorised for the business domain. Keep the From identity under business control and use Reply-To for the visitor where appropriate. Verify provider limits and test delivery end to end. A form’s success notification alone does not prove receipt in the destination inbox.

Phishing risk needs both account controls and a verification workflow. Enable available multifactor protection, teach staff to check high-impact requests independently and provide a reporting route. An authenticated message can still contain a dishonest request. Review access and evidence if compromise is suspected rather than simply deleting the email.

When receiving stops, compare a direct server or webmail test with the affected client. Check account status, quota, spelling and authoritative MX records, then use bounce or delivery evidence. Do not change DNS repeatedly without a diagnosis. Restore the failing stage and test the original message route again.

Organise sales and support mail around responsibility and continuity. Define who triages messages, how replies are coordinated and when escalation happens. Distinguish aliases from shared inbox functions in the actual plan. A role address is valuable when the team can operate it reliably during absence and handover.

Removing a former employee’s access can require session revocation, delegated-access review, connected-app checks and device follow-up. Preserve business data under an informed process before deleting anything. The available controls depend on the platform and licence. Record who now owns the account’s work and recovery arrangements.