Form successfully submitted! Please check your inbox.
Product Newsletter June 19th
We've changed the conversation handling to improve the scalability of the platform. This release also contains changes to the way that messages are handled in Zendesk, as well as a lot of bug fixes.
Hello!
It's time for another product update from the team at BotXO.
In this update, we'll be highlighting a big change we've made in the way that conversations are handled in the platform, some changes to the way messages are handled in Zendesk, as well as releasing a whole lotta bug fixes.
What's new:
Change in conversation handling.
Change in our handling of messages in Zendesk.
New blog posts to keep you up to date on the latest news within the Chatbot world.
New webhook templates for the platform Pipedrive.
Bug fixes for days.
Keep reading to find a detailed description of our new additions.
Change in conversation handling
In the past few months, we've been working on decoupling the part of our platform that handles conversations. The reason for doing this is that it will offer us far greater scalability in the future while improving the performance of our conversation handling overall.
We're happy to tell you that this change in conversation handling has now been completed successfully.
While you probably won't see any noticeable change on your end, this represents a noteworthy milestone in ̶o̶u̶r̶ ̶q̶u̶e̶s̶t̶ ̶f̶o̶r̶ ̶w̶o̶r̶l̶d̶ ̶d̶o̶m̶i̶n̶a̶t̶i̶o̶n̶ our product roadmap.
Change in our handling of messages in Zendesk
We've made a number of changes to the way that messages are handled in the Zendesk Chat Widget.
Previously, we were unable to process the first message sent by the end user in cases where the Connection Evaluation order "Module Connections, then Global Connections" was selected.
We've changed this behaviour so that we're now able to process the first message sent by the user regardless of the Connection Evaluation order chosen.
If you have any questions about what this means for your existing configuration, don't hesitate tocontact us.
Recent blog posts
To help you stay up to date on the latest trends within the world of AI and chatbot development, we're throwing a blog post your way to help you stay current:
On the menu today, we have a selection of webhook templates for the platform Pipedrive.
The first webhook template is Pipedrive Add Organization, which lets you fire a webhook that creates a new organization inside your Pipedrive environment. This webhook template is designed to work in conjunction with our other two Pipedrive webhook templates, in order to create a Deal in Pipedrive.
The second webhook template is Pipedrive Add Person, which uses the organization ID generated by the Pipedrive Add Organization webhook template, in order to add a new person to that specific organization. Once fired, it will generate a person ID that can be used in order to add a Deal in Pipedrive.
The third webhook template is Pipedrive Add Deal, which uses the organization ID and person ID generated by the two previous webhook templates in order to add a Deal in Pipedrive. Deals represent ongoing, lost, or won sales in Pipedrive. It's a great tool to let your Sales team keep track of new leads.
Psst! If there's a specific platform that you'd like us to integrate with, let us know.
As always, we've been fixing some things to make your life a little easier:
Users were unable to remove default NLU domains from their NLU dashboard.
The descriptions of webhook templates were improperly shown in Connections.
In some cases, the first message of a conversation had some inconsistent behaviour in Message Reports.
Console error would occur when copy-pasting certain modules within a chatbot.
Advanced Reports function in Message Reports would send an Excel file with no data in it when the fromDate and toDate were the same dates.
Bots with a specific version (how many changes the bots had undergone) would create new sessions for all active conversations when the bots were published.
An error message would be displayed when accessing a Facebook Messenger conversation in the Inbox.
Modules that had the flag "Don't wait for user input, just evaluate the Connections" and featured a Custom Variable Connection that had Jinja code in it, made the flow break.
Agencies were unable to view webhooks belonging to Child Companies.
The values of Custom Variables would be unable to be displayed after going through a Global Connection.
The "Go to previous" function in Bot Settings had a number of inconsistencies that are now improved.
Known bugs:
Custom Groups, when created and changed by the Bot Operator, will default to the original name and colour.
Please see our known bugs article for a list of unsolved long-term bugs.
Get in contact with us
Whether you need assistance from our Customer Success team, want to request a new feature or search for an article in our knowledge base; we love being in contact with you.
Get access to all features for 14 days and try out our technology for free. No credit card required.
Book a Demo
Please fill in your information below to receive a guided tour of the BotXO Platform and have a talk about your use case.
Learn more about our NLU engine.
We’re thrilled to see that you’re interested in our NLU engine. Please fill in your information below and our humans will be in touch soon to give you a tour.
Sign up for our BotXO Essential Plan
We’re happy to see you’re signing up to the XO Essential Plan! Please fill in your information below:
Sign up for our BotXO Business Plan
We’re happy to see you’re signing up to the XO Business Plan! Please fill in your information below:
Sign up for our BotXO Enterprise Plan
We’re happy to see you’re signing up to the XO Enterprise Plan! Please fill in your information below:
