Route a message that concerns two clients

Where the extra work starts

Separate the actions and evidence by engagement so each owner receives the right context without unrelated client information.

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.

Start with the entity named for each requested outcome. If the message says “both companies” without identifying them clearly, resolve that ambiguity before attaching documents to client records.

A practical way to get it right

Create an entity-action map with one row per distinct outcome. Record the entity reference, requested task, relevant attachment and receiving owner. Verify that each recipient needs and is permitted to see the context you supply; do not forward the whole mixed-client chain by default.

Keep a coordinator for any consolidated client response. The coordinator should obtain outcomes from the separate owners and avoid declaring the whole message complete when only one entity's work is finished. If one action depends on the other, name that dependency explicitly.

Store evidence in the approved entity locations and link the source message through permitted access. Where a document genuinely covers both entities, ask the engagement owner how to maintain the shared evidence rather than duplicating it without a clear version owner.

Microsoft: Share and access another person’s mailbox makes mailbox access permission-dependent. Check each assignee’s permitted context before distributing a message containing two entities.

What this looks like on a real task

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

There are two operational actions and a communication responsibility. Cedar can finish while Birch remains open. Copy the entity-action map and add next-check dates; do not count the acknowledgement as a third completed client requirement. If the attachment names are ambiguous, the map should show that uncertainty rather than assigning files by alphabetical order.

Catch the cases that create rework

If an assignee discovers the wrong entity after work has started, stop the affected routing and notify the coordinator. Correct the references and record what needs rechecking. Avoid silently moving the file while leaving earlier decisions attached to the wrong client.

A shared contact does not imply identical access rights across teams. If a recipient cannot view the mixed source message, provide a reviewed extract or separate instruction through an approved route, preserving a traceable source reference.

Microsoft: Reply to or forward an email message explains that forwarding includes original attachments. Remove unrelated material from any permitted handoff after reviewing the actual outgoing copy.

Decide whether the change is worth keeping

Ask each owner to identify their entity, evidence and completion condition without relying on the message subject. Check that the client-facing response accurately reports both outcomes and any remaining dependency. A useful review counts entity-specific unresolved actions; one email with two clients must not disappear merely because one team has replied.

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