Handle a shared-inbox message with no clear client match

Where the extra work starts

Resolve the match before routing the work so staff do not build a response or spreadsheet around the wrong engagement.

Once someone owns the email, the invoice PDF may still need to be keyed into Excel. Download the attachment through your approved process, then use ParseMill to extract, review and export it. Shared-inbox routing and replies remain with your existing email tools.

Keep the message in a restricted unassigned queue while establishing the relationship. This is an administrative routing check, not a request to collect extra identity documents by email.

A practical way to get it right

Inspect the actual sender and reply addresses, the entity named in the message and any existing request reference. Compare these with the firm's approved contact record and relevant earlier correspondence. Record which evidence agrees and which conflicts. Do not treat a familiar signature block as independent confirmation.

Where the relationship is uncertain, contact the known engagement owner or use an established contact channel already held by the firm. Ask a narrow question: which entity and existing request does this message concern? Do not forward the unexplained attachment to multiple client teams to see who recognizes it.

Assign an owner for resolving the match and a next check time. Once confirmed, record the client reference and confirmation evidence, then route only the information necessary for that work. Preserve the original sender details rather than replacing them with the inferred client name.

Microsoft: Share and access another person’s mailbox describes permission-based mailbox access. Check the receiving team’s access before routing an uncertain sender’s content.

What this looks like on a real task

Synthetic example. The people, references and figures below are invented to demonstrate the method.

The first row has two consistent identifiers. The other rows do not become confirmed merely because a person is recognizable. Copy the evidence and decision columns into a triage record; add a named checker and date. For M54, the known relationship may be genuine while the selected client record is still wrong. Identity and work destination are separate checks.

Catch the cases that create rework

If the message asks for sensitive information before the match is resolved, retain the request for the authorized reviewer and do not include client-specific details in a speculative reply. If the sender cannot supply a usable reference, ask the established client contact to clarify through the agreed route.

A routing correction should be visible to anyone already assigned the work. Remove the mistaken action from their active queue with a cross-reference rather than silently leaving two versions in circulation.

Replies from an Outlook shared mailbox can use the shared address, as Microsoft: Open and use a shared mailbox explains. Select the appropriate mailbox only after confirming the client relationship.

Decide whether the change is worth keeping

Check that the final client assignment has a reason someone else can follow. Review unresolved messages by age and next action, not by familiarity of the sender's name. A successful process leaves confirmed messages with the correct owner and uncertain messages with an active investigation; it does not force every message into a client record by the end of the day.

The workflow audit checklist can help record the observed friction before considering a change.