# Stop email conversations reopening **URL:** \ **Category:** Tickets & Conversations\ **Created:** [June 22, 2022, 3:49pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565 "2022-06-22T15:49:13Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![AHooper8](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@AHooper8](https://community.hubspot.com/u/AHooper8)\ **Post date:** [June 22, 2022, 3:49pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/1 "2022-06-22T15:49:13Z")
When an email is replied to and closed, and then subsiquently replied to by a customer some time later, HubSpot automatically reopens the conversation. This in itself is great but it keeps the conversation assigned to the original person. If they are on holiday or sick, this is easy to miss. HubSpot is set to have auto assign off, but it still leaves reopened conversatrions assigned to the original team memeber. Is there a way to get reopened conversations to go back to unassigned, or to start as a new conversation? ---
**Author:** ![CateDuarte](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/cateduarte/32/78852_2.png) [@CateDuarte](https://community.hubspot.com/u/CateDuarte)\ **Post date:** [June 22, 2022, 4:52pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/2 "2022-06-22T16:52:59Z")
Hi @AHooper8 , Would this help? [https://community.hubspot.com/t5/Tickets-Conversations/How-to-stop-automated-assignments-with-conversations/m-p/587541#M3198](https://community.hubspot.com/t5/Tickets-Conversations/How-to-stop-automated-assignments-with-conversations/m-p/587541#M3198) I guess its the issue you are having. ---
**Author:** ![AHooper8](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@AHooper8](https://community.hubspot.com/u/AHooper8)\ **Post date:** [June 23, 2022, 9:38am UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/3 "2022-06-23T09:38:26Z")
Unfortuantly not. I already have it set to not auto-assign. The way we work is emails come in and it doesn’t auto assign. They then get allocated an owner, are dealt with and the converstion is closed. If the customer then replies again the original conversation/email thread reopens against the same owner. If that person is on holiday, it is very easy to miss. What would be better would be if it reopened not assigned, or started a new conversation. ---
**Author:** ![DanMYD](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmyd/32/106381_2.png) [@DanMYD](https://community.hubspot.com/u/DanMYD)\ **Post date:** [January 5, 2024, 3:09pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/4 "2024-01-05T15:09:29Z")
One option is to setup a workflow where it triggers if a ticket status “has ever been any of” Closed and the current status is any of the other ticket status. Then you can clear the ticket owner property or rotate it to another team member. Or you could have it close the ticket again and then create a new ticket. With both these options, you’d want to think about how that impacts reporting though. ---
**Author:** ![AHooper8](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@AHooper8](https://community.hubspot.com/u/AHooper8)\ **Post date:** [January 11, 2024, 4:01pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/5 "2024-01-11T16:01:23Z")
Hi Dan, this would definitly make a mess of reporting but what I have managed to do is create a workflow where if the “last message received” date is updated after the “close date” (both conversation properties) then a new ticket is raised. ---
**Author:** ![DanMYD](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/danmyd/32/106381_2.png) [@DanMYD](https://community.hubspot.com/u/DanMYD)\ **Post date:** [January 11, 2024, 4:26pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/6 "2024-01-11T16:26:22Z")
Very nice. There always seems to be a trade off with these workarounds! 🙃 ---
**Author:** ![MBlock6](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@MBlock6](https://community.hubspot.com/u/MBlock6)\ **Post date:** [January 26, 2024, 4:19pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/7 "2024-01-26T16:19:20Z")
hi there! could you screenshot the steps you used to create this workflow? I’m getting tripped up on the close date. thank you!! ---
**Author:** ![PamCotton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pamcotton/32/47916_2.png) [@PamCotton](https://community.hubspot.com/u/PamCotton)\ **Post date:** [January 26, 2024, 9:14pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/8 "2024-01-26T21:14:22Z")
Hi, @MBlock6 while we wait for **@AHooper8** reply, users in accounts with Service Hub Starter, Professional, and Enterprise subscriptions can automate ticket status and certain actions within a pipeline’s settings. For ticket automation beyond the options below, users in Service Hub Professional or Enterprise accounts can create [ticket-based workflows with more advanced actions](https://knowledge.hubspot.com/workflows/choose-your-workflow-actions). Kindly, Pam ---
**Author:** ![AHooper8](https://avatars.discourse-cdn.com/v4/letter/a/b5ac83/32.png) [@AHooper8](https://community.hubspot.com/u/AHooper8)\ **Post date:** [February 13, 2024, 1:19pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/9 "2024-02-13T13:19:38Z")
Hi, I actually had to change it again afterwards and add a branch in. Without the branch it just sent an email every time: ![AHooper8_0-1707829944762.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/b/b622c5db704ec08aafd0c3d1306e39f62f48f8a5.png) ---
**Author:** ![PamCotton](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pamcotton/32/47916_2.png) [@PamCotton](https://community.hubspot.com/u/PamCotton)\ **Post date:** [April 10, 2024, 3:19pm UTC](https://community.hubspot.com/t/stop-email-conversations-reopening/59565/10 "2024-04-10T15:19:39Z")
Hey @AHooper8, Thank you for the screenshot. After changing, did it resolve it or do you still need help? Kindly, Pam