A customer has replied to your quote. The message is sitting in Outlook or Gmail, but their HubSpot record still shows your last outgoing email. A colleague checks the CRM and prepares to chase someone who has already answered.
Start with one missing reply and trace its route. Mailbox delivery, email logging and record association are separate checks. Fixing the wrong one can leave the gap in place or capture more correspondence than your team intended.
This guide covers individual work emails and one-to-one customer conversations. Shared team inboxes and marketing-campaign replies have their own routes, so identify which you are investigating before changing anything.
1. Confirm what is actually missing
Open the original reply in your mailbox and the customer’s contact record side by side. Record the sender, receiving address, subject, received time and the HubSpot user involved. Use a controlled test message when sharing examples outside your team.
Then distinguish three situations:
- The reply never reached your mailbox: investigate mail delivery first.
- The reply reached your mailbox but has no CRM email activity: investigate logging.
- The email appears on the contact but not the deal you expected: inspect its record associations before reconnecting anything.
Also check whether you are comparing a reply within an existing conversation with a completely new incoming email. They can behave differently under your selected logging rule. Keep the example intact while investigating; repeatedly forwarding it or creating another contact can make the evidence harder to follow.
2. Check the account’s current email logging rule
HubSpot’s current contact email logging guidance, updated on 14 October 2026, distinguishes three options:
- Log replies only: incoming messages must belong to a conversation already logged in the CRM.
- Log all emails (from known contacts): captures incoming and outgoing correspondence with existing contacts through connected individual work emails, including messages sent outside the CRM.
- Create new contacts from logged emails: extends capture to incoming messages from people not yet in the CRM. This remains a beta requiring a Super Admin to opt the account in.
Find the selected option under Settings, Data Management, Objects, then select Activities and open Email Log & Track. Account access permission is required to manage it.
The documentation identifies known-contact logging as the default. Inspect your account rather than assuming its selection. An unknown sender is not covered simply because known-contact capture is enabled. Agree the intended scope before broadening capture across the team.
3. If you use replies-only logging, inspect the original thread
Under HubSpot’s replies-only requirements, the original email must have been sent through the CRM or through the connected email client with the Sales extension or add-in and logging selected. The receiving individual work email must still be connected to an active user, the reply must retain the subject, and exclusions must not block logging.
A fresh email from an existing customer therefore needs a different diagnosis from a reply to a logged quote. A changed subject can also take a reply outside the recognised thread. Do not apply those replies-only restrictions to every account without checking its rule first.
The same guidance warns that changing inbox providers can interrupt reply capture and prevent sequence contacts from being automatically unenrolled. If the gap began during a mail migration, review affected sequences and stop inappropriate follow-ups while investigating.
When escalating an unexplained failure, HubSpot recommends an example contact record and the reply’s email headers. Share those through the appropriate support route.
4. Verify the receiving mailbox and connection type
Check the actual address that received the reply. A user’s HubSpot sign-in address, a forwarding destination and the mailbox connected for sales correspondence may differ.
HubSpot’s individual work email connection guide places email connections under Settings, General, Email. Verify that the intended mailbox is connected using the correct provider. Confirm the hosting provider with your IT team if necessary; using the Outlook application does not by itself establish where the mailbox is hosted.
The guide also says one email account cannot serve as both an individual work email and a team email connection. Microsoft 365 shared mailboxes are not supported as individual work email connections.
If replies go to a shared sales address, establish its existing team-inbox setup before trying to reconnect it as someone’s individual mailbox. Avoid disrupting a working shared channel to solve a single user’s logging problem.
5. Review personal and account-wide exclusions
A healthy connection can still leave correspondence out of the CRM deliberately. Check both levels of HubSpot’s never log lists: a user’s personal exclusions and exclusions applying to everyone.
Look for the customer’s exact email address and their domain. A domain exclusion can explain why several people at one business are affected while other conversations log normally. These lists also apply when using HubSpot’s BCC or forwarding logging addresses; forwarding a message is not a way around an exclusion.
Check why an entry exists before removing it. Keep exclusions that serve a clear purpose, and correct only the entry responsible for an unintended gap.
Never log changes are not retroactive: adding an exclusion does not remove previously logged activity. Do not use the list as a historical clean-up tool.
6. Separate logging from tracking and associations
HubSpot’s Sales Chrome extension guidance distinguishes tracking email engagement from logging an email against CRM records. Selecting tracking is not a substitute for recording the correspondence.
For a Gmail test using the extension, check the Log selection and the records selected for association. Verify the saved email on the intended contact and relevant deal. An engagement notification alone does not show that the conversation history is where your colleagues need it.
If the contact has the message but a deal does not, preserve the existing activity and review its associations. Treat that as a narrower repair than a missing mailbox connection. Avoid logging the same message again simply to make it visible elsewhere.
7. Recover important replies separately from fixing future capture
Make a short recovery list of live opportunities whose correspondence is incomplete. Prioritise replies containing acceptance, questions, changed requirements or requests to stop contact. Give each conversation an owner so two colleagues do not both respond.
Log an individual past message
HubSpot documents retrospective logging from Gmail and Outlook using the Sales Chrome extension or Office 365 add-in. It requires a connected individual work email and personal email access. The older Outlook Desktop add-in does not support this feature, and View-Only users cannot use it.
Select the intended existing records when recovering a message. This retrospective method does not log non-inline file attachments, so check whether the team also needs the original attachment through its normal approved storage route.
Use the forwarding route where appropriate
Alternatively, follow HubSpot’s forwarding-address instructions to log a received reply. Copy the Forwarding Address from the Manual Logging section in the activity settings. Forward the individual reply with its forwarded-message header intact from an eligible user, connected address or recognised alias.
The receiving contact must not be excluded, the mail format must be supported and your email server must permit external forwarding. This route can create a contact if the original sender is not already in the CRM, so check the result rather than assuming it updated the intended person.
Use the BCC logging address when sending an outgoing message; use the forwarding route for an already received reply. Recover one message first, inspect its content and associations, then proceed through the agreed list without duplicating existing activity.
8. Test the real working pattern
A successful manual recovery proves that one message can be saved. It does not prove future automatic logging works. After the focused repair, test with a controlled external mailbox and record what you expect under the selected rule.
- Send an ordinary one-to-one email through the team’s normal route and confirm its CRM activity.
- Reply within the same conversation and check that the reply appears on the intended contact and relevant records.
- Send a separate new message from an existing test contact to check the account’s broader logging rule.
- If mobile email is part of everyday work, repeat the relevant test from the actual mobile app.
- Verify an intentionally excluded test address remains excluded, and have a colleague confirm they can find the permitted conversation history.
Keep the receiving address, timestamps, chosen rule, expected records and observed result with the repair notes. If the test fails, those details give your administrator or HubSpot support a repeatable example.
Make conversation history dependable
Assign someone to own mailbox connections, exclusions and the recovery of missed conversations. Recheck the working pattern after a provider migration or a change to the team’s email process.
If your sales handover depends on colleagues asking each other what a customer said, BuzzBoost can help review your email and CRM setup. Tell us which replies are missing and how your team handles enquiries, and we can scope the next practical step.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
