A reply needs to be visible to the team
A customer asks whether anyone has answered yesterday’s message. One colleague remembers replying; the person covering the mailbox cannot find the response. Before sending a second answer, establish where the first message was saved and whether the team is looking in the right place.
Microsoft documents an Exchange Online scenario in Outlook 2016 and later where delegated messages sent as, or on behalf of, a shared mailbox are saved in the sender’s own Sent Items instead of the shared mailbox. That gives support a specific behaviour to investigate. A missing shared-folder copy alone does not establish that no reply was sent.
Check the actual sending route
Our suggested check is an agreed test message to an internal test recipient, with an unmistakable subject and no customer information. Record which Outlook client was used, the sending identity and the time. Ask the sender where the copy appears, then ask another authorised mailbox member whether they can locate it through the normal team workflow.
In a fictional bookings team, the morning coordinator can find the test reply in their own mailbox but the afternoon coordinator cannot find it in the shared view. They document that result for the administrator rather than assuming the recipient needs another email. Keep any check of a real customer thread within the team’s approved access arrangements.
Give the administrator a precise change request
Microsoft describes mailbox settings that save a copy in the shared mailbox, with separate options for Send As and Send on Behalf. It says this mailbox-side method is the applicable option for new Outlook. Ask the Exchange administrator to review the current configuration against the sending route you actually use.
Include the observed result and the behaviour the service owner wants. Avoid distributing an old registry workaround across laptops without that review. Agree a limited change and repeat the test with the affected client before extending it. This briefing is a support workflow, not an instruction to change every shared mailbox identically.
Make the handover usable
After an authorised change, have the covering colleague locate the new test reply without help from its sender. Check that the recipient received the intended message, and record any remaining mismatch. Do not resend real customer mail as a way of testing a folder setting.
Update the team’s short handover note with where to check outgoing correspondence and who investigates an unclear case. If the trail still cannot be followed, keep a named support action open. The outcome you want is a colleague able to establish what was sent before deciding whether another response is needed.
Sources
Practical suggestions in this article are editorial recommendations. The source supports the guidance attributed to it.
- Microsoft Learn · Shared mailbox sent items ↗
Checked 19 October 2026
Something needs correcting?
Get in touch to explain which claim needs attention and share the supporting source.