Shared Inbox or CRM? Organise Website Enquiries Before They Go Missing

If two people answer the same website enquiry, the problem is not simply email delivery. The team needs a shared understanding of who owns the reply and whether the request is still open.

Start with the level of coordination required

A shared inbox can suit a small team handling straightforward conversations. A CRM becomes more useful when enquiries need stages, activities, service details and reporting across several people. The choice depends on the process, not the label on the software.

Keep one operational queue

Copying every message into personal inboxes and a CRM can create competing versions of the work. Decide where staff assign, answer and close requests. Customer-facing replies should still use an appropriate business identity and preserve the conversation history.

• Define assignment and reassignment rules.
• Distinguish unread from genuinely unresolved.
• Keep internal notes separate from customer messages.
• Make absence cover possible without shared passwords.
• Test how attachments and replies are retained.

Compare two ordinary enquiries

Use a simple price question and a request requiring several follow-ups. Ask staff to handle both in the shortlisted setup. If the CRM demands many fields that nobody uses, simplify it. If the inbox cannot show who should act next, an explicit task workflow may be necessary.

Judge the result by follow-through

Track missed assignments and unresolved conversations, using actual records rather than a vendor's generic productivity claim. Document how staff access is removed when someone leaves. A useful system lets the next person continue the conversation without asking the customer to repeat everything.