Website Name Change
I have changed the name of this website from Mining Business Data to BotFlo. I am offering a 60% off discount on both my Dialogflow ES and Dialogflow CX courses till April 20th 2021 for people who can help me spread the word about my new website.
I offer a 90 minute strategy/consultation service for people who are building complex Dialogflow ES or CX bots and need specific help around designing the conversation flow.
Price of Strategy service: $299
Depending on where you are with your ES bot, there are three primary use cases for this service:
Before you have built your bot
You have questions about whether Dialogflow is the best choice for your complex or large chatbot project. This is the best reason to use this service, as Dialogflow is not the correct tool for all types of bots. Specifically, there are certain situations where you may need a lot of control over your bot’s behavior and Dialogflow may not be sufficient. In that case, something like RASA NLU (which isn’t really a low code tool) can be a better choice.
Building the bot
You would like an accelerated prototyping session where we build out the conversation flow of the bot.
This is very useful if you are looking to build a prototype very quickly and don’t mind using a low code database such as Airtable. While it will not be possible to build an entire bot inside a single prototyping call, you can make a lot of progress, plus you can avoid making costly mistakes which might otherwise waste your time/money/resources.
You have already built a bot
You are stuck with your Dialogflow bot development, and your bot is not accurate or robust enough to satisfy your requirements.
Before you consider this option, please take some time to go through this article (sometimes you may not need my help):
Dialogflow CX is still relatively new and may not be suitable for all bots. I recommend reading the following articles before getting in touch:
If you are still interested, then please note that CX requires a lot more programming effort at the moment simply because a lot of tooling which exists for ES hasn’t really been built out for CX yet. Unless you already have a programmer on your team this might not be a good choice.