Form successfully submitted! Please check your inbox.
Product Newsletter February 26th
You now have the ability to interface with our SupportBot directly and access to several new features and improvements to the platform.
Helloooo!
Inbetween watching re-runs of Seinfeld and shamelessly stealing gifs from there, I've put together a product newsletter to help you stay updated on the platform's newest features and improvements.
What's new:
Added a snazzy little SupportBot to keep you moving forward.
Gave the Debugger a serious tune-up to help you understand your bot.
Added the ability to use Jinja code directly in Connections.
SupportBot - Your Personal BotXO Assistant
We're excited to announce the public beta release of the BotXO SupportBot.
Outfitted with a comprehensive NLU, and seamlessly integrated with our customer support systems, the SupportBot is here to help you with any questions you might have in relation to the platform.
The SupportBot is located in the bottom right of almost every page of the BotXO Platform and has page-specific tips and tricks to help you with exactly what you're doing. Because of its integration with our support systems, it is also able to create a support ticket for when your issue goes outside the scope of what the SupportBot covers.
The SupportBot is the first step towards a personalized experience when working with BotXO and we hope that it is looked to not only as a source of support directly in the platform but also as a showcase of valuable features that you could include in your own bot(s).
As you can tell from the gif above, we've added some serious depth to the Debugger (and are continuing to add more!).
The three new features we've added are:
The ability to set the initial variables of a conversation.
For when you want to test the behaviour bot when specific variable values are supplied.
Displaying whether a webhook succeeded or failed.
Useful for pinpointing the fundamental cause for an end user's flow going wrong.
The ability to reset the chat without leaving the tester.
A quality-of-life change with the added benefit of remembering the initial variables you've set.
One important thing to be aware of:
If you haven't updated your styling options in Bot Settings in a while, you might experience that the Debugger is not available to you. In order to fix that, you will need to make a tiny change in the styling options of your bot and save. After saving, the Debugger should be displayed when hitting "Test" in the top bar. You can, of course, revert the change you make instantly after saving.
Jinja Code: The Art of Knowing What Your Users Want Before They Do
I know the words "Jinja" and "Code" are not sources of unbridled excitement among most people, but if you bear with me for a second here, I'll tell you just how exciting this feature actually is, and how much value it can bring to your chatbot.
We automatically store some data provided to us from different channels like Facebook and Zendesk. That data contains important information such as the country that the end user resides in, or what page they're currently navigating. This information can help us drive the conversation to certain modules based on what that data contains.
Let's say you have a user who activates your widget while navigating your pricing page. When the widget pops open, the user asks about pricing since that's what they're interested in. But why should they need to? Wouldn't it be better if the bot already knew to ask the user about pricing?
With the addition of being able to use Jinja Code in Connections, you'll now be able to use any of the data we store (we call them Reserved Variables) to achieve exactly that.
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:
As always, we've been fixing some things to make your life a little easier:
Some users would experience an error when trying to deploy a bot to a Facebook page.
When closing the NLU Dashboard while training the NLU, there was some inconsistent behaviour exhibited in the state of domains.
When using two underscores in a custom variable, the value in between the underscores would turn italic and would result in the value not matching anything in subsequent connections.
When the list of custom variables available for use in a given bot reached a certain length, it was impossible to scroll through them.
Known bugs:
Inbox is inaccessible and hidden from view.
When a single connection contains two or more webhooks fired in succession, then the value returned by the last webhook is not saved.
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:
