Feature requests

See how many conversations were handled about what topics

How many end-users gave feedback How many end-users gave thumbs up How many end-users gave thumbs down

A way to see what you've done / what your colleagues have been doing, and the possibility to go back to an earlier version.

I would like to automatically crawl my URL's in the Web Crawler every X time, instead of having to manually select 'Crawl' to recrawl my URL's

Currently, the AI Agent responds to every image a customer sends. However, when multiple images are sent consecutively, the bot responds multiple times, which can overwhelm customers and create a spam-like experience. We propose introducing the following improvements for handling images: Option to Disable Image Responses: Allow administrators to disable automatic responses to images entirely. Single Response to Multiple Images: Implement logic to detect if multiple images are sent within a short time frame and respond only once to the first image or batch of images. Trigger for Human Handoff: Provide an option to automatically trigger a handoff to a human agent whenever a customer sends an image. This is particularly useful for cases where customers send images to report issues, such as damages or defects.

E.g. if someone asks if they can still add something to their order, they can before 2:00 pm, but after 2:00 pm they can't. It would be nice to have the AI Agent know what time it is and give an answer based on that.

When the end-user is logged into a customer/client/patient portal, we want to know who's logged in and see from who the conversation is coming. So automatically retrieve customer data.

E.g. when the AI Agent answered correctly and I always want to see this answer regarding this certain topic in next conversations, I want to give a thumbs up.

An additional verification step when e.g. retrieving order status. In addition to entering the order number, users should also be required to provide either their email address or postal code (NAW data) for verification purposes. The system should then cross-reference this information with the order tool, ensuring that the order number matches the provided email address or postal code. Only if both pieces of information align should the order status be displayed to the user.

You want to be able to 'chain' requests after each other in Actions. This way you can for example first get an warehouse ID for a product, to then get the the stock information of this product.