Improvements

It would be very interesting for us to be able to make comparative views between two time periods in different moments of history. As an example, we would like to have the ability to compare May 2022 with May 2023.

🔗 Metadata Ability to select if a ticket should be tagged only if it matches a specific metadata field (e.g. customer subscription type). 📧 Channels Only tag the ticket if it's from a specific channel, like email. 🌅 Attachements "It would be great if Lang was able to tag tickets only if they include a picture, or add another tag if the ticket doesn't include a picture, since there will be an opportunity for automation."

It would be helpful if the Lang admin was able to see who submitted the tag with the option to provide feedback. If the tag is incorrect, it would be great to have the option to delete the tag because right now I am only able to set it live.

Ability to create intents on-demand based on a short sample of texts. This is useful when a specific intent wasn't generated initially due to low volume or relevance.

I would like to see a changelog for each project in Lang so that he can keep track of any changes that were made in the project. This would also be helpful for documentation purposes as an admin.

I want to understand what a tag is actually tagging to get a better sense of my evolving taxonomy. This is not easy to do right now. Tag configurations might have dozens of components like concepts that logically combined with other rules, sometimes making it hard to understand what a tag does from a first glance. This is also relevant as the tag evolves in time.

It would be very useful to be able to scroll to see more than 3 samples when choosing n intent or keyword while creating Tags.

Summarize dashboards key information in 4-5 sentences to quickly understand what's behind key growth drivers, outliers, etc.

New section where all the key information across the platform is centralized, making it easier to have a quick look at metrics and performance indicators.

It would be nice to see when a customer writes in multiple times about the same request. Zendesk does not provide a way to identify these tickets today, and ideally we would be able to apply a "duplicate ticket" tag and then take merge them