Shared inbox or ticketing system? The answer is usually about state, not email.

FOUNDATION

Define the support promise before configuring the inbox

A shared mailbox solves access. A collaborative inbox adds assignment and collision awareness. A ticketing system adds durable state, identifiers, structured workflow, automation, reporting, and retention. Choose the smallest model that still answers who owns the request and what happens next.

WORKFLOW

Build the smallest reliable operating loop

Map the lifecycle from new to open, on hold, and resolved. Decide how replies reopen work, whether unread state is personal, how internal notes differ from customer mail, how recipients are managed, and which events should notify the team.

PITFALLS

Test the edge cases that break team trust

Avoid adding ticket numbers without reliable threading, statuses nobody uses, assignments hidden from the list, or reports built on ambiguous state. A complicated taxonomy does not fix a workflow the team cannot see.

CHECKLIST

Validate the customer and agent experience together

Send a new request from an external address, verify ticket creation and acknowledgement, assign it, open it from two agent accounts, add a private note, change recipients, paste an image, attach a file, reply, answer from the customer mailbox, resolve the ticket, delete a disposable test, and confirm a later sync does not recreate it. Record the expected owner and outcome for every step.