All ideas

When calling the fetch rule API endpoint, you are returned with minimal information (name and actions). It would be more ideal if there was reusable information fields such as which inbox is being impacted (inbox ID) and which tags are being appli...

Now that the core API supports groups, it would be nice to be able to add custom fields to them as well. For my use case, I want to add a boolean value to tell my application if users should be allowed to add themselves to the group via API.

I wish to ask a question and get an AI answer without having to read the entire conversation(s). For example: I'm in a conversation and I'm looking for a specific information ("what is this customer saying about X") I'm looking at the analytics ab...

It'd be great if we could add a blank field as a variable for the user to fill in, instead of a pre-generated field. This is something Yesware and Zendesk have

Twitter is pretty much a redundant platform and these default fields for a Contact are unnecessary clutter for the vast majority of Contacts.

This would allow you to add a filter for only conversations where your rule triggered, e.g. allowing you to focus on the breach/achievement of your teams' rules only without other rules also being considered in the displayed results.

As soon as there are more than 10 conversations contributing to a metric, it becomes very difficult to filter them further. Being able to save the metric results into a view would make them easier to view within the app or to group together so tha...

Tracking the total number of message of a conversation