How to choose a shared inbox for a small support team
Build a practical evaluation brief for ownership, channels, escalation, self-service and the full recurring support bill.
Start with the enquiry your team loses today
Write down one recurring failure: two staff replying to the same person, an unanswered follow-up, a handover without context or a message trapped in an employee’s account. Choose the first problem the shared inbox must solve. Give it an owner and a measurable internal outcome, such as every open enquiry having an assigned person and a next action. Keep this outcome separate from a vendor’s marketing performance claim.
Map addresses, channels and ownership
List each support address and messaging channel, then record its owner, backup owner, opening hours and escalation route. Two email addresses are two channels of the same type; email plus SMS uses two types. Write which people answer, which approve, which only view and which maintain help articles. Price the appropriate access roles rather than giving every occasional reviewer a full agent seat by default.
Count a normal cycle and a busy cycle
Use a recent representative period to count people helped, conversations, messages and staff who need access. Those numbers are different. A repeat customer may create several conversations, while one conversation may contain many replies. Add a busy-season scenario and a staff-growth scenario. Record the billing-cycle reset and what happens at each cap, including whether the system pauses work, adds fees or requires an upgrade.
Run a handover that can fail
In an authorised trial, create a synthetic enquiry, assign it to one person and ask a second person to draft a reply. Check collision warnings, internal notes and the difference between a private comment and a customer-facing message. Reassign the work when the owner is away and make the deadline overdue. Inspect the escalation and the customer’s notification. The test should show who owns the next action without exposing internal notes.
Evaluate self-service and AI handover separately
Choose ten common questions and identify the approved answer, its owner and its review date. Search for the answer using the language a customer uses, including a misspelling. For AI assistance, include an unsupported question, an outdated answer and a request for a human. Record the event the vendor bills for: a conversation, resolution, seat or other unit. A lower unit price does not establish a higher resolution rate or less human work.
Ask for the complete retained-plan quote
Send the vendor a written brief covering staff roles, inboxes, channel types, help sites, rules, reporting, integrations and expected AI usage. Separate the subscription from messaging, extra resources, onboarding and optional tools. Compare the plan that remains after the trial and the standard renewal term. Keep currency and tax scope with the numbers. An annual monthly equivalent is a commitment over a year, not automatically a rolling monthly fee.
Plan the migration and ownership review
Test a sample export and decide what history must remain accessible. Set up forwarding and permissions in a controlled pilot, verify the reply-from address and check for forwarding loops before migrating the whole team. Assign ownership of rules, knowledge articles and integration credentials. Review unassigned work, overdue replies, repeat enquiries and avoidable manual handovers after rollout. Use measured results from your own operation to choose the next improvement.
Put the guide into practice
Explore help desk tools, then compare your shortlist.
Explore the category →