Our experimental initiative to prototype a bot-ready information solution using Google’s Dialogflow

This post is part of a series. For more information and links to other posts in the series, see the “Building bot-ready knowledge bases” home page.

Final testing in the Dialogflow console

During the building, training, testing, and debugging phases of our GROCERYbot project, we used the Dialogflow console to test our bot. Following are two examples that show some the final testing we did before we published the bot to the web.

Publishing to the web

For our final development activities, we wanted to see how GROCERYbot would actually look on the web. To do that, we clicked the Integrations link in the Dialogflow console, enabled Web Demo for GROCERYbot, and clicked its icon.

Note that there are many more integrations available than just the Dialogflow Web Demo (for example, Slack and Twitter). There are even more that are not visible in this image.

The Web Demo information page that appears provides you with linking information for your chatbot. Clicking the link takes you to the web version of your bot.

GROCERYbot on the web

Below is our GROCERYbot on the web. During this stage of the project we went back and forth between the console and the web version. Additional changes that we made in the console were automatically reflected on the web.

Note that some of the debugging clues we added are still appearing in the web bot shown below. If we wanted to publish this bot publicly, we would have to go back and remove that information.

What’s next?

In our last post in this series (#8), we share the lessons we learned from our grocery shopping project, and list several possible follow-on projects.