Allow Multiple AI Bots in One Account
planned
S
Steve Querio
Allow us to have multiple AI Conversational bots in one account that are trained for different functions. Example: One bot would be for scheduling appointments, one bot would be for support, one bot would be for completing forms. Another example would be if one subaccount had multiple websites that each required its own conversational AI.
Log In
G
Gowtham Jakka
Puru Bansal & Sales & Marketing: Conv AI also needs to be made available per channel i.e. be able to select which live chat widget in case there are multiple Live Chat widgets or mobile numbers in case there are multiple LC phone numbers.
I
Iver Aune
Guys, what do you think about these bot enhancements? https://ideas.gohighlevel.com/conversation-ai/p/booking-bot-including-workflow-action-enhancements
K
Kunal Sarhadi
Absolutely necessary. The current version can only be trained for a specific product. If you are selling in multiple cities the bot fails and keeps giving the same price etc. for both cities.
A
Anthony Mitchell
Has anyone figured out how to trigger the bot in a workflow? I want to set the bot to reply to specific contacts but not every SMS that the subaccount receives. IE: Form submission Trigger, SMS Sent to start the conversation, Contact replied to workflow, Bot is triggered?
Seems simple enough but haven't been able to figure it out?
G
George Bronson
Yes, and each separately trained bot should be activated on whatever channels we want (Live Chat, SMS, etc). And would likely be Auto Pilot of course. However, we still need to be able to set some channels to Suggestive or Off. It's almost like we need to define which bot as criteria in workflow Trigger or other settings. We have to be able to control which workflows respond to which bots.
J
Jonathan Killam
I can not wait for this feature release!!!
T
Tammy Peix
Absolutely necessary since it makes it complex to train a bot to solve all the possible problems a lead/client might have. Would need many more words available for a very detailed prompt.
D
Daniel Marr
Any progress on this? Absolutely critical if we want to build robust solutions. A generalised catch all bot doesn't cut it. These should be created as single purpose agents that can be assigned knowledge bases and tool such as calendar access, trigger workflow, human handoff etc...
Puru Bansal
J
Johnny Scott
wish I could build out different client bots inside one account in the workflows. tried this and it went crazy so had to go back to one bot with one setup for sms seller leads lol. this would be amazing
Load More
→