Log seller emails to the right deal: 4 CRM rules to check

• Check which address or inbox connection logs the email, because HubSpot associates BCC or forwarding address emails to the recipient's contact, its primary company, and the five most recent open deals, according to HubSpot.
• Verify message size limits, as Pipedrive requires the total Smart Bcc message size, including attachments, to be under 20MB, according to Pipedrive.
• Confirm deal status before expecting automatic links, since Pipedrive automatic linking to deals and leads works only for open deals associated with the email’s recipient, according to Pipedrive.
• Account for sync timing variability, because Microsoft documents no defined SLA for the duration of a synchronization cycle due to external factors, according to Microsoft.
• Pick one open deal, send or forward one real seller email through your logging route, then open that deal and check whether the thread appears, noting the record it attached to and how long it took.

Verify which address or inbox connection logs the email, which records it attaches to, how big the message can be, and how long sync takes. Confirm the deal shows the thread before the forecast call. See weekly deal review filters.

1. Routing: Determine if you use a BCC or forwarding address or a connected inbox.
2. Attachment: Identify which records the email attaches to. Check if it links to the contact first or directly to the deal, and verify the specific deal record if multiple are open.
3. Size: Check the maximum message size. Different tools have different caps for what can be logged, so verify the limit for your specific logging method.
4. Sync: Understand the timing of the sync. Some systems have defined cycles, while others may not have a strict service level agreement for when the email appears.

Pick one open deal and send one real seller email through your logging route. Open the deal to see if the thread appears, recording the attached record and the time it took.

Choosing between a BCC/forwarding address and a connected inbox determines how your CRM captures seller emails. A BCC or forwarding route requires you to manually direct email traffic to a specific address, while a connected inbox syncs directly with your email provider. Each method has distinct authentication requirements and attachment behaviors that affect whether an email lands on the correct deal record.

BCC and forwarding addresses In this model, you forward or BCC emails to a unique address provided by the CRM. Pipedrive assigns a unique Bcc address to each lead and deal, allowing you to link an email to a specific record by pasting that deal-specific address into the Bcc field, according to Pipedrive. If you use a universal Bcc address, any replies from customers must be forwarded to that same address to appear in the inbox, according to Pipedrive. Freshworks matches emails forwarded to its address with the email addresses of leads and contacts in the system, according to Freshworks.

Connected inboxes A connected inbox integrates directly with your email service. Microsoft Dynamics 365 Sales requires mailbox approval for the mailbox to process email, according to Microsoft. Freshsales scans all incoming emails once connected and fetches only email addresses that belong to contacts, attaching them with corresponding records, according to Freshworks.

Authentication and manual steps BCC routes often require authentication checks. If both DKIM and SPF checks fail, the email will not sync to your Pipedrive account, according to Pipedrive.

Choosing the right route Paste a Pipedrive lead- or deal-specific Bcc address into the Bcc field to link that record, according to Pipedrive. Choose a connected inbox if you want automatic scanning and attachment based on existing contact records, as Freshsales attaches emails only to addresses belonging to contacts, according to Freshworks.

Ensure the address or connection is active before sending test emails.

Below, a table summarizes the documented logging constraints for each platform. Verify these limits against your specific configuration before relying on them during a deal review.

The destination of a logged email varies by system, determining whether it appears on a contact, company, or deal record. Understanding these attachment rules is critical for ensuring the deal review reflects actual buyer interaction.

In HubSpot, when using the BCC or forwarding address method, the logged email automatically associates with the recipient's contact record and its primary associated company record. See the buying company on a deal. Automatic association means the email thread appears on multiple open deals simultaneously, not just a single specific opportunity.

Pipedrive operates differently regarding automatic deal linking. Automatic linking to deals and leads only works for open deals associated with the email’s recipient, according to Pipedrive. If a deal is closed or not associated with the recipient, the email will not automatically link to it. This limitation requires sellers to ensure the deal is open and properly associated with the contact before relying on automatic attachment.

Microsoft Dynamics 365 Sales integrates with Exchange to track conversations. For example, a seller can email a contact from an opportunity record and track the conversation in the opportunity timeline, according to Microsoft.

Freshworks handles unmatched emails by creating new records. When matches aren’t found in the system, the email addresses automatically become new leads, according to Freshworks.

To verify which record an email attaches to in your CRM, check the deal record after sending a test email. Confirm whether the thread appears on the deal timeline or only on the contact record. If the email does not appear on the deal, check the deal's status and association with the contact. In systems that attach multiple deals automatically, confirm the deal sits among the most recent open ones linked to the contact. Systems requiring manual association or specific send origins need the email sent from the correct record context. This check ensures the deal review displays the relevant buyer contact history.

Before relying on logged email for a forecast call, verify the technical constraints that can block a message from appearing. These limits vary by provider and CRM configuration, so check the specific settings for your stack.

File size caps The file size limit on an email depends on your email provider. For example, the limit in Gmail is 25MB, while the limit in Outlook is 20MB, according to Pipedrive. If a seller attaches a large PDF or video file that exceeds this provider-specific threshold, the email may not sync correctly. Check your team’s primary email provider to identify the exact cap they operate under.

Sync timing and SLA For systems using server-side synchronization between customer engagement apps and email servers, there is no defined SLA for the duration of a synchronization cycle. This is because the duration is directly influenced by external factors, according to Microsoft. Consequently, you cannot promise a specific timeframe for when an email will appear on the deal record.

The mailbox will be ready for processing again in 5 to 12 minutes. This timeframe is based on how active the mailbox has been in the last sync cycles, according to Microsoft.

Authentication and routing While size and timing are the primary blockers, authentication failures also prevent logging. If the CRM cannot verify the sender or recipient, the email may not attach to any record. Ensure your sales team uses the correct BCC or forwarding address configured in the CRM.

When a seller email is missing from a deal record, the first check is whether the message passed authentication. If both DKIM and SPF checks fail, the email won’t be synced to your Pipedrive account, according to Pipedrive. This means the message never entered the system at all, so it cannot attach to any contact, company, or deal. Before assuming a linking error, confirm that the sender’s domain passed both authentication checks. If the email came from an external domain you do not control, you cannot fix the sender’s records, but you can verify whether the failure is consistent.

The second check is whether the sender is already a contact in your CRM. Many systems attach emails to existing contacts first and then link them to deals. If the sender has no contact record, the email may sit in an inbox or a generic log without a deal association. Review the sender’s email address against your contact list. Create the contact record first if the person is new, before expecting the email to appear on a deal. Buyers changing email addresses or new stakeholders joining the conversation make this step especially important.

The third check is the deal’s status. Some CRMs only link emails to open deals. If a deal is closed or lost, new emails from that buyer may not attach to it. Check the deal’s current stage. See open, won, and lost stage rules. If the deal is no longer open, the email may attach to the contact or company instead, or it may not link at all.

You have 1 open deal and send 1 email with a 10 MB file. Check the logging route, then open the deal. If the thread is missing, wait 15 minutes and check the contact record too. Note where the thread attached.

Action step Send a test email with a 10MB attachment to your logging address. Wait 15 minutes, then check the deal record. If the email is missing, check the provider’s size limit and the mailbox’s sync status.

Does a BCC email attach straight to a deal?

Not always. HubSpot automatically associates logged emails to the recipient's contact record, its primary associated company, and the five most recent open deals linked to that contact, according to HubSpot. Pasting a Pipedrive lead- or deal-specific Bcc address can link an email to that record, according to Pipedrive. Automatic linking only works for open deals associated with the recipient, according to Pipedrive.

Why did an email not link to my deal?

Automatic linking to deals and leads in Pipedrive only works for open deals associated with the email’s recipient, so closed deals will not receive the link, according to Pipedrive. Microsoft server-side synchronization requires mailbox approval, and the process is influenced by external factors that prevent a guaranteed immediate link, according to Microsoft.

Is there a size limit on logged email?

The total size limit for emails logged with the BCC or a forwarding address in HubSpot is 40 MB, according to HubSpot. Smart Bcc total message size, including attachments, must be under 20MB, according to Pipedrive.

How long does inbox sync take?

Microsoft states there is no defined SLA for the duration of a synchronization cycle because it is directly influenced by external factors, according to Microsoft. A five-minute postponement occurs after an incoming cycle in their server-side synchronization process, according to Microsoft.

What happens to emails from people who are not contacts yet?

Freshworks automatically creates new leads when matches aren’t found in the system for incoming emails, according to Freshworks.