Messages Count
Last updated
Last updated
One of the main counters of your account is the Messages Count.
As you move upward from free to professional or agency plan you will see the available messages pool greatly increased.
Xenioo messages are used as a means of counting how much your chatbot is used and are, most of the time, directly determining the cost of your chatbot.
In the following paragraph, we will explore how this counter is affected by messages, operations, and integrations.
Very simply: every time your chatbot replies to any of your users, we count one message.
A single bot reply may be comprised of multiple elements: for example, it could be made of two text lines and three quick buttons: all the block is still counted as one message by Xenioo.
In the image below, your chatbot is displaying a single line of text. This is counted as one message.
In the image below instead, your chatbot is displaying 2 bubbles and 4 buttons. Still, this is counted as one message.
For both cases, Xenioo will count just one message.
After you publish your bot, pay close attention to its real-time statistical dashboard and follow closely its success verifying how many messages are used daily.
Message count has no impact on how you build your Interaction (Interactions define a group of actions but do not affect how messages are counted).
Any message sent or received inside the preview section, where you test and try your chatbot before publishing, DOES NOT count toward your paid account messages.
Any action that requires integration with external sources to retrieve or synchronize data will increase your messages counter by 1 upon execution.
Any external web service or API call, any Firebase or DialogFlow or IBM Watson integration will increase your message counter as well.
A chatbot that retrieves data from an API REST endpoint and displays the result to the user will, at least, consume 2 messages from your account quota.
Please note that the message is counted as the action executes and not if any result is produced. For example, a broadcast sending news to multiple users based on the results of an API call or RSS feed may not send any message until there's an actual news but still be executed by Xenioo multiple times each day. All of these executions will add to your premium counter.
All of these actions stated below will generate an additional message during chatbot execution.
Action
Mode
One additional message for each message evaluation, regardless of number of actions
One additional message for each message evaluation, regardless of number of actions
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message per action.
One additional message for each analyzed feed source.
One additional message for each action that changes a database collection(save, delete)
Time Out
Xenioo API Actions have by default a 10 seconds timeout. If you require a higher timeout please make sure to get in touch with us at team@xenioo.com.
When the timeout is increased, any call using more than 30 seconds will count for an additional premium message.
The Events Webhook will automatically transfer to a provided hook URL multiple events happening on Xenioo backend for a specific chatbot.
Calls to this hook count as messages outgoing and will be summed to your account messages count.
Message counters are reset on the 1st day of every month.
Xenioo will automatically send you the first message whenever your messages usage will rise above 80% and a second one when it reaches 90%.
If you finish the number of available messages before the end of the month, your chatbots will stop replying to your users as they don't have any more messages to use.
You can add more messages to your account by simply adding additional packages or switching to an unlimited message model by adding the no-limits package that can bill every message outside your standard messages count separately.
The no-limits option can prove very useful if you have chatbots that can have high traffic only in specific months during the year.
