All ideas

Today, teammates can be given different sets of conversation permissions (e.g. ability to send a reply) between different Workspaces. However, creating a dedicated Workspace just for this purpose can be over-the-top and have undesired side effects...

Ability to clone/duplicate existant knowledge base articles.

Open rule templates to individual and company rules for a more seamless and accurate rollout. Example use cases: main Highway use case revolves around using the rules and macros in a personal inbox. The rules and connectors we published are only s...

Bots often add "attachments" or "blocks" with additional message content. These are not included in the message text since their intended use seems to be for "lower priority content", according to the Slack docs.

Logging this idea for a client: "Were you able to identify options for mass rule uploads outside of API IDs? I have teams asking me to make appts to set rules and leverage functionality. Rules are such an important feature and it would be awesome ...

We would like to be able to customize the chatbot flow / serve our customers different flows depending on specific customer attributes (i.e., contact fields). Different customers fall under different categories in terms of how we will provide supp...

It would be useful to prevent delays in Front and opening attachments. If we can set up a scheduled time every day to automatically clear cache and refresh instead of doing it manually and per user.

Currently, shared contacts are shared with everyone in the company rather than by workspace. I'd like to be able to separate out shared contacts to specific workspaces, rahter than to everyone, to avoid confusion and support our security team's le...