In June, we made major improvements to the document scanner and AI agent capabilities. You can now upload files to the knowledge source document scanner in just one click, streamlining the setup process. We’ve also enhanced our AI agents with better fallback handling.
Additionally, all bot builders now support follow-up messages, making conversations more contextual and dynamic.
Features
Auto-Upload Knowledge Source File
You can now upload your Knowledge Source documents into our Document Scanner with just one click.
Improvements
- We’ve added the “wrap text” functionality to the entity fields, so that the text will wrap around and be visible even when the number of entities is larger.
- We’ve added the latest Gemini models to Kommunicate.
- We’ve improved our support for table data. You can now preview and download tables. We’ve also improved our markdown support to add structured messages to your chats.
- We’ve added the ability to create follow-up messages to all the bot builders on our platform.
- If your AI agent is unable to respond to a request multiple times, it will now automatically hand off the conversation to a human agent.
- We’ve improved our inline code implementation. Now, you can import coding libraries like OpenAI while using inline code.
Bug Fixes
- We fixed a data discrepancy issue between the “Download Data” and “Dashboard Overview” sections to ensure consistent reporting across views.
- We resolved an issue in the Notes feature where agents were not receiving email notifications when tagged.
- We fixed a bug in the Web SDK where the answer feedback component and copy-paste actions displayed incorrect colors.
- We addressed a problem in the Excel Scanner where using comparison symbols in questions caused errors during parsing.
- We fixed a routing issue where, even after an agent came online and conversations were reassigned from the waiting queue, the default assignee’s name continued to appear in the UI.
- We patched a security loophole that allowed users to edit articles from other applications.
- We resolved a vulnerability where the package-lock.json file was unintentionally exposed.
- We fixed a security issue where password reset tokens were being leaked to third-party domains.
- We closed an HTML injection vulnerability that allowed malicious profile names to execute code in “Forgot Password” emails.
