What is it?

HubSpot now uses the Reply-To email header to determine the sender for contact creation and outbound replies in Help Desk and Conversations Inbox, ensuring replies reach the intended recipient and CRM records are accurate.

Why does it matter?

Support teams using Help Desk or Conversations Inbox often receive emails where the From address is not the real sender, causing replies to bounce, incorrect contact records, and broken conversation threads. This change addresses a major pain point by ensuring replies go to the correct person, CRM data stays accurate, and support automation works as intended. It unblocks Customer Agent adoption for thousands of portals and brings HubSpot in line with established competitor behavior.

How does it work?

• When an inbound email has a Reply-To header that differs from the From header, HubSpot uses the Reply-To address for both contact resolution (creating or matching a CRM contact) and outbound reply routing.
• Three safeguards are in place: fallback to From if Reply-To is a noreply address, fallback to From if Reply-To is in the forwarding chain, and creation of a visitor (not a contact) if Reply-To is a GUID/token relay address.
• If the email is a human-forwarded message, the original sender extracted from headers/body takes precedence.
• This change is applied automatically for new threads; no user action or configuration is required.

Who gets it?

All hubs and tiers