Change is the only constant at Meldus. We push hard to constantly improve our products based on your feedback. Learn more about our history of fixes and enhancements.
You're always in control of your data history with Meldus, which is why, from launch, we've provided users the ability to purge their data history from Meldus. We've now introduced a new shortcut command to allow users to purge their data history directly within the Meldus app.
Simply enter the new mel history shortcut command in the message compose box and send it to Meldus. You'll be presented with a card with two options to delete your data history from Meldus.
Rest assured, deleting your data from Meldus leaves your data in Salesforce and Microsoft Teams as is.
This is a modest feature introduction, but one that reinforces our commitment to providing you control over your data history with Meldus at all times.
We received handy feedback that, for new users, the step of connecting to Salesforce can be a little daunting. Newcomers to Meldus needed more clarity around how Meldus connects to Salesforce, how it uses that connection, and that users can disconnect at any time.
We've now clarified the wording on our Connect to Salesforce card to provide more information and streamline the connection step for new users.
Fixed an issue in the Tour that caused a tour step to fail for users who are yet to connect to Salesforce.
We strive to make getting started with Meldus as simple as possible. So we've streamlined our initial experience for new users.
When you install Meldus into Microsoft Teams, our new welcome message makes it super simple to quickly learn what Meldus can do. Start our welcome tour with a simple button, and we'll guide you through some examples of Meldus in action, answering questions of Salesforce just using demonstration data.
From there, it's simple to connect to Salesforce and try Meldus for real. Easy!
Adjusted wording on the Getting Started card, to help guide early users to the awesomeness of Meldus more easily.
Fixed an issue affecting some users where the Salesforce connection required re-login too frequently.
Improved the bot's handling of calendar-related questions:
Introduced handling of “my” and “I” questions, such as:
Meldus is now able to better use the context of your Salesforce user login to return results from Salesforce that you own or that relate to you. So let your ego run wild and ask the "my" questions you need.
Tuned the bot’s exec summary to better summarise calendar events chronologically.
Fixed an issue where the bot formatted date parts such as years, quarters and months as numbers; now correctly formatted as text.
Introduced locale-based dates. Dates in results from Salesforce are now formatted based on your locale setting in Salesforce, and dates and times reflect your timezone setting.
Tuned the bot’s understanding of more complex, multipart user questions and improved its ability to separate them into executable commands to Salesforce. We continue to fine tune the bot so it answers questions as often as possible with one command to Salesforce, and resorts to a multi-command approach only when absolutely necessary. It’s a tricky business, but we’re getting better all the time!
Removed retry on no rows returned: the bot previously made a second attempt to answer a question if the first attempt returned no rows from Salesforce, in case the empty result was caused by the bot making an error. As the bot has improved its accuracy, we removed that retry mechanism, which improves performance and usability, especially for multipart questions.
Removed name personalisation from the exec summary to avoid confusion as to the ownership of records returned from Salesforce. For example, the bot was summarising a company-wide sales pipeline with “Hilda, your pipeline shows strong performance …”, which could create confusion.
Name personalisation: Meldus now consistently understands your name, so it’s just a little more friendly. Your name is derived from your authentication via Microsoft 365.
Introduced shortcut commands to apply number abbreviations in Salesforce results tables:
Minor fix to font rendering in charts on Mac OS.
Extended Salesforce token refresh period.
Fixed a minor bug with disconnecting from a Salesforce sandbox connection.