Shared Customer Inbox — Brief

A field guide for consulting firms / 01

Keep account context intact as conversations change hands.

A shared customer inbox can be more than a common address. Evaluate how it connects messages, people, and decisions across the long path from first inquiry to engagement.

Explore CRM workflows A practical reading guide, not a product tour

A useful history preserves the reasoning, not just the messages.

When a partner, consultant, and operations colleague each touch an account, a thread alone may not explain what was decided or who should act next.

Illustrative example

One account.
Several conversations.

Use this sample as a checklist for the context a shared inbox and contact record might need to hold.

People & roles

Identify the client sponsor, other participants, and the colleague responsible for the relationship.

Conversation

Keep relevant inquiries, meeting notes, and proposal exchanges connected to the right contact or account.

Decision context

Record the scope discussed, open questions, and any stated constraints without treating assumptions as commitments.

Next action

Make the owner, expected follow-up, and any handoff visible enough for another colleague to pick up the thread.

Follow one inquiry through the handoffs.

During CRM selection, walk through a realistic inquiry rather than relying on a feature list. Ask the people who handle the work to test where context appears and where ownership becomes uncertain.

01 / RECEIVE

Connect the message to a person

Consider how an incoming inquiry is associated with an existing contact and account. A familiar sender may be discussing a new project, while a new sender may belong to an established client.

Can the team distinguish a new contact from a new opportunity without losing the original message?

02 / ROUTE

Make responsibility explicit

Review how a message reaches the appropriate practice or relationship owner, including exceptions when that person is unavailable. Check how colleagues can see that an inquiry is already being handled.

What prevents a handoff from becoming two replies, or no reply at all?

03 / CONTINUE

Carry the context forward

Explore how a colleague can find prior exchanges, internal notes, and the agreed next step before responding. Long pauses between discussions make the quality of that record particularly important.

Can a new participant understand what happened without reconstructing the account from separate inboxes?

Examine the gaps between the boxes.

A shared inbox is only useful if its collaboration model matches the firm’s actual account responsibilities. Bring these questions to a product evaluation.

01

Visibility with boundaries

Discuss who needs to see client correspondence and internal notes. Check whether access can reflect the sensitivity of different engagements and the way teams are staffed.

02

Routing that tolerates exceptions

Ask how ownership is assigned, changed, and reviewed when an inquiry crosses practice areas or the usual relationship owner is away.

03

History that remains legible

Inspect how messages and notes relate to contacts and accounts. Look for a clear distinction between client communications, internal observations, and confirmed decisions.

04

Adoption in the working day

Ask consultants to trace a real handoff in a product evaluation. Note which details they must enter themselves and whether the resulting record is useful to the next colleague.

Return to the decision at hand.

Use these sections to structure a conversation with the people who own client relationships and the people who manage incoming work.