One account manager replies to a renewal question from the agency's shared mailbox. The next person opens that mailbox, cannot find the reply and starts drafting another response. Before resending, find out whether the message is missing or simply stored somewhere the colleague did not check.
For a small insurance agency using Microsoft 365 and Outlook, the sender address, mailbox permissions and sent-copy settings are separate parts of the workflow. A shared inbox alone does not establish a shared record of every outgoing message.
Check the sender and the folder first
Ask the person who sent the reply to check the message's From address and their own Sent Items folder. Then check Sent Items beneath the shared mailbox itself. These are different folders, even when they appear in the same Outlook window.
Microsoft documents that messages sent from a shared mailbox are, by default, saved in the sender's Sent Items rather than the shared mailbox's Sent Items. That is a useful starting explanation, not a diagnosis for every missing message.
If a message copy is found, record its subject, approximate time and which mailbox contains it. Use the agency's approved process for investigating client correspondence. A saved sent copy by itself does not prove delivery to the recipient.
Confirm that this is actually a shared mailbox
A shared mailbox, a distribution list and an employee mailbox with delegated access are not interchangeable setups. Have the Microsoft 365 administrator confirm what the agency is using before applying a fix intended for shared mailboxes.
Also distinguish opening a mailbox from sending through it. Microsoft's Exchange documentation separates Full Access from Send As and Send on Behalf permissions. Someone who can read the inbox may still need the appropriate sending permission.
Keep individual sign-ins. Microsoft says shared mailbox accounts are not intended for direct sign-in and should remain blocked from signing in. Sharing a mailbox password is not a substitute for correctly assigned access.
Ask the administrator to review sent-copy settings
For a Microsoft 365 shared mailbox, Microsoft's admin guidance describes editing Sent items settings so the team can see copies of replies in the shared mailbox. The administrator should select the options appropriate to the agency's sending method.
This is an Exchange mailbox configuration task. Installing Intune or changing the laptop's device policies is not the direct fix for this setting.
If the administrator uses Exchange PowerShell, Microsoft's troubleshooting article distinguishes MessageCopyForSentAsEnabled from MessageCopyForSendOnBehalfEnabled. The correct choice depends on how people send. Do not apply a command copied from a forum without confirming the mailbox and intended behavior.
Microsoft also distinguishes the server-side method from a classic Outlook registry workaround. Its documentation says only the server-side method applies to new Outlook. Start with the documented method for the client's actual Outlook version.
Test with an internal message, not client records
After an authorized change, send a harmless internal test from the shared address. Use an obvious subject such as “Shared mailbox workflow test” and include no policyholder information or attachments.
Have another authorized colleague check the shared Sent Items folder. Confirm the test's From address, where the copy appears, and whether the second person can open it. Test the Outlook clients the team actually uses rather than assuming one successful desktop test covers every device.
Write down the result and the agreed workflow. Treat the change as tested only when it produces the intended behavior for the agency's setup.
If the new test still fails, narrow the problem
Record whether the issue affects one person, one Outlook client or everyone. Ask the administrator to compare the folder in Outlook on the web with the desktop client. A difference is a useful clue about the client view or synchronization, not proof that the mailbox configuration is wrong.
If sending itself fails, investigate that separately from where sent copies are stored. If only older messages are absent, do not assume a setting changed today will recreate historical copies. Agree on any historical-message work separately.
Make the handoff clear
Consistent sent copies can help colleagues see earlier replies, but they do not assign an owner to the next action. Agree on who handles the conversation, how reassignment is recorded and when staff should check before sending a second response.
This workflow is not a substitute for the agency's approved retention, records or client-data requirements. Keep those decisions with the responsible business owner and administrator.
Get help with the mailbox workflow
Full Metal Architect helps Maryland professional firms and other small businesses troubleshoot Microsoft 365 and everyday office technology. Get IT Help with your Outlook version, whether the mailbox is shared, and whether the issue affects one person or the whole team.
Do not include passwords, policy numbers, client email bodies or attachments in the contact form. FMA discusses access, scope and cost before paid work begins. No managed IT contract is required.
Official references
Microsoft: Configure shared mailbox settings
Microsoft: Messages sent from a shared mailbox are not saved to its Sent Items folder
Microsoft: Open and use a shared mailbox in Outlook
Microsoft: Shared mailbox permissions in Exchange Online
Microsoft: About shared mailboxes
Documentation checked October 31, 2026. The applicable steps depend on the actual mailbox, client, permissions and environment.
