Dialogflow CX

I got this question in a YouTube comment. Unfortunately, this viewer has it completely inverted. Consider these three things: Dialogflow CX has no free tier CX has a much steeper learning curve CX is still in Beta, meaning nearly no one (except perhaps those who have direct access to the Dialogflow CX dev team) is using it with any sort of confidence. In fact, here is a Twitter exchange I had with a CX developer advocate. It is a good idea to read it carefully one more time. Especially this response: So the more practical approach would be to begin building your bot in Dialogflow ES. If and when it becomes too complex for ES, you should consider moving it…

A reader recently asked me if Dialogflow CX supports the Dialogflow Messenger integration. Answer: It doesn’t. But more importantly, CX supports almost no integrations out of the box. I think it is important to understand why that might be the case. Unlike ES, there is no free tier in CX I wrote about this in my article comparing Dialogflow ES and CX, and while my initial pricing calculation was off by quite a bit (and was duly corrected by a commenter), the main point is that there is no free tier in CX as of this writing. This might not be obvious to people who are new to Dialogflow, but every 1-click integration in Dialogflow ES uses the Dialogflow API…

Last updated: 1 Oct 2020 If you didn’t know, the folks at Google recently introduced Dialogflow CX, which is meant for developing large or very complex agents. The older version of Dialogflow has been renamed to Dialogflow ES (short for Essentials), and is more suited to develop small and simple agents. You can also find a comparison chart on this page. What my peers think There was the usual hype and self-congratulatory tweets when CX was released, but I am more interested in the opinions of my peers. It didn’t take me long to confirm what I was already thinking. Here is a tweet from Allen Firstenberg, who has been working with Dialogflow for quite a while (and is one…