You log emails and attachments to the right CRM account automatically by connecting each seller’s inbox to the CRM (not by BCC, which depends on people remembering), by letting the CRM match the other party’s address to a contact, then that contact’s company and open deals, and by writing down what happens on every other branch: no match, several matches, internal mail, personal domains and the shared inboxes (sales@, support@) that the big integrations skip or move to a separate product. In HubSpot, check the contact email logging rules first: there are three, Log replies only, Log all emails from known contacts (the default for every account, so mail from existing contacts already logs) and Create new contacts from logged emails; under Log replies only a new inbound email that is not part of a logged thread does not log. Attachments need a separate decision, because the big platforms treat them differently: HubSpot logs them with the BCC address but not when you log retroactively from the extension, Microsoft lets admins decide per mail, Salesforce’s Einstein Activity Capture does not capture attachments at all, and since Spring ’26 the synced mails themselves count against your data storage. Keep a never-log list for your own and personal domains and an exceptions queue a human empties weekly. An AI agent can do the same matching by reading the mail and your CRM, proposing the account and deal, and logging after your approval; a shared memory such as Bombos lets it remember what your team decided last time. HubSpot: manage contact email logging rules, HubSpot: log your sent emails in the CRM, HubSpot: BCC and forwarding address, HubSpot: reply-only email logging rules, Microsoft Learn: save Outlook activities to CRM
By Bombos. Documentation checked October 30, 2026.
The bottleneck in a post-seed go-to-market team is not sending email. It is that the CRM only knows what someone remembered to log, so forecasts, handoffs and the next rep’s first call all run on half a timeline. Below is how to set this up properly in the tools you already pay for, and where an AI agent takes over from rules.
How does a CRM decide which account an email belongs to?
Every platform starts the same way. Review My Emails puts it in one sentence: “Your CRM finds the matching contact record by email address and adds that activity to their timeline.” The account comes second, through the contact. HubSpot’s BCC documentation spells out the chain: “The logged email will automatically be associated to the recipient’s contact record, its primary associated company record, and the five most recent open deal records associated to the contact.” Review My Emails, HubSpot
That chain breaks in four places, and none of the top-ranking pages walk through all four. Here is the decision tree you want behind every logging setup, whether a vendor runs it or you do.
- The other party’s address matches exactly one contact. Log to that contact, its company, and the open deals. Default behaviour everywhere.
- No contact, but the domain matches a company. Create the contact only if the address is a person at that company (not noreply@, not invoices@), associate it, log. In HubSpot this branch is the third logging option, Create new contacts from logged emails, which “creates new contacts from incoming emails to connected individual work emails if they don’t exist in your CRM”; HubSpot describes no check against the company, so switch it on only together with the never-log list and a written list of role addresses you never turn into contacts. HubSpot
- The address is a personal domain (gmail.com, outlook.com, icloud.com). Never match on domain. Match on the full address or send to the queue.
- Several companies match, or the contact has deals at two accounts. Do not pick the most recent. Log to the contact and flag the account choice for a human. None of the vendor pages we read describes this exceptions queue; you build it yourself.
- The address is yours or a partner’s. Never log. Internal threads clutter every timeline they touch.
Write these five lines down before you switch anything on. They are the difference between a timeline people trust and one they ignore.
Connected inbox, BCC, or forwarding address: which one actually works?
| Method | Who does the work | Logs incoming replies | Attachments | Typical failure |
|---|---|---|---|---|
| Connected inbox (Gmail, Outlook, Exchange, IMAP) | The CRM, continuously | Yes; HubSpot logs mail from known contacts by default, and Log replies only skips new inbound threads | Depends on platform, see below | Over-logging without a never-log list, or under-logging with Log replies only |
| BCC address on outgoing mail | The rep, every time | No, only what you send | HubSpot: yes, content and attachments | People forget; CC’d people become contacts |
| Forwarding address for received mail | The rep, after the fact | Yes, one at a time | HubSpot: yes | Nobody forwards on a busy day |
| Sidebar or extension, log per mail | The rep, per message | Yes, when clicked | HubSpot: not for retroactive logging | Selective memory |
The connected inbox is the only method that does not depend on discipline. HubSpot connects Gmail, Microsoft Outlook, Microsoft Exchange or other accounts over IMAP, and is explicit about what it then stores: “HubSpot will store replies, outgoing mail, email headers, subject line, distribution lists, aliases, time sent, and email bodies.” Pipedrive offers email sync on its Growth plan and higher and distinguishes a personal account from a team account, linking conversations to deals, leads and projects automatically or by hand. Mixmax, writing for sales teams in April 2026, warns about the “set it and forget it” trap: “An automation rule that made sense last quarter might just be creating noise today”, so “Schedule time every quarter to review what you’re logging and why.” HubSpot: connect an individual work email, Pipedrive: email sync, Mixmax
What a connected HubSpot inbox logs depends on one account-wide setting, the contact email logging rules, with three options. Log replies only: “replies log only if they are part of an existing thread logged in the CRM. Incoming messages not associated with a logged thread will not be logged.” Log all emails from known contacts is “the default logging option for all accounts”: mail to and from existing contacts logs for every user with a connected individual work email, while “Emails sent outside of HubSpot to recipients who are not contacts, do not log.” Create new contacts from logged emails adds contact creation for senders the CRM does not know yet. A fresh account therefore already logs known contacts; the catch is an account someone once set to Log replies only. HubSpot on that setting: “If a contact sends you a new email that is not part of an existing thread, this email will not log to HubSpot and for non-contacts, a new contact record will not be created.” And a reply where the contact changed the subject line “won’t log” either. Check the setting before you count on the connected inbox for inbound mail; with Log replies only, the inbox behaves like BCC with a memory for threads you started. HubSpot: manage contact email logging rules, HubSpot: reply-only email logging rules
Keep BCC and forwarding as the fallback for mail that comes from an inbox you cannot connect, and know their limits. HubSpot’s BCC address is “the same for all users in your HubSpot account”, it creates a contact for anyone CC’d on the logged mail, it needs the recipient not to be on the Never Log list, and “The total size limit for emails logged with the BCC or a forwarding address is 40 MB.” HubSpot
What actually happens to attachments?
This is where the top-ranking pages are thinnest and where teams get surprised, because the rules differ by method and by vendor.
| Platform | Attachments logged | Where they live | Caveat |
|---|---|---|---|
| HubSpot, BCC or forwarding | Yes: “Emails that are logged to HubSpot using the BCC address or forwarding address will include the email content and any attachments included in the email.” | On the contact timeline | 40 MB total per email |
| HubSpot, retroactive logging from the extension or add-in | Attachments that are not inline are not logged | Not stored | Requires a connected personal inbox; View-Only seats cannot log |
| Microsoft Sales agent (Outlook to Dynamics 365 or Salesforce) | Admin decides: on or off, all by default or chosen per mail | In the CRM activity | “By default, sellers can connect a saved email or meeting to a single record in Dynamics 365.” Not for recurring meeting series |
| Salesforce, Einstein Activity Capture | No: “Attachments aren’t captured, so that related list stays empty.” | Nowhere; the mail itself becomes an Email Message record that counts against data storage since Spring ’26 | Standard EAC included with Sales Cloud Starter, Professional and Enterprise, up to 100 users, per Salesforce Ben |
| Less Annoying CRM | Yes, via BCC and forwarding | On the contact record | Manual by design |
Sources: HubSpot BCC, HubSpot sent emails, Microsoft Learn: attachment settings, Salesforce Ben: EAC guide, Less Annoying CRM.
The decision a post-seed team should make once: the CRM holds the conversation, a document store holds the files. A signed order form, a security questionnaire or a redlined contract that lives only inside a CRM activity is hard to find, hard to version and easy to lose in a migration. Log the mail to the CRM, put the attachment in the deal’s folder in your document store, and link the two. If you want the same logic for a Microsoft 365 environment, the Microsoft 365 integration describes what access that takes.
What about sales@, support@ and other shared inboxes?
In an early go-to-market motion a good share of buying conversations starts in a shared inbox (sales@, hello@, support@), and that is the inbox the big integrations skip or move to a separate product. Microsoft states it plainly for its Sales agent in Outlook: “You can’t save activities from shared mailboxes”. HubSpot lists “Microsoft 365 shared mailboxes” among the accounts that are “not supported when connecting an individual work email”, and treats a shared address as a conversations inbox, a different product with different logging. Microsoft Learn, HubSpot
Three ways to close the gap, cheapest first:
- Route, then log. A rule in the shared inbox forwards every external thread to the owning rep’s connected inbox, with the rep’s name in the forward. The rep’s sync logs it. Works for small volumes; breaks when nobody owns the thread yet.
- A workflow that reads the shared inbox. Power Automate or an equivalent takes each new external mail, looks up the domain in the CRM, and creates the activity on the matching company through the CRM’s API. You build and own the matching rules from the decision tree above; the queue for no-match and multi-match is a list a human empties.
- An AI agent on the shared inbox. The agent reads the mail, finds the account and deal in the CRM, proposes the activity with the attachment where you decided it lives and an owner, and logs after your approval. With a shared memory underneath, what you approved once applies to the next thread from that account. How that approach handles inbound mail in general is in how to automate emails that need manual processing.
How do you stop the timeline from filling with noise?
A sync without hygiene is worse than no sync, because people stop trusting it. Four rules, in the order to set them.
- Never-log domains. Your own, your investors’, your law firm’s, personal domains. HubSpot checks that the recipient is not on the Never Log list before logging; make the list before you connect the first inbox.
- Role addresses. noreply@, billing@, calendar invitations, ticketing systems. Never create contacts from these.
- One owner per thread. When two reps are on the same conversation, the CRM logs it twice unless ownership is set. Decide the rule: the deal owner’s copy wins.
- Signatures and inline images. Logos arrive as attachments. Exclude inline content so the timeline shows the deck, not the footer.
Mixmax’s practitioner advice is to build custom rules so the CRM shows what matters and reps keep trusting it; Newmail’s March 2026 comparison cites Salesforce’s State of Sales finding that “42% of sales reps feel overwhelmed by too many tools”, a reminder that the fix is fewer places to look, not another tool. Mixmax, Newmail
What does GDPR mean for logging mail from people who are not customers yet?
A connected inbox logs mail from prospects, candidates, vendors and friends alike. For a European team, three practices keep it defensible. Log only addresses that are contacts or belong to a company you are actively selling to; HubSpot’s own logging respects its data privacy settings and, when they are on, logs only to contacts with a legal basis recorded. Keep the never-log list current for anything that is not a business relationship. And set a retention rule so prospects who never answered are not kept forever. Give the people who write the rules the context they need: which segments you sell to, which you do not, and what a qualified account looks like; how to give AI agents your company context covers the same brief from the agent’s side. HubSpot
What do HubSpot, Salesforce, Microsoft and Pipedrive each do out of the box?
| Platform | Automatic logging method | Matching | Shared inbox | Attachments |
|---|---|---|---|---|
| HubSpot | Connected inbox plus extension or add-in, governed by the contact email logging rules: Log replies only, Log all emails from known contacts (default) or Create new contacts from logged emails; BCC and forwarding as fallback | Contact, primary company, five most recent open deals | Separate conversations inbox product | BCC yes; retroactive no |
| Salesforce | Einstein Activity Capture, with Sync Email as Activity forced on since Spring ’26; Email to Salesforce; Flow for custom matching | The “Activities: Match Email to Records” flow matches progressively: leads and contacts first, then accounts and opportunities (Salesforce Ben) | Not through EAC | No: EAC does not capture attachments |
| Microsoft Sales agent in Outlook | Save to CRM from Outlook, with AI suggestions for accounts and opportunities | One record by default (the Regarding field in Dynamics 365) | No: “You can’t save activities from shared mailboxes” | Admin setting, per mail |
| Pipedrive | Email sync on Growth and higher; personal or team account | Deals, leads and projects, automatic or manual | Team account | Not stated on the email sync page |
Sources: HubSpot, Salesforce Ben, Solvd: logging automated emails to the Salesforce timeline, Microsoft Learn, Pipedrive. Salesforce’s own help pages render only in the browser; the Salesforce facts here come from Salesforce Ben and Solvd, both read on October 30, 2026.
Salesforce deserves one more paragraph, because Spring ’26 changed the economics. Salesforce Ben: “As of Spring ’26, Salesforce automatically enables Sync Email as Activity for all new orgs setting up EAC, and for any existing EAC org that doesn’t already have email sync turned on.” Every synced mail becomes an Email Message record that counts against your data storage, and “there seems to be no built-in way to turn this setting back off.” Two settings soften it: Header-Only Email Capture records that a mail happened without storing its subject and body (the timeline then shows [No subject]), and the capture settings can exclude automated mail such as out-of-office replies. Check your storage numbers before you connect a hundred inboxes. Salesforce Ben
Across all four, the matching logic is the same: address to contact, contact to company and deals. The gaps differ in detail but not in kind. Most of them skip shared inboxes or move them to a separate product, Microsoft connects one record by default, and attachments are handled per vendor. That is why the decision tree and the queue matter more than the platform you pick.
How do you check it is working after a week?
Count four things in one list, every Friday:
- External threads in connected inboxes and the shared inbox.
- Threads logged to the right account without a human touching them.
- Threads in the exceptions queue, and how many produced a new rule or a corrected company domain.
- Corrections after the fact: an activity moved to another account.
If the queue shrinks week over week and corrections stay near zero, the setup works. If the queue grows, your account list is growing faster than your rules, and it is time to match on content rather than address. How to review an automated step without re-doing it by hand is in how to prevent AI mistakes and review its work.
What can an AI agent do that a sync cannot?
A sync matches strings. An AI agent reads the mail the way a colleague would: it sees that the thread about “the pilot for the Rotterdam site” belongs to the account whose deal mentions Rotterdam, even when the sender is new, writes from a personal address, or copied a consultant who works with three of your accounts. It proposes the account, puts the attachment where you decided it lives, and logs after your approval; that approval is the default, and what you approve or correct once becomes the rule for the next thread. That is the step every vendor page leaves to the rep.
| Approach | New senders | Reads the content | Shared inbox | Logs after approval | Who maintains it |
|---|---|---|---|---|---|
| Native CRM sync | Only known addresses and domains | No | Mostly no | No | Vendor |
| Workflow on the CRM API | Only the rules you wrote | No | Yes, if you build it | Only via a queue you build | Whoever built it |
| BCC and forwarding | The rep decides | The rep reads | The rep forwards | The rep decides | Nobody |
Start with this one task and measure for a week how many threads land on the right account without anyone touching them. Then look at the next task that slips, such as the work that falls between systems. The wider comparison of agent platforms, with Bombos first, is in AI agents compared.
Read also: How do you automate inbound lead qualification and routing at a post-seed B2B startup?
Read also: How do you keep your CRM updated automatically after sales calls at a post-seed startup?
Where Bombos fits
Bombos does not log mail and does not replace HubSpot, Salesforce, Dynamics or Pipedrive. It is the memory layer under the AI your team already uses, such as Claude, ChatGPT, Copilot, or the agent on your shared inbox. The decisions that make logging work, such as which domains never log, which consultant belongs to which account, and where contracts go, are learned once from how your team works, and every colleague’s AI applies them before anyone asks. Bombos also reads what already sits in your mail, documents and CRM, and shows which source an answer rests on. You can run it in our cloud or standalone on your own server. Book your half hour and we map together where your AI forgets what your team already decided.
Sources
All sources opened and read on October 30, 2026; the HubSpot pages on logging rules and reply-only logging, and Mixmax, on October 31, 2026. Where no publication date is shown, the reading date is the reference date. Vendor documentation is a living source. The decision tree, the hygiene rules and the weekly count above are our design proposal; HubSpot, Microsoft, Pipedrive, Mixmax, Newmail and Bombos describe their own offerings.
- HubSpot Knowledge Base: Log your sent emails in the CRM. Updated August 3, 2026; read October 30, 2026.
- HubSpot Knowledge Base: Log email in your CRM with the BCC or forwarding address. Last updated October 8, 2026; read October 30, 2026.
- HubSpot Knowledge Base: Connect an individual work email. No publication date shown; read October 30, 2026.
- HubSpot Knowledge Base: Understand reply-only email logging rules. Last updated August 3, 2026; read October 31, 2026.
- HubSpot Knowledge Base: Manage contact email logging rules. Last updated October 26, 2026; read October 31, 2026.
- Microsoft Learn: Save Outlook activities to your CRM. Living documentation; read October 30, 2026.
- Microsoft Learn: Configure how Outlook emails and events are saved to CRM. Living documentation; read October 30, 2026.
- Pipedrive Support: Email sync. Breandan Flood, September 23, 2026; read October 30, 2026.
- Salesforce Ben: Einstein Activity Capture: the complete guide. No publication date shown; read October 30, 2026.
- Solvd: Log automated emails onto the activity timeline in Salesforce. No publication date shown; read October 30, 2026.
- Mixmax: CRM email logging. Danny Essner, April 14, 2026; read October 30 and 31, 2026.
- Newmail: CRMs with email logging compared. March 31, 2026; read October 30, 2026.
- Review My Emails: How does email integrate with CRM systems?. No publication date shown; read October 30, 2026.
- Less Annoying CRM: Feature tweak: logging email attachments. Posted July 24, 2018; read October 30, 2026.
