Connecting a shared mailbox to a CRM is a decision about how a team handles correspondence. Before enabling synchronisation, decide which messages become CRM records, who owns the resulting work and where replies should be sent. Those decisions matter more to daily operations than whether a connector can display an inbox inside another screen.
Choose the purpose of each mailbox
A sales enquiry address, support address and accounts address carry different kinds of work. Inventory the shared mailboxes and describe their intended purpose. Identify messages that should create a new lead or ticket, messages that should attach to an existing record and messages that should remain outside the CRM workflow.
Choose between capturing everything in a defined mailbox, capturing selected folders or letting staff log selected messages. Each approach creates a different operating burden. Broad capture needs reliable filtering and review. Selective capture needs clear staff responsibility. Do not adopt a universal rule before examining the actual mixture of messages in each mailbox.
Decide where the team works and replies
If staff reply from both Outlook and the CRM, define how each reply becomes visible in the shared history. Specify the intended sender identity, where sent copies should appear and who can send as the shared address. Ask the implementer to demonstrate those behaviours with the actual mailbox configuration rather than relying on a generic email integration demo.
Keep message state separate from work state. Marking an email read does not mean someone owns the enquiry or has answered it. Use a CRM assignment and next action for accountable work. Likewise, moving a message to an archive folder should not silently close the associated ticket unless that behaviour has been deliberately designed and tested.
Verify the permission model for shared access
Microsoft Graph supports delegated permissions for reading or writing shared and delegated folders. However, Microsoft states that Mail.Read.Shared and Mail.ReadWrite.Shared do not support change-notification subscriptions for those folders; its documented subscription approach uses application Mail.Read permission. See the shared-folder access documentation.
That distinction is a reason to ask precise questions, not a recommendation to grant broad permissions automatically. Have the administrator review the chosen access model and resource scope. Confirm how the connector operates when a named employee is absent or leaves, and who can reconnect it if authorisation stops working.
Define matching before importing history
Decide how a message is associated with an account, opportunity or ticket. A sender can have several active projects, and a forwarded email may arrive from an internal colleague rather than the customer. Give ambiguous messages a review queue. Incorrectly attaching a message to the wrong customer can be harder to notice than leaving it temporarily unmatched.
Choose whether past correspondence is required and how much is useful. A pilot with a limited date range can expose matching problems before a large history import. Record the import boundary and distinguish historical messages from fresh enquiries so old mail does not trigger new assignments, customer acknowledgements or overdue-work alerts.
Worked hypothetical example: one mailbox, two work types
A fictional equipment supplier receives sales enquiries and delivery questions at a shared information address. The team agrees that a request for a new quotation creates a lead, while a question about an existing order enters an operations queue. Unclear messages go to a duty coordinator who chooses the destination and remains responsible until an owner accepts it.
A buyer emails about two separate orders in one message. The coordinator links the correspondence to the account and creates two follow-up tasks with clear order references. The system does not guess a single order from the sender's address. A colleague then forwards the same message internally; it is reviewed as related correspondence rather than automatically creating another lead.
During testing, a user archives the original message in Outlook. The CRM's assigned work remains open until the responsible coordinator records the answer. This hypothetical scenario tests the separation of email handling and business responsibility. It does not claim a measured improvement or describe a real implementation.
Test identifiers when messages move
Microsoft explains that ordinary Outlook item identifiers can change when items move. Graph offers an optional immutable identifier format that remains stable while an item stays in the same mailbox, with exceptions such as movement to an archive mailbox. The details appear in Microsoft's immutable identifier guidance.
Ask how the connector identifies a previously imported message after a folder move. Test its behaviour rather than assuming the feature name guarantees duplicate prevention. Include archive movement and a copied message in the test set. The goal is a dependable association between the mailbox item and CRM activity, with understandable handling when that association changes.
Set visibility for bodies, attachments and internal notes
Mailbox access and CRM access need separate decisions. Determine which CRM roles can read captured correspondence and attachments. A person who can view a customer name does not necessarily need every email associated with that customer. Check whether replies include previous internal discussion or attachments that were intended only for colleagues.
- Preview the sender, recipients and attached files before sending.
- Test a reply from both supported working interfaces.
- Check an inaccessible account using an ordinary CRM user.
- Verify that a connection failure leaves visible unprocessed work.
- Confirm who reviews unmatched and failed messages each working day.
Launch one mailbox with explicit acceptance checks
Start with a mailbox whose purpose and owner are clear. Require correct capture, assignment, reply visibility and recovery from a disconnected account before widening the rollout. Use the CRM access review guide to check the resulting visibility. Explore Visuosofts CRM development or contact Visuosofts with your mailbox purposes and examples of messages that are difficult to route.