# Tag chat conversation

**URL:** <https://community.hubspot.com/t/tag-chat-conversation/64695>\
**Category:** HubSpot Ideas\
**Tags:** conversations-inbox\
**Created:** [September 8, 2022, 1:28pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695 "2022-09-08T13:28:23Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![AnaisThomas](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@AnaisThomas](https://community.hubspot.com/u/AnaisThomas)\
**Post date:** [September 8, 2022, 1:28pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/1 "2022-09-08T13:28:23Z")

</div>

I want to tag chat conversations in HubSpot in order to identify them and create reports on these tags.

These would allow my company to see the topics of chats at the moment, create new articles on the knowledage base responding to the needs of our customers.

In the end, We would be able to see the progression of knowledge with the level of questions asked.

---

<div class="post-metadata">

**Author:** ![deisym](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/deisym/32/9373_2.png) [@deisym](https://community.hubspot.com/u/deisym)\
**Post date:** [September 23, 2022, 8:34pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/2 "2022-09-23T20:34:27Z")

</div>

Es una funcionalidad muy necesaria para la medición de consultas frecuentes, mejoras o sugerencias de los usuarios que se atienden usando la herramienta de Conversaciones de HubSpot.

---

<div class="post-metadata">

**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\
**Post date:** [October 3, 2022, 3:48pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/3 "2022-10-03T15:48:52Z")

</div>

I think the tag idea would make this a little easier and more seamless for teams.

We currently use custom ticket properties to categorize them and identify documentation updates, as well as associate to GitHub issues.

---

<div class="post-metadata">

**Author:** ![SteveHTM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevehtm/32/22074_2.png) [@SteveHTM](https://community.hubspot.com/u/SteveHTM)\
**Post date:** [March 15, 2023, 4:52am UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/4 "2023-03-15T04:52:10Z")

</div>

In general - it would be a great enhancement to have some writeable properties on the Conversations object. Or the ability to extend the object with custom properties like you can do with almost all other object types. Any custom code or clever parsing of the conversation content currently has no pace to out result values!

---

<div class="post-metadata">

**Author:** ![KRobertsson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/krobertsson/32/53612_2.png) [@KRobertsson](https://community.hubspot.com/u/KRobertsson)\
**Post date:** [February 7, 2024, 11:06am UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/5 "2024-02-07T11:06:07Z")

</div>

We would need this! U  
The workaround with creating tickets with tags is more complicated and not needed when you normally do not use the tickets…

---

<div class="post-metadata">

**Author:** ![RArvai](https://avatars.discourse-cdn.com/v4/letter/r/6a8cbe/32.png) [@RArvai](https://community.hubspot.com/u/RArvai)\
**Post date:** [April 2, 2024, 2:50pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/6 "2024-04-02T14:50:33Z")

</div>

We miss dearly this feature, it would be so great to have more options when it comes to conversations, tag would be one of them. Not all companies are ticket-heavy, live chat (without bots) is crucial for some companies, like ours.

---

<div class="post-metadata">

**Author:** ![CShaw44](https://avatars.discourse-cdn.com/v4/letter/c/b4bc9f/32.png) [@CShaw44](https://community.hubspot.com/u/CShaw44)\
**Post date:** [August 12, 2024, 9:42am UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/7 "2024-08-12T09:42:06Z")

</div>

I totally agree. It would be really valuable to tag the chats into categories to measure what people are coming into the chat to tak about. Really hope this feature can be implemented in the future!

---

<div class="post-metadata">

**Author:** ![KTheill](https://avatars.discourse-cdn.com/v4/letter/k/ecc23a/32.png) [@KTheill](https://community.hubspot.com/u/KTheill)\
**Post date:** [August 29, 2024, 10:24am UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/8 "2024-08-29T10:24:38Z")

</div>

This would be a great option to get an overview of the topics our customers enquire about

---

<div class="post-metadata">

**Author:** ![JGeraghty4](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@JGeraghty4](https://community.hubspot.com/u/JGeraghty4)\
**Post date:** [October 21, 2024, 2:19pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/9 "2024-10-21T14:19:56Z")

</div>

I just wanted to add my voice to the others here in saying that the ability to tag and categorise incoming mails would make hubspot inbox a lot more powerful. Tagging owuld enable us to assign certain easier topics to newly trained memebrs of the team, to identify priority clients and to assign and distribute work more evenly among our team. Thank you.

---

<div class="post-metadata">

**Author:** ![SteveHTM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevehtm/32/22074_2.png) [@SteveHTM](https://community.hubspot.com/u/SteveHTM)\
**Post date:** [October 22, 2024, 6:36pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/10 "2024-10-22T18:36:38Z")

</div>

Following up on the prior comment in this conversation - I agree that tags would be a useful option for conversations. If we generalize out from that idea, enabling the ‘conversation’ object to be **a fully grown up member of the record familiy** would open the door to his ide and many more! In ther words, having conversation property options appear in the ‘property settings’ menu would enable writable/displayable options to exist related to conversations (or message threads inside conversation) without needing to add a tag to associated properties (like contact).

Steve

---

<div class="post-metadata">

**Author:** ![KaydenMichael](https://avatars.discourse-cdn.com/v4/letter/k/2acd7d/32.png) [@KaydenMichael](https://community.hubspot.com/u/KaydenMichael)\
**Post date:** [December 10, 2024, 9:03pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/11 "2024-12-10T21:03:51Z")

</div>

This would also be helpful across business units - to see which site/brand initiatiated the conversation

---

<div class="post-metadata">

**Author:** ![JRosendal](https://avatars.discourse-cdn.com/v4/letter/j/85e7bf/32.png) [@JRosendal](https://community.hubspot.com/u/JRosendal)\
**Post date:** [February 17, 2025, 3:28pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/12 "2025-02-17T15:28:49Z")

</div>

Is it really not possible to add any tagging/closing codes towards tickets in Hubspot? How are we then supposed to do proper reports and make strategic data driven decisions based on all inbound activities on tickets handled by our support team using hubspot Service Cloud? This feature is perhaps the most basic feature within the omnichannel customer support handling platforms available.

As a support manager I need to file reports on all inbound tickets towards my part of the organisation. I missing having a 360 degree overview of the activities within my team and I don’t know into details what reasons our customers are contacting us about.

Please prioritise this

---

<div class="post-metadata">

**Author:** ![DonelleLL](https://avatars.discourse-cdn.com/v4/letter/d/e5b9ba/32.png) [@DonelleLL](https://community.hubspot.com/u/DonelleLL)\
**Post date:** [August 8, 2025, 2:38pm UTC](https://community.hubspot.com/t/tag-chat-conversation/64695/13 "2025-08-08T14:38:59Z")

</div>

Is this still not available? I desperately need this for our new selling channel that utilizes a specific bot within our Inbox. I do not want to create a seperate inbox. Is the only solution to create tickets? These conversations do not require a ticket.
