Skip to main content

Reopen closed HubSpot conversations

Keep a customer's messaging history in a single HubSpot thread by letting Octopods reopen closed conversations when new messages arrive.

Written by Mohamed Elbadwihi

When a customer replies after you’ve closed a HubSpot conversation, you can reopen the closed conversation in the same thread instead of starting a new one. Turn on Open Closed Conversation Thread for the channel, and the customer’s full history stays in one thread. For more on working in HubSpot, visit HubSpot inbox and CRM view.

Why this setting matters

By default, HubSpot creates a brand-new conversation thread if a customer messages you again after their previous conversation has been closed for more than 24 hours. That protects agents from picking up old threads, but it also splits a single customer’s history across multiple threads.

Turn on Open Closed Conversation Thread and Octopods reopens the existing thread whenever a closed conversation gets a new message, keeping everything in one place.

Where the setting lives

The setting is available per channel on HubSpot workspaces.

  1. Sign in to Octopods and open your HubSpot workspace.

  2. Open the channel you want to configure.

  3. Scroll to the Open Closed Conversation Thread section.

Turn reopening on

  1. In the Open Closed Conversation Thread section, select the Yes radio (labeled “Automatically reopen closed conversations”).

  2. Click Update HubSpot Open Conversation to save.

From then on, when a customer messages you on that channel and their most recent conversation is closed, Octopods reopens the existing thread and appends the new message instead of starting a fresh one.

Turn reopening off

  1. In the Open Closed Conversation Thread section, select the No radio (labeled “Let HubSpot create new conversation threads”).

  2. Click Update HubSpot Open Conversation to save.

When reopening is off, HubSpot’s default behavior takes over and a new thread is created whenever a closed conversation has been dormant for more than 24 hours.

How the 24-hour window works

HubSpot’s own rule is:

  • If the conversation was closed within the last 24 hours, HubSpot reopens it automatically even without the Octopods setting. Any new inbound message lands on the existing thread.

  • If the conversation has been closed for more than 24 hours, HubSpot creates a new thread by default.

The Octopods Open Closed Conversation Thread setting covers that second case — once a conversation has been closed for more than 24 hours, Octopods steps in and reopens the existing thread so you don’t end up with a new one.

Note: The 24-hour window is set by HubSpot; it is not configurable in Octopods.

Reopen closed HubSpot conversations FAQs

Why did HubSpot start a new conversation when my customer replied?

The conversation had been closed for more than 24 hours, and Open Closed Conversation Thread was off for that channel. Turn it on to keep future replies in the same thread.

Do I lose the history of the old conversation?

No. The old thread still exists. With the setting off, the customer’s history is split across threads. You can find earlier threads from the contact record. See Associating Conversations with CRM Records.

Will turning the setting on merge threads that are already split?

No. The setting doesn’t change threads that are already split. It applies only to new incoming messages from the moment you turn it on.

Do I need to turn this on for every channel?

Yes. The setting is per channel. Turn it on for each channel where you want replies to reopen the same thread.

For more on threads in HubSpot, see How Conversations Work in HubSpot.

When to leave it off

Some teams prefer a fresh thread for each new conversation because:

  • They close conversations after resolution and want a clean slate next time.

  • Their routing rules depend on conversation creation events that only fire on brand-new threads.

  • Their reporting relies on counting conversations rather than messages.

If any of those apply, keep the setting off so HubSpot’s default behavior applies.


What’s next

Did this answer your question?