[TrueGeek]

I understand, it's hard. But from the opposite end it can be hard for users to trust so you have to make that easier on them by being more transparent.

I'd suggest finding a perfect use case - maybe it's not T-Mobile. Then record a happy path video showing it working perfectly.

Also - as a tip, a lot of these companies will use the same software. So, right now your bot didn't do well with T-Mobile at all because it didn't know how to response to multi-button prompts. But once you teach it how to do that it'll know how to response to any company that uses the same software (LivePerson). Almost always you don't have to 'press' the button, you can just respond with the text of the button.

[neal_]

Appreciate it! Yea that video is pretty bad from a marketing perspective. I was kinda just thinking technical proof of concept shows it reading and replying...

Buttons and other actions are a bit tough. Currently it extracts the inner html from the chat wrapper div and gets all the text from the chat. This is great for being universal for different providers but it does have trade offs. detecting new messages can be tough if the inner html changes alot without an actual reply being received.... And depending on how the messages are labeled it sometimes has no way of detecting who is who, it relies mainly just off context.... Lots to improve. Overall supporting providers is good approach get alot of different website compatibility for integrating a single provider. So long as the customizations dont break anything. Main thing is making everything universal for it work on any site. That's the main challenge supporting lots of sites while still providing good context and the information needed. Appreciate the advice! I may post again when i have some of this stuff dialed in

[xandrius]

Don't worry, just know that once you publish like you did, you're doing marketing and you only get a few shots at those before losing credibility.

Keep it up and share it widely once it's really epic!