The community members discuss the limitations of Typebot, a chatbot platform. One community member shares their experience building complex chatbot flows that integrate with various systems, but notes the importance of considering the potential scale and maintaining each component. They suggest isolating components into separate Typebots and using Typebot's "jump" feature to navigate between them. Another challenge mentioned is keeping users engaged with large, complex flows, and the community member recommends streamlining the flow to include only essential elements. Another community member adds that if the flow fails due to its complexity, the user must restart from the beginning.
In my experience, the only limitations you'll encounter won't be with Typebot itself. I've built complex flows where users could simulate loan applications directly in the chat, integrating with bank APIs, validators, CRMs, and more.
The key is to consider the potential scale of your flow and how to maintain each system involved. One solution I've found is to isolate each component into separate Typebots with their own logic, using Typebot (jump) to navigate between them.
Another challenge is user engagement – will they stay engaged with a massive flow? Consumers often have negative experiences when seeking support, facing long wait times and repetitive information. Aim to streamline your flow and only include what's essential.
One other limitation I’ve discovered is that, if the flow for some reasons fails (for example because it’s engineer who made it, lost it’s mind in complexity) the user must restart from the scratch.
