Type bot Limitations and Best Practice
I wonder what limitations of typebot is. How complex and big can one typebot?
x amount of Groups? y amount of modules? z amount of connections in between?
2 Replies
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.
Good points there
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.