A customer reply is visible in Outlook or Gmail, yet the salesperson cannot find it in Pipedrive. Elsewhere, messages appear in Sales Inbox but not beside the relevant deal. Both complaints sound like a Pipedrive email sync problem, but they do not establish the same failure.
Quick answer
Check the connected account and sync state, then separate message inclusion, inbox display, record linking, and conversation visibility. Re-authenticate only when the connection evidence calls for it. Investigate automated sending independently rather than assuming a restored inbox fixes every follow-up.
Key takeaways
- Separate connection failures from inbox inclusion, record linking, and visibility.
- Use connection evidence before disconnecting or re-authenticating an account.
- Verify automated follow-ups separately from ordinary email synchronization.
This guide uses official Pipedrive documentation reviewed on October 9, 2026. It is a documentation-based troubleshooting workflow, not a hands-on product test. The examples are fictional operating scenarios. Plan eligibility and interface labels should be checked against your current account.
Choose the symptom before changing settings
Start with a specific message, not a report that “email is broken.” Ask its owner which mailbox received it, which Pipedrive user should see it, and whether the missing location is Sales Inbox, a deal’s detail view, or an automated-send history.
Record the sender, recipient, subject, message time with timezone, and expected linked item in an approved private workspace. If a team member is helping, use a case reference in shared chat instead of copying a customer’s conversation repeatedly.
Pipedrive’s email-sync overview currently lists the feature on Growth and higher plans. It distinguishes personal accounts from team accounts and explains that shared conversations appear in linked item views, not automatically in another user’s mailbox. Check account type and intended viewing location before treating a colleague’s different inbox as evidence of a failed connection.
Define one outcome for the investigation. A useful statement is “the mailbox owner can find this eligible reply in Sales Inbox and associate it with the correct opportunity.” That is narrower and more testable than promising every historical message will appear everywhere.
A practical triage worksheet
| Question | Evidence to inspect | What not to assume |
|---|---|---|
| Is the mailbox connected? | Account identity and sync notification/state | That an old connection still has access |
| Is the message included? | Original mailbox location and selected sync labels | That every folder is in scope |
| Is the view hiding it? | Inbox or Sent filters | That absence from one filtered list means loss |
| Is it linked correctly? | Thread association with the intended item | That syncing equals correct deal attachment |
| Should this viewer see it? | Conversation sharing and linked-item access | That visibility should be widened for everyone |
| Was an automated email attempted? | Automation history and default sending account | That incoming sync proves an automation sent |
Use the worksheet to assign the next action rather than to label the cause prematurely. A message can be included but hidden by a filter, or available to its owner while deliberately private to others. Preserve those distinctions in the incident notes.
Confirm the intended mailbox and connection
Open the account menu and inspect the connected email account in Personal preferences. Compare the account with the mailbox containing the example message. Check whether the complaint concerns a personal account, a shared team address, or another account altogether.
Ask what changed before the first failure. Relevant context can include a provider credential update, a mailbox migration, a new company access policy, or a changed server configuration. Record the timing without asserting that the change caused the incident.
The official re-authentication guide describes a stopped-sync notification when Pipedrive loses mailbox access. It directs users to Re-authenticate from the notification or Personal preferences > Email sync. The mailbox owner completes the provider authentication and access flow; Pipedrive states that previous email history remains unchanged.
Have the authorized owner complete that step privately. Do not ask a colleague to send a mailbox password through chat, and do not approve an unexpected access scope merely because it appears during troubleshooting. If company policy blocks the connection, involve the responsible administrator.
Check inclusion before attempting a reconnect
If the account is connected, find the example message in the original provider mailbox. Note its folder or label and whether another message from the same conversation appears in Pipedrive. A single excluded message and an entirely disconnected account require different evidence.
Pipedrive’s email-sync troubleshooting reference recommends checking Inbox/Sent filters and the Labels setting: only messages under selected labels sync. It also distinguishes messages absent from Sales Inbox from threads absent in a record’s detail view, where linking needs inspection. Browser checks and a documented disconnect/reconnect are additional troubleshooting options, not a reason to skip these earlier checks.
For an illustrative sales team, customer replies are moved into a project label by a mailbox rule. If that label is outside the agreed sync selection, investigate whether the selection or the mailbox rule should change. Do not broaden sync to all personal mail without considering confidentiality.
Take a redacted record of the current selection before changing it. Specify the business purpose of each included label and identify the owner who approves the scope. A narrower approved configuration can be correct even when it excludes messages someone informally expects to see.
Separate a filter problem from a missing record link
Search in the appropriate account and review active display filters. Compare the result with the original complaint location. If a message appears when a filter is removed, document that observation rather than reconnecting a mailbox that is already bringing in the message.
Next, inspect the conversation’s association with the intended deal, lead, or contact. Confirm the specific item rather than linking by a familiar name alone. One organization may have several active opportunities, and attaching a thread to the wrong one creates misleading sales history.
For an illustrative consultancy, the same customer is discussing both a renewal and a new implementation. The email belongs to the renewal, although the newest open deal concerns implementation. Have the responsible salesperson choose the association based on the conversation’s purpose.
If manual linking resolves the detail-view complaint, review the operating rule that led to the association. Keep automatic association expectations in the CRM requirements rather than relying on each salesperson to remember exceptions. Daily Jade’s CRM requirements guide provides a broader framework for those decisions.
Respect conversation privacy during diagnosis
A manager’s inability to see an email does not automatically mean the message failed to sync. Ask the mailbox owner whether the conversation is present for them. Then review the intended sharing arrangement and access to the linked business item.
Do not use “share everything” as a universal repair. Personal mailboxes can contain confidential client matters, employment information, or unrelated private correspondence. The correct visibility boundary should follow the organization’s approved collaboration and privacy rules.
Keep the diagnosis neutral: “the owner can see the thread; the manager cannot see the linked conversation.” That observation identifies a visibility question without implying that the manager is entitled to broader access. Route any permission decision to the responsible administrator.
This applies to teams in the US, Canada, UK, and Australia, but the guide does not establish a legal basis for sharing correspondence in those countries. Use your company’s privacy and retention policies for the authorization decision; use product documentation for the software behavior.
Investigate outgoing automation as a separate path
When an automated follow-up is missing, inspect the automation’s evidence rather than using an incoming customer reply as the only test. Identify the automation, the expected trigger, the owner, and the action that should have sent the email.
The automation troubleshooting guide directs users to inspect failed actions in history, verify active email sync, and choose a default email account when multiple accounts are synced. It states that disabling the default account setting stops email actions in automations. It also advises investigating promptly because automation history is retained for 15 days.
Capture the relevant error while it is still available. Avoid repeatedly triggering the business action simply to generate new history. Check whether an earlier attempt actually sent a message before approving a retry, especially for customer follow-ups with sensitive context.
Assign the recovery decision to the person responsible for that communication. A restored mailbox can enable future actions, but historical failed sends still need review. Do not promise that every old automation failure will replay automatically after the connection returns.
Custom mail providers need an administrator-led check
For a custom provider, obtain the current approved server configuration from the mailbox administrator. Do not copy a port and hostname from an unrelated company’s setup. Confirm the intended connection method and whether the organization’s policy allows it.
Pipedrive’s IMAP and SMTP reference says native Gmail and Exchange connections should be used before a custom connection when available. It documents provider-specific settings and notes that POP3 and unencrypted IMAP on port 143 are unsupported. Where app-specific passwords or network restrictions apply, follow the provider’s and administrator’s approved process.
Keep that check separate from editing customer records. A server configuration issue should not be “fixed” by importing emails again through another route or changing customer addresses. Such workarounds can create a second, confusing history without addressing access to the mailbox.
If a configuration change is approved, record its owner, previous setting, new setting, and validation plan. Do not lower encryption or authentication protections to make a connection pass. Escalate an unsupported provider arrangement rather than disguising it as a normal sync setup.
Verify the repair with a controlled conversation
Use an approved test sender and recipient, with a distinct subject that can be searched in both systems. Make the content harmless and ensure any sales automation attached to the test item is understood before sending.
Check the message in the original mailbox, then the appropriate Pipedrive Sales Inbox, then the intended linked item. Verify visibility as the authorized owner and, where appropriate, as the intended collaborating user. Record each result separately.
If outgoing communication was also affected, test that path independently and confirm receipt with the approved recipient. A message appearing in a CRM conversation is different evidence from successful delivery to the other person’s mailbox.
Finish by reviewing the affected incident window. Identify customer replies that need a human response and failed follow-ups that require a decision. Give the sales team a clear recovery list rather than announcing “fixed” while unanswered enquiries remain hidden in operational backlog.
Escalate with useful, protected evidence
Provide the affected user and account type, provider, observed sync state, incident times, example message reference, expected location, relevant label/filter selection, and any automation error. State which checks succeeded and where the discrepancy remains.
Pipedrive’s raw-email-source guide explains that raw source is obtained from the external email account, not Pipedrive, and may be requested for support as an EML file. Such a file can contain private message content and routing data; share it only through an authorized support channel when needed.
Redact routine screenshots and avoid sending credentials. If the support team needs an unredacted example, have the responsible person approve that disclosure. A smaller, relevant evidence packet is more useful than an uncontrolled export of the entire sales mailbox.
Frequently asked questions
Why can I see an email in Sales Inbox but not on a deal?
Inspect the conversation’s link to the intended item and the viewer’s access. Syncing a message into the owner’s inbox does not by itself prove the correct deal association or sharing arrangement. Validate the business context before changing links.
Should I disconnect the account immediately?
First check the account identity, sync state, selected labels, display filters, and record linking. Use the documented recovery route if those checks support a connection fault. Preserve your approved settings so that a reconnect does not accidentally broaden the email scope.
Does restoring sync fix failed automated follow-ups?
It can restore a prerequisite for future sending, but each failed follow-up still needs its own evidence and recovery decision. Inspect automation history, the active/default account, and prior delivery before retrying. Avoid duplicate customer communication.
Close the incident, not just the connection warning
A reliable Pipedrive email sync repair ends with the intended conversation in the right place, visible to the right people, and any missed customer actions assigned. Keep the incident notes for your CRM implementation process. If the incident reveals a wider product-fit question, consult the Pipedrive review separately; do not turn one unexplained sync problem into a premature platform migration.
Join the conversation
Share a useful perspective, question, or first-hand experience with other Daily Jade readers.