Changelog
Stay updated on our latest product features, improvements and fixes.
Previously, users could downvote a bot's response to indicate dissatisfaction. However, we lacked clarity on the reasons behind the downvotes, requiring us to speculate based on reviews of downvoted responses.
Now, with the new feedback mechanism, trusted users can select predefined reasons for downvoting and provide specific feedback, enabling us to promptly address issues and enhance the bot's performance. This streamlined process ensures that feedback is received promptly and reduces the risk of it being overlooked.
Next time you downvote a response, you'll automatically see these options available.
Scammers often target Discord servers, making members vulnerable to DMs impersonating team members. When attacks occur, server support is flooded with scam complaints. Now, you can disable server-wide DMs with a single click in bot settings. Grant the AwesomeQA bot 'Manage Server' permission to use this feature.
Many servers used languages other than English as their primary mode of communication in channels. When installing the AwesomeQA bot for support, they were only able to train it by uploading web pages like documents. Consequently, the 'chat history' wasn't accessible for the bot to learn from.
Now, the bot has the capability to learn from chat history for all servers, irrespective of whether the messages are in English or not. This feature has been enabled for all servers, providing benefits to every user.
Resolved a scraping issue with Google Docs, specifically when redirects were involved.
If a user downvotes the answer they received, a cooldown period is triggered to reduce further attempts, as subsequent answers are unlikely to improve accuracy.
Now, you can see the last update time for the web pages uploaded. This helps you know if those pages need to be scraped again due to recent changes.
Before, users had to delete multiple entries one by one from the knowledge base when different FAQ formulations existed. Now, only one entry appears, making the knowledge item deletion faster.
The bot now better understands whether it's in Discord or Telegram when answering questions, ensuring context-appropriate responses.
You can now configure the bot to learn from the FAQ channel in the server, similar to how you could for the announcement channel before.
Previously, even when tagged, the bot sometimes didn't generate an answer if it deemed there wasn't enough information. Now, it replies with whatever info it has, improving user experience.
Now, when missing information is added to the knowledge base, the bot's message about the absence of information automatically transforms into an answer to the question.
Previously, users faced inconvenience when manually adjusting permissions for each ticket channel created in the tickets category. Now, default permissions can be set for each channel category, simplifying the process.
Plus, users managing multiple servers can now access all permissions and configurations from one account, eliminating the need for multiple logins.
Also, sometimes there were missing channels on the permissions page, as they lacked 'view channel' permissions from the Discord side. With this update, such channels are now visible, enabling users to configure permissions easily.
To top it off, we have also improved the overall loading speed of the page. Visit your permissions page to explore these enhancements.
Now you can upload even Google Drive-hosted docs, spreadsheets, and presentations for bot training, which was not possible before. You can try it out in your web pages section right now.
The newly added FAQ items are instantly listed and available for all actions now.
A bug that initially hindered the web page scraping process has now been resolved.
Fixed the issue where the bot sometimes replied to questions in other languages in English.
The bot now properly hyperlinked channel names in its responses, allowing users to navigate directly to the channel with a single click.
Timeout errors reported during the extraction of FAQ insights from communities have been fixed.
The error notification on the dashboard during the AQA-Edit flow, when adapting answers on the web app and saving, has been fixed.
Newlines are now correctly formatted during generation. Previously, they appeared as "\n" while generating the answer but were formatted correctly once the generation was complete.
Implemented a performance improvement to address slow reload times for FAQ items on the Knowledge Hub after editing.
The issue where the correct dashboard wasn't opened by default through the 'add info' prompt from the channel chat, especially when users had access to multiple dashboards for different communities, has been resolved.
The bot now notifies you via Discord DMs once the training process is complete, eliminating the need for manual checking.
Think AwesomeQA was already quick? It was faster than most humans. With this update, it's lightning-fast!
We revamped our data structure for storing knowledge, turbocharging the retrieval process.
Result? Response time slashed by an average of 34%.
We understand how important it is for clear instructions to be available as you set up and begin to use the AwesomeQA bot. Now, if AwesomeQA is tagged but can’t reply, you will receive more specific guidance instantly in response to your question:
When no information exists: Instructions on how to add to the knowledge base will be given.
When ‘reply’ permissions are toggled off: The user asking the question in that channel will be notified.
During onboarding: Instructions on how to start the onboarding process will be provided.
During training: Information to wait for the training process to complete will be indicated.
We have further enhanced our feedback system by updating our emojis. To offer more clarity, feedback submissions from our trusted users will now include a "Mod certified" text in addition to the emoji. Thanks to ninefungerbils from Consensys for asking for it.
We experienced an issue with Telegram that affected the bot's ability to detect messages and learn from trusted users, resulting in some cases where learning was incomplete. This issue has now been resolved.
We have enhanced the onboarding process with clearer step descriptions, the integration of URL scraping rules into a tooltip on the docs page, the instant opening of tooltips on mobile, and an additional "Finish" button on the summary page.
Fixed an error happening when clicking on AQA-Add for any message that was not from AwesomeQA, as well as a formatting issue when links were part of the preview.
We have reintroduced pre-filled answers when you execute AQA-Edit. Earlier, due to a bug, the answers were not being pre-filled after executing AQA-Edit.
GitHub wikis can now be used as a documentation source.
Fixed an encoding issue related to the ‘custom footer text’ feature.
Fixed a bug that sometimes, due to caching, newly added questions from the knowledge base were not answered.
Bug fixes and performance improvements for discord feedback emojis.
We changed the feedback mechanism from reactions to buttons so that our bot does not have to vote itself. Further, we believe that the buttons incentivize users to provide feedback and are separated from additional reactions such as '💯', which do not contribute to the rating.
As a result of this change, you are no longer able to view who upvoted or downvoted an answer by hovering over the buttons.
To address this issue, we have implemented a new system based on feedback from cryptopia and 184eth of ensdomains:
When a Trusted user, such as an admin, upvotes an answer, a '✅' will appear to confirm the upvote.
Similarly, when an answer is upvoted by the author i.e. the person who asked the question, a '👍' emoji will be displayed.
Now you have the option to include a personalized message, such as a disclaimer, in the footer of the bot's responses from the settings page. This message can be up to 200 characters in length. This feature was created based on direct feedback from our customers, including Robots Farm.
We deployed a new version of our AI which reduces the number of wrong responses. We started focusing more on recent information, and now use all the available context to make a good judgment of what’s helpful and what isn’t.
Previously, when you wanted to edit a bot's answer, a link was provided through a hidden message after using the AQA-Edit command. However, there was a Discord bug that prevented some users from seeing this message with the link.
We have now added a clickable '🖊️' edit emoji directly on the message to solve this issue. This means that even if you cannot see the hidden message with the link, you can still easily edit the bot's answer by simply clicking on the '🖊️' emoji.
The support portal now shows tickets for all channels with learn or send permission
Fixed a timeout error that caused to bot ignore a small percentage of messages
Fixed a bug that caused our bot to not respond in the language of the question
Toggle all now shows the correct state if all permissions in the category are turned off
Fixed a bug where our website scraper would only find 1 page
Fixed a bug that if someone replied to a message more than 12 hours ago, the referenced message was not included as context for the AI
Fixed a bug that displayed the discord message in the support portal without content