Imagine a customer emails your shop about a missing order. Two staff members reply with different promises. A third, who left last month, still knows the password to the account. The problem is not that the team needs a more memorable password; it needs an inbox with named access and a way to assign ownership.
For a Nigerian small business that handles orders by email alongside WhatsApp or social messages, a shared email address can make the business look organised. But a single shared login also makes offboarding, two-step verification and accountability harder. The goal is one public address with individual staff access, not one credential copied into several phones.
Choose the right type of shared workflow
If your organisation uses Google Workspace, Google Groups Collaborative Inbox can receive messages through a group and let members assign conversations or take them for themselves. This is a Groups workflow, not simply several people signing into the same Gmail account. An administrator must enable the required Groups settings and choose permissions appropriate to the team. Check how external customers can email the address before advertising it publicly.
If you use Microsoft 365 for business, a shared mailbox lets administrators grant people access to a common address while they use their own accounts. Microsoft says a shared mailbox is not designed for direct sign-in: the account associated with it should have sign-in blocked. Check your licence and capacity requirements against current Microsoft guidance before assuming a particular configuration is free or unlimited.
These are not identical products. Choose based on the mail system you already administer and the actual workflow you need. If you only have personal free Gmail accounts, do not assume the Workspace administrative features described here are included. A full help-desk product may be justified later if you need service-level reporting or multichannel ticketing, but start by defining the problem.
Set up a small, accountable process
Start with one address customers will recognise, such as help@yourdomain. Name one administrator and at least one backup administrator. Give each worker their own account and the least access needed. Require strong individual authentication, preferably with multi-factor protection supported by the provider. Do not email a common password to the team.
Agree on simple ownership rules before the inbox goes live: who checks it, who assigns a new request, who replies, and what happens when the first owner is absent. Test the process with a non-sensitive message from an outside address. Confirm that replies show the intended business identity, arrive back at the customer, and do not cause two agents to send conflicting answers. A short written template can help with receipts and response times, but staff must check the facts of each case.
Keep customer data in the approved mail system rather than copying identification documents into personal messaging apps. Avoid collecting more information than a support task requires. If a customer sends sensitive account information, limit access and follow the organisation’s retention and incident procedures. Do not ask customers for passwords, one-time codes or full payment-card details.
The offboarding test
Now ask the question that exposes a bad setup: if one team member leaves tomorrow, can you remove their access without changing everyone else’s password? With properly administered individual accounts and group or shared-mailbox permissions, you can revoke that user’s access and check the remaining team. Also review forwarding rules, devices, delegated access and any external integrations. Keep business records according to your retention policy; do not delete a shared history merely to remove one employee.
When a shared inbox is not enough
As message volume grows, missed ownership or duplicate replies may persist even after access is fixed. Then consider a dedicated ticketing workflow with assignment, status and audit history. Judge it by whether the team actually answers customers accurately and securely, not by the number of dashboard features on a sales page. For a small team, clear ownership and reversible access are the most valuable first upgrades.
Frequently asked questions
Can everyone simply sign in to support@? That defeats individual accountability and makes departures harder to manage. Use supported delegation, a collaborative group or a shared mailbox instead.
Is Google Groups the same as a Gmail shared mailbox? No. It is a group-based conversation workflow with its own permissions and interface.
Does a Microsoft shared mailbox need a separate password for staff? Staff should use their own granted accounts; Microsoft advises blocking direct sign-in to the shared mailbox account. Check current licensing conditions for your scenario.
Continue reading on Tech Embed
Topic hub: Explore more in Cybersecurity in Nigeria.
Sources
Google Workspace: use a group as a Collaborative Inbox; Google Workspace: configure Collaborative Inbox; Microsoft 365: about shared mailboxes. Provider instructions checked 24 September; interface and licensing terms may change.
