Location Entity

The locations' enrichments weren't consistently performed due to some rate limiting we were experiencing with the provider that we use to perform geocoding. We've fixed the issue, and everything is now back to normal.

We've also added a new field to its enrichment: country. This field contains the ISO 3166-2 code of the country of the detected location.

Now, your LOCATION entity looks like this:

  "formatted": "41000 Blois, France",
  "lat": 47.58609209999999,
  "lng": 1.3359475,
  "place": "ChIJXdLII5VX40cRsCk4BdfIDQQ",
  "type": "locality",
  "country": "fr",
  "raw": "Blois",
  "confidence": 0.84

Transfer Logs

You can transfer logs from one bot to another. You can use this when forking a bot to work on a new version. Just before using the new version as the productive one, transfer the logs from your current bot to the new one.

  1. Go to the settings page for your bot and click Danger Zone.
  2. Click the Transfer All Logs button and select the new bot.

You'll receive an email notifying you once the transfer is finished.

Bot Builder Webhook Action

At many points in your conversation, you probably want to retrieve business information, connect to an external system, or simply ping a monitoring service. You can do this through webhooks.


We've released a new version of the webhook action to let you customize your HTTP requests and make them more complete and secure:

  • You can specify the HTTP method to use in your webhook call (GET, POST, PUT, or PATCH)
  • You can configure basic authentication
  • You can configure a key-value pair for headers
  • You can either use the default body we already provide with the conversation state or create your own custom body

Plus, you can save everything as a template to reuse each component and make your webhook configuration easier!

Usage Metrics

You now have access to usage metrics detailing how your bot is used, for example, the number of conversations and users, how many messages are sent every day, month, and year, and which skills or intents are used the most.


All metrics are extracted through the Bot Builder from the conversations that users have with your bot.

Most metrics are filtered by one of the languages of your bot (except for some graphs, where indicated) and a time range that you can select.

You can now see in real time:

  • Number of conversations (A conversation is a sequence of interactions between your bot and your users. When no new messages appear in the conversation for 10 minutes, we consider the conversation to be over.)
  • Number of users
  • Number of messages received (All messages sent by your users are considered as messages received when the users type a sentence, but also when they click on a button or quick reply.)
  • Average messages by conversation
  • A typical day and week (based on the number of messages received)
  • Most used skills, intents, and entities

Intent Description

All your intents can have a description. We added this description field in different places in the platform to let you interact with it:

  • In the result of the /request API endpoint, you'll now receive the descriptions of the matched intents in addition to their names and our confidence level.
  • In the Bot Builder, you can now use the intent's description in all of your conditions: intent-desc

Fork Bots

  • We were experiencing some trouble with big bots (with more than 200 intents) on basic actions, like a fork. We've improved the behavior of the fork feature for both small and big bots.
  • You can now be a member of organizations. When forking a bot, you now have to select if you want the bot forked in your account or in an organization (and if so, which one).
  • We've fixed the counter of forks that could be negative.

Organization accounts

Organization accounts let groups easily create bots together. They're shared accounts, allowing all members of the organization to collaborate on multiple bots at the same time with the same level of permission.


Some key features:

  • From your profile, you can create private and public organizations
  • Only administrators can update the members' list and change the organization settings
  • You can transfer your own bots to a new organization by going to the Settings page for the bot and clicking Danger Zone

More details in the documentation.


We've updated our webchat:

  • Few minor fixes on the Quickreplies component
  • Better browser compatibility on Apple Safari, Mozilla Firefox, and Microsoft Edge
  • A total mobile UI rework, so you can embed the Recast.AI webchat in a webpage and have a smooth experience on mobile too.

If you're not using it, check out this little demo to understand how to plug your chatbot to your website:


And remember, this project is open source on GitHub and the code is available here: https://github.com/RecastAI/Webchat

SAP Jam Integration

Newcomer from the SAP family! SAP Jam as a channel, a collaborative software for enterprise. If you use it and want to create a bot and deploy it there, you can!

A complete tutorial to understand how to connect your bot to SAP Jam is available here.

Screen Shot 2018-06-06 at 15.12.52.png

Slack Integration

We've just released a bugfix for the Slack integration. If you've experienced issues connecting your bot to Slack, please try the following steps:

  1. Remove your bot from your workspace (https://<workspace>.slack.com/apps/manage)
  2. Re-authorize your bot as described in the last step of the Slack integration in the Recast.AI dashboard:

Your bot is now live, share the URL with your friends! https://slack.com/oauth/authorize?scope=bot&client_id=SLACK_CLIENT_ID

No published changelogs yet.

Surely RecastAI will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree