Botmock is by far the most powerful prototyping tool for conversation design I’ve used. Since the first time, when I tested the trial, I was astonished by it’s easy learning curve and collaboration features .With Botmock I can design better, faster, and more collaboratively. It has reduced the number of steps required for me to design complex flows and projects.

Maybe some UX features, like the projects' page UX, can be improved.

My experience with Botmock has been quite good so far. One of the biggest problems in the chatbot creation market is to connect conversational flows (created by content creators) to applications and allow access to flows programmatically - Botmock solves this problem and provides an application that is an awesome solution for both parties.

-Awesome tool to create conversational flows; -Flows accessible through API; -Easy to use - from content creators to technical team; -Easy to integrate with a high range of external apps; -User Friendly UI; -Great technical support;

- Sometimes the graphical interface crash and browser reset is needed (data is not lost); - More examples in the API documentation; - Questions Forum to increase Botmock community connection;

The graphical interface is nice Customer support is always quick and willing to help

Features like being able to import projects are lacking Things get pretty slow when projects grow

Wonderful!

As someone who never worked on chatbots before and researched a lot of dialogue flow tools, Botmock was the easiest to learn and use! I find Botmock accelerated our ability to capture intents and define dialogue flow and works for handing off requirements to developers as well as presenting to non technical business stakeholders. If I have question I can't find in Help docs or blogs, someone always responds via chat quickly

I don't like some of the new changes to dialogue flow space, I find it harder to add a label to connection points.

From initial drafting to IT implementation, Botmock is the primary tool for our conversational design projects. Its UX has greatly improved over the past year and once you get the hang of it is quite intuitive. While it still has some bugs and potential growth areas, it has a great support staff (shoutout to [SENSITIVE CONTENT HIDDEN]) who are happy to help and push out quick fixes to ease pain points when they do arise.

I love that I can use the app to create our initial build of projects and seamlessly transition into testing the projects — both as myself validating work and for user testing with people outside fo the working team. This builds efficiencies and I have also appreciated improvements to the UI like the improved zoom function and control over the connections between content blocks. This had previously been a weak point, but is now much easier and improves how easily I can show projects to team members who only seldom use Botmock.

We have encountered versioning issues when multiple team members are working at the same time. These can be extreme (hours of lost work) but more commonly are small inconsistencies that require one user to refresh the page. I think Google Docs serves as a best in class experience for this, and it's inconvenient to have to realize that we're in disagreement over things that are out of sync and there isn't any actual issue. The search functionality is also subpar as it seemingly only searches the titles of content blocks rather than the content within them. When I'm QAing and trying to replace all instances of a word (or something of the sort), this has a significant impact on how confident I can feel. A small thing, but I also download all projects as CSVs, and there are often far too many columns. Some are completely empty, others just seem to randomly spread out quickly reply button options, etc across different columns. I typically take a whole day to organize a final project's spreadsheet before delivery to the client.