Form successfully submitted! Please check your inbox.
Product Newsletter November 13th
Global Connection performance improvements, new matching rules, and more.
It's time for another update from the team at BotXO.
Improvements to the performance of Global Connections.
Added numeric matching rules for connections.
It's now possible to define a default fallback module for when no fallback is defined. This will help prevent end users from stumbling into dead-ends.
New highlighted Webhook Templates (some really cool ones).
Continue reading to find a detailed description of our new additions.
Gotta go fast!
The internet is abuzz with news of the new Sonic movie, so we can think of no better time to release some much-needed performance improvements to our Global Connections.
Starting today, bots that contain many Global Connections should see a marked difference in both the loading speed and general performance of the Global Connections view.
It's important to note that even though this update has drastically improved the performance, we're still working on additional changes that will improve it even further.
Once the final improvements are complete, not even Doctor Eggman will be able to keep up with you.
Numeric matching rules
We've added a number (ha, get it?) of numeric matching rules for you to match connections by. The previous matching rules all related to text-based input which made it hard to work with numbers, but with the new matching rules, it's as easy as pie.
It's available in both "response to" connections, and "custom variable" connections, and the new matching rules you can use are:
Equals, does not equal, less than, greater than, less than or equal to, and greater than or equal to.
We've added a new function in Bot Settings that allows you to specify a default fallback module for when no fallback is defined.
This ensures that whenever a connection is not met, and no fallbacks are defined for that module, the conversation will always have the default fallback module to rely on.
Never again will an end user stumble into a dead-end, and have the conversation start all over again.
Highlighted Webhook Templates
As is tradition, we've added some new Webhook Templates for you to play with.
The first template is BotXO Sentiment Analysis v2, which determines whether an end user reply is positive, neutral, or negative. Whereas the first iteration of this Webhook Template only supported Danish, this one supports 11 languages: Danish, Dutch, English, Finnish, French, German, Italian, Norwegian, Polish, Spanish, and Swedish.
The second template is Slack Message Sender, which can be used to send a message to Slack. The use cases for this template are practically endless, as you can append any information you desire to the message. It can be used to, for example, notify your customer support team that an end user wants to get in contact with them:
The third template is Zapier Trigger Zap, which opens up a world of possibilities for adding value to your company. It's a task automation platform that has pre-built integrations with a ton of different systems. With this template, you'll be able to trigger the workflows defined in Zapier to execute any number of tasks, like creating a contact in HubSpot when an end user shows interest in being added to your mailing list.
We have been fixing bugs and improving performance, for example:
Fixed: In the Webhook Builder, users were unable to use "-" in input fields.
Fixed: Users were unable to edit a webhook that used a private webhook template.
When using the new numeric matching rules in connections, and inputting numbers with decimal delimiters like ".", and having three numbers after the delimiter, the number is treated as thousands, not as decimals.
After saving a Webhook that was created from a Webhook Template that pre-filled authentication details, the user will be prompted to fill in the API password. For now, the solution is to ignore this field as the webhook will work regardless.