# Salesforce and Outlook: which emails actually land on the opportunity

https://salesbond.app/blog/salesforce-outlook-email-sync-opportunities/
Published: 2026-10-08 · Updated: 2026-10-26

In Salesforce, emails sent or received through a connected Outlook mailbox, whether Einstein Activity Capture picks them up or a rep logs them with the Outlook integration add-in, are matched to records by email address, so a contact without the right address leaves the email without a deal ( [Nektar: Salesforce email integration guide](https://nektar.ai/salesforce-email-integration-email-sync-complete-guide/)). The settings page will not tell you whether that works. To check it, open three recent opportunities and look for the last customer thread on each. If it is there on all three, the sync is doing its job. If one is empty, you have found the hole, and it is older than this week.

## Install is the easy part

Most of what ranks for “Salesforce Outlook integration” is a setup walkthrough. Weflow’s guide is a good example: it takes you from the add-in to the connected mailbox and stops there ( [Weflow: Salesforce Outlook integration](https://www.weflow.ai/blog/salesforce-outlook-integration)). That is fair, because setup is what the admin is asked to do. It takes an afternoon, somebody ticks a box in the the rollout plan, and the team is told that email is now “in Salesforce”.

What nobody writes down is that the integration does not decide where an email goes. The data does. Once the mailbox is connected, Salesforce relates emails and calendar events to accounts, contacts, leads and opportunities, and emails you send from Salesforce go out through your own mailbox ( [Salesforce Sales Productivity guide, PDF](https://resources.docs.salesforce.com/214/latest/en-us/sfdc/pdf/sales_productivity.pdf)). The verb there is “relates”. Relating needs something to relate to. A contact that was never created, an address that changed when the buyer moved jobs, a reply from a colleague nobody added to the account: each one is an email that arrives in the inbox and never reaches the deal.

We think this is the part a sales manager should own, not the admin. The admin can prove the connection works. Only the manager can see that the pricing thread on a renewal (call it Hendriks; the deals in this article are made up) is not on the Hendriks opportunity, and that six months from now, when the rep has left, nobody will know the discount was already promised.

## How an email finds its opportunity

The path is short. Salesforce reads the addresses in the From, To and CC fields and looks for records that carry them. Contacts are the main link, and the match is built on email addresses rather than on names or company domains ( [Nektar](https://nektar.ai/salesforce-email-integration-email-sync-complete-guide/)). If the address is on a contact, the email reaches the contact.

Whether it then reaches the right opportunity depends on how that contact is tied to deals. In Salesforce that tie is usually an Opportunity Contact Role: the record that says this person plays a part in this deal. A contact with no role on the opportunity is a contact the email can find and a deal it can’t. And an account with several open opportunities is exactly where, by the same guide, matching gets harder; the email may end up on the account or on the wrong deal.

![Path of an Outlook email to a Salesforce opportunity: address on a contact, then a Contact Role on the deal](https://salesbond.app/wp-content/uploads/2026/10/salesforce-outlook-email-sync-opportunities-2.png)

When the email does not find the deal, the reason is almost always one of these:

- The contact exists but the **Email** field is blank, still holds the address from the buyer’s previous company, or doesn’t match the second address the customer sometimes writes from.
- Someone new joined the thread on the customer side and was never added as a contact. Their emails have no home.
- The rep’s side is the problem. Einstein Activity Capture syncs only mail tied to the primary address on the rep’s Salesforce user and doesn’t support aliases ( [Salesforce Help: Considerations for Setting Up Einstein Activity Capture](https://help.salesforce.com/s/articleView?id=sf.aac_limitations.htm&language=en_US&type=5) ), and Nektar lists shared mailboxes as a known limit of the Microsoft add-ins. A reply sent from an alias, a shared inbox or a second mailbox never enters the sync.
- The account has three open opportunities and the email landed on the account, or on the wrong one of the three.

Notice that none of these is a sync failure. The connection is green on every one of them. That is why the settings page cannot tell you about the hole and the deal can. Extensions that write to opportunities need the same scrutiny, and here is a [five-step check for extensions that write](https://salesbond.app/blog/salesforce-chrome-extensions-crm-writes-audit/).

## Einstein Activity Capture vs logging by hand

There are two ways an Outlook email ends up in Salesforce, and it is common to run both without anyone having chosen. Einstein Activity Capture (EAC) watches the connected mailbox and adds matching emails and events by itself. The Outlook integration add-in lets the rep pick an email and log it to a record from inside Outlook. They solve different problems.

- **Auto-capture** catches what the rep would have forgotten. Nobody has to remember to log, which matters, because the reasons reps skip the CRM are rarely laziness; we went through them in why reps don’t update the CRM. The price is that capture is only as good as the address match above, and the rep never sees the moment the email went to the account instead of the deal.
- **Logging by hand** puts the email exactly where the rep chooses, including on the right one of three opportunities. It depends on the rep choosing, every time, and on the days they are closing they will not. HubSpot teams face the same trade-off, covered in [logging emails with the HubSpot sales extension](https://salesbond.app/blog/hubspot-sales-extension-crm-logging/).
- **Both at once** is where many teams end up. The risk is that everyone assumes the other mechanism covered the gap. Salesforce also warns that logging a captured email with the add-in’s Log Email button can create a duplicate on the timeline ( [Salesforce Help: Considerations for Sync Email as Salesforce Activity](https://help.salesforce.com/s/articleView?id=sales.eac_email_activity_considerations.htm&language=en_US&type=5) ).

One practical note before you pick. EAC Standard comes with most Sales Cloud editions, but it is capped at 100 users, and going past that takes a paid license ( [Trailhead: Outlook integration](https://trailhead.salesforce.com/content/learn/modules/outlook_integration/outlook_integration_unit_3)). Check your edition and licenses before you plan around it.

## What your report will not show

Here is the trap for a manager who runs the team from an activity report, and whether you are in it depends on one setting.

Salesforce now offers a mode called Sync Email as Salesforce Activity. With it on, captured emails are stored as regular Salesforce activity records, which reports, flows and search can use. Without it, captured email shows on the activity timeline but isn’t saved as email records, so reports can’t see it; for setups made before Summer ’25, Salesforce recommends migrating to the new mode ( [Salesforce Help: Using Emails Without Sync Email as Salesforce Activity](https://help.salesforce.com/s/articleView?id=sales.aac_guidelines.htm&language=en_US&type=5)). So ask your admin one question: which mode is our org on?

If its the older one, your “emails sent per rep last week” report counts only what reps logged by hand. A rep who relies on auto-capture can look idle in it while her inbox is full. If it’s the new mode, the report is closer to the truth, but it still counts emails, not deals: an email that matched the account instead of the opportunity is counted and still missing from the deal.

Either way the advice is the same. Do not judge a rep’s activity from the email report alone, and do not treat a quiet report as proof that a deal is quiet. Open the deal.

That is also why we do not recommend a reporting fix for this. We recommend a habit.

## A three-deal check you can do on Friday

It takes twenty minutes and needs no admin rights.

1. Pick three opportunities that changed stage this week or had a customer meeting. If more than three qualify, take the three with the most money on them.
2. Ask each owner one question: “What was the last email you exchanged with the customer on this deal? Subject line is enough.” Write the three subject lines down.
3. Open each opportunity and look for that email. There are three possible answers, and you record which one you got: on the opportunity; on the contact or account but not on the opportunity; nowhere in Salesforce.
4. For each “nowhere”, open the contact and check the **Email** field against the address the customer actually wrote from. For each “contact but not opportunity”, check whether that contact has an Opportunity Contact Role on the deal at all.

![Example check sheet for three made-up deals showing where each last customer email was found, with two fixes](https://salesbond.app/wp-content/uploads/2026/10/salesforce-outlook-email-sync-opportunities-3.png)

Say the check turns up two clean deals and one “nowhere”, because the buyer replied from a personal-looking address her company uses for contractors. The rep knew. Salesforce did not. The fix takes five minutes: the address goes on the contact, the thread gets logged by hand, and the next captured email lands on the deal on its own.

Then say the rule out loud on Monday, in one sentence, so it survives the rep’s next busy week: an email to a customer must be able to find its deal, which means the contact exists, the address is the one they actually write from, and the contact has a Contact Role on the opportunity. Say it the same way every time. It pairs well with the minimum we ask for in [call notes](https://salesbond.app/blog/sales-call-notes-minimum/): one line about what was said, on the record where the next person will look for it.

If the check keeps turning up the same hole this is where we would stop doing it by hand. We build SalesBond, a sales management layer on top of the CRM a team already uses. Its Deal Health checks run more than 20 rules across activity, progression and data, and an opportunity with money on it and no logged history is one of the things they flag, without you picking the three deals yourself. It does not know which email went missing. It does know which deal has gone silent in the CRM while the rep says it’s alive. [Check your CRM with SalesBond](https://salesbond.app/) if Friday keeps finding the same three deals.

## The hole is older than this week

The uncomfortable part of the three-deal check is that whatever you find did not start this week. If one deal in three has a missing thread now, the deals you closed last quarter had the same odds, and the ones you lost had them too. Nobody can tell you from the CRM why the Brightwater pilot stalled in March, because the email where the buyer said the budget moved to Q4 is sitting in an inbox that belongs to someone who no longer works here.

That is the real argument for the rule, and it is not about reporting. It is about who owns the history of a deal: the rep’s inbox, or the company. We wrote about that question for small teams in [who owns the CRM data](https://salesbond.app/blog/crm-data-ownership-small-sales-team/), and the Salesforce version of the answer is the one above. Connect the mailbox, yes. Then make sure every email can find its deal, and check three of them before you go home on Friday.