Ok, so you want to be a lead bot - to generate leads. Quiro bot (or however you spell it) is a great example of something that would work for this purpose with so much more functionality. I may go back to that and see what can be done. However, for this product. The way they have designed the pop up messages and allows it to return another message if no action is taken, the look of the avatar etc is all good.

I'm not against the premise but at this point you need to offer more customization.

1. They say they integrate with another Brazil chat called Jivochat or something - I cannot get this integration to work and I am by far no layman to technology.

2. They have no API public and available - not even a JS limited version that would allow you to take control easier so that at the end of a chat, you could initiate a new service that does live chat. Right now their only option is a redirect, which will redirect them to another page and doesn't fit well with the needs.

3. The other options for blocks are very limited. Again, they will fall back and say this is not meant for chat, AI etc, its just a lead form type bot. But the facts are that there should be ability / documentation that allows us to easily remove this bot at the end of a flow, and then initiate a new bot from another service. Or whatever we want to do.

4. Options should allow this as well. Look you are living in 2024, if you are trying to put up gates, you will lose because another will allow the ecosystem to live. Then when you put out whatever GPT you want - people will be willing to try it and stick with it. However, by limiting the type of blocks so there is no custom html, there is no way to change a direction makes this really pointless.

5. Look, Queriobot is a great example to learn from & give the ability for us to do things without having to go full customization mode. https://academy.quriobot.com/how-to-build-an-advanced-bot/using-both-quriobot-and-tawk-to/ - great way to easily switch over to a live chat or something while still using leadster. They have tutorials for many integrations. Now, this is more technical, but thats why you should have some sort of JS SDK. Keeping this closed off - makes 0 sense because you are taking up a large amount of real estate (the corners) & there is going to be time when we want to trigger something once a lead is caught. Now I know we could write something where after a flow is converted, the bot I believe disappears, and then can write a function to launch another service if the bot has disappeared - but why not just make it much more simple.

So overall, if all you want is to collect some information from your potential leads - its not a bad app. But in 2024, you need much more than this & you need ecosystems to at least have some developer friendly sdk's or API's to help connect the dots. Interactivity is the name of the game. I'm unsure about keeping it or not - we'll see if there is any sorts of developer documentation.