A business address such as support@ should remain usable when an individual is absent or leaves. Forwarding everything to one person’s private inbox can hide the conversation from the next operator and complicate access removal. The right arrangement depends on the provider and work, but its ownership and responsibilities need to be explicit.
Separate the address from the person
Confirm the provider’s supported shared/delegated mailbox model, licences, storage limits and access requirements. Do not assume every plan permits the same functions. Give each authorised person their own identity and appropriate permission rather than sharing a common password. Check how sent items, replies and audit records are retained so the business can understand who did what.
An alias is not necessarily a separate inbox. Forwarding is not necessarily a recoverable shared record. A mail group may distribute messages without giving anyone responsibility for completing the work. Demonstrate the actual receiving, assignment and reply journey before calling it a support process.
Make responsibility visible
Decide who checks the address, at what genuinely staffed times and what happens during absence. Define how an enquiry is acknowledged, given an owner and followed up without duplicate replies. An automated acknowledgement is an operational signal, not proof a person has read or accepted a support request. Do not advertise a response promise based only on the presence of an email address.
Keep a minimal customer/project reference and a current status in the appropriate controlled record. Avoid pasting full confidential messages into unrelated projects or a broadly visible dashboard. If a future customer portal records communications, that must be an authorised customer-safe projection; it is not created automatically by configuring a shared mailbox.
Check security and exit
Protect the underlying identities, administrator recovery and delegated access with suitable authentication. Review forwarding, external delegates and rules, especially after an account incident. Ensure removal of one operator does not destroy the business’s ability to recover the mailbox or locate relevant correspondence. Retention and deletion need a business/data-protection policy, not unlimited storage by default.
Test with synthetic messages or authorised controlled correspondents: receiving, replying from the intended identity, locating sent items, absence cover and revoking a delegate. Verify what the recipient actually receives rather than trusting a local compose screen. Record provider-specific limitations and support ownership.
The smallest useful arrangement may be a supported shared mailbox plus a clear manual ownership routine. A paid ticketing system is justified only if volume, routing or service commitments require it. Adding software cannot fix an inbox which nobody is actually authorised or available to handle.
Sources and review
Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.
Next review: 4 May 2027