# Merge support conversations together

**URL:** <https://community.hubspot.com/t/merge-support-conversations-together/34093>\
**Category:** HubSpot Ideas\
**Tags:** conversations-inbox\
**Created:** [March 18, 2021, 1:24pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093 "2021-03-18T13:24:02Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyBrightmile](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/andybrightmile/32/76463_2.png) [@AndyBrightmile](https://community.hubspot.com/u/AndyBrightmile)\
**Post date:** [March 18, 2021, 1:24pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/1 "2021-03-18T13:24:02Z")

</div>

As a Super User, it would be great to have the ability to merge two or more conversations together. We often have several live chats and email trails from the same contact (regarding the same issue) and it would be great to be able to merge these together to create a single thread. Other tools such as Zendesk have this functionality and it would be a great improvement for the Hubspot Conversations Tool.

---

<div class="post-metadata">

**Author:** ![DavideDL](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/davidedl/32/59606_2.png) [@DavideDL](https://community.hubspot.com/u/DavideDL)\
**Post date:** [August 28, 2020, 12:26pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/2 "2020-08-28T12:26:20Z")

</div>

It would be nice to have a feature to merge emails in one thread.  
Let me give you an example:

Person 1 (the scientist) sends an email to place order 123 to [sales@mycompany.com](mailto:sales@mycompany.com)

Person 2 (the purchase manager) sends an email with the PO attached for order 123 to [sales@mycompany.com](mailto:sales@mycompany.com)

Given the current settings, we have 2 different emails from 2 different people referring to the same task/ticket.

It would be nice to have a feature to merge the 2 emails or to link the 2 emails

---

<div class="post-metadata">

**Author:** ![alguil](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/alguil/32/28756_2.png) [@alguil](https://community.hubspot.com/u/alguil)\
**Post date:** [November 17, 2020, 8:36am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/3 "2020-11-17T08:36:28Z")

</div>

![34346i988C078A97A0022E.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/a/ac25c49ca43478e1f3dff0e176c6902f4eef5561.png)

+1 on this idea. Adding a “merge” feature in the “Plus” section on the inbox, after having selected several conversations to merge it in once would be very nice.

Additional nice to have : if conversations are already linked to a ticket, the tickets would also be merged in one

---

<div class="post-metadata">

**Author:** ![benesch\_e](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/benesch_e/32/43030_2.png) [@benesch\_e](https://community.hubspot.com/u/benesch_e)\
**Post date:** [March 25, 2021, 8:35pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/4 "2021-03-25T20:35:48Z")

</div>

Agreed, it would be nice to have a way to EASILY merge things into one record for support issues. We have a team email that generates a ticket for each submission, the team email is also sometimes the easiest way to make sure all our support team gets notified of important information regarding a problem… it means we have a bunch of clicks to merge the two tickets together.

---

<div class="post-metadata">

**Author:** ![EricRthePM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ericrthepm/32/87988_2.png) [@EricRthePM](https://community.hubspot.com/u/EricRthePM)\
**Post date:** [May 4, 2021, 3:36pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/5 "2021-05-04T15:36:53Z")

</div>

Hi folks, My name is Eric and I am a PM on the Conversations team working on an exciting new feature that allows Inbox users to switch their communication channel with a visitor from chat to email and keep the conversation going within the same thread. If you are interested in getting early access to this feature and having your feedback heard, I’d love for you to express your interest by filling out the form linked below.

[Channel Switching opt in](https://docs.google.com/forms/d/e/1FAIpQLSeTOduAVOlwD3jGRqDiARWzH23iR2iZuG60sfNmiablxjp7cA/viewform)

Please note: As this feature is in early testing, we’re slowly introducing it to early requestors. Once selected to participate, we’ll reach out to let you know!

---

<div class="post-metadata">

**Author:** ![EricRthePM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/ericrthepm/32/87988_2.png) [@EricRthePM](https://community.hubspot.com/u/EricRthePM)\
**Post date:** [May 4, 2021, 3:37pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/6 "2021-05-04T15:37:17Z")

</div>

Empty

---

<div class="post-metadata">

**Author:** ![Steve](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/steve/32/63860_2.png) [@Steve](https://community.hubspot.com/u/Steve)\
**Post date:** [September 16, 2021, 12:33am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/7 "2021-09-16T00:33:31Z")

</div>

I agree this is great idea, it’s sometime I expected to be a feature already.

I just had an email reply to a conversation marked as spam, when I marked as not spam, it started a new conversation, very annoying.

---

<div class="post-metadata">

**Author:** ![PeterIngemann](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/peteringemann/32/41549_2.png) [@PeterIngemann](https://community.hubspot.com/u/PeterIngemann)\
**Post date:** [February 16, 2022, 9:08am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/8 "2022-02-16T09:08:41Z")

</div>

We are having the exact same issue. A lot of inbox mails and chats for the same ticket - flooding our inbox..

---

<div class="post-metadata">

**Author:** ![JAquila](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaquila/32/82396_2.png) [@JAquila](https://community.hubspot.com/u/JAquila)\
**Post date:** [September 9, 2022, 1:27am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/9 "2022-09-09T01:27:48Z")

</div>

While merging would be super helpful, just the ability to attach a conversation to an existing ticket would tremendously lighten the load for us.

---

<div class="post-metadata">

**Author:** ![DNichols](https://avatars.discourse-cdn.com/v4/letter/d/97f17d/32.png) [@DNichols](https://community.hubspot.com/u/DNichols)\
**Post date:** [October 4, 2022, 10:35pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/10 "2022-10-04T22:35:11Z")

</div>

This has become an issue for us as well. What is the recommended procedure for these situations?

---

<div class="post-metadata">

**Author:** ![LNarbonne](https://avatars.discourse-cdn.com/v4/letter/l/e495f1/32.png) [@LNarbonne](https://community.hubspot.com/u/LNarbonne)\
**Post date:** [October 5, 2022, 7:14pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/11 "2022-10-05T19:14:02Z")

</div>

We need this as well, please give us an update, it’s a baisc feature.

---

<div class="post-metadata">

**Author:** ![jounti](https://avatars.discourse-cdn.com/v4/letter/j/848f3c/32.png) [@jounti](https://community.hubspot.com/u/jounti)\
**Post date:** [November 21, 2022, 8:59am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/12 "2022-11-21T08:59:41Z")

</div>

That would be a very useful feature. We often have to search for the correct conversation because emails and chats are separated.

---

<div class="post-metadata">

**Author:** ![JustinK8](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@JustinK8](https://community.hubspot.com/u/JustinK8)\
**Post date:** [December 9, 2022, 2:03pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/13 "2022-12-09T14:03:08Z")

</div>

I am currently using Fresh Works (Help Desk, Chat and Contact Center) and you can create, combine, merge conversations, tickets and calls in in Help Desk. A call can be attached to any open ticket. A chat can me attached to any open ticket. Tickets can be merged.

If Hub Spot wants to really roll out a useful Service Hub I see this as a MUST ADD. I just started using Service Hub as a trial and see this as a major pain point, especially during any busy customer times.

Waiting to see where Hub Spot can take the next step on this as right now I do not see us moving forward with Service Hub. (Also inbound calling is not up to par with most services)

---

<div class="post-metadata">

**Author:** ![stevejobboo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevejobboo/32/30348_2.png) [@stevejobboo](https://community.hubspot.com/u/stevejobboo)\
**Post date:** [December 27, 2022, 3:01am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/14 "2022-12-27T03:01:10Z")

</div>

I get annoyed easy on the Hubspot conversations.  
I’ve made a form on the website and when the customer fill the form, it comes to Conversation inbox.

By the way, When when the customer reply to me, it doesn’t come to the same conversation.  
I get more chats than the context. I want to manage same context in the same conversation.  
So please make this feature!

---

<div class="post-metadata">

**Author:** ![techops](https://avatars.discourse-cdn.com/v4/letter/t/53a042/32.png) [@techops](https://community.hubspot.com/u/techops)\
**Post date:** [March 12, 2023, 6:26pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/15 "2023-03-12T18:26:27Z")

</div>

Is there an update to this suggestion from two years ago?

---

<div class="post-metadata">

**Author:** ![DhContreras](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dhcontreras/32/6375_2.png) [@DhContreras](https://community.hubspot.com/u/DhContreras)\
**Post date:** [March 15, 2023, 7:50pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/16 "2023-03-15T19:50:40Z")

</div>

This is a significant pain point easy to identify even in the initiation process of working with a new Service platform. If your customers are messy, and most customers are messy via email, this is a major roadblock if it’s not fixed/added as a feature.

---

<div class="post-metadata">

**Author:** ![coamyot](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/coamyot/32/95715_2.png) [@coamyot](https://community.hubspot.com/u/coamyot)\
**Post date:** [March 29, 2023, 6:32am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/17 "2023-03-29T06:32:15Z")

</div>

Update? We need this. Wasting time managing a mix of multiple conversations for single issues. Waste of time, ressources and business as our customer suffer from the lack of cohesion.

---

<div class="post-metadata">

**Author:** ![PAlessiKrarup](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@PAlessiKrarup](https://community.hubspot.com/u/PAlessiKrarup)\
**Post date:** [June 12, 2023, 11:18am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/18 "2023-06-12T11:18:25Z")

</div>

This is really needed!

---

<div class="post-metadata">

**Author:** ![VMPYX4](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/vmpyx4/32/31184_2.png) [@VMPYX4](https://community.hubspot.com/u/VMPYX4)\
**Post date:** [August 16, 2023, 7:23am UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/19 "2023-08-16T07:23:58Z")

</div>

+1 on this idea!

---

<div class="post-metadata">

**Author:** ![Lara\_Q](https://avatars.discourse-cdn.com/v4/letter/l/cab0a1/32.png) [@Lara\_Q](https://community.hubspot.com/u/Lara_Q)\
**Post date:** [August 21, 2023, 2:11pm UTC](https://community.hubspot.com/t/merge-support-conversations-together/34093/20 "2023-08-21T14:11:58Z")

</div>

This is super important and a basic feature on any support CRM. We had today a customer reaching out twice via email, once on chat and once on WhatsApp all about the same subject. We need to be able to merge this as one because it is one case.  
If we close 3 of the conversations and respond to the fourth, we cannot even document it as conversations do not have numbers like tickets, so we cannot say: responded on conversation 12345678

[Next page](https://community.hubspot.com/t/merge-support-conversations-together/34093.md?page=2)
