In regards of architecture… Our idea has two perspectives. The operator that needs to register with some information about his business and the person that needs support. Should we have 2 agents for this? Building an API so the agents can share information is solvable for us. I would simply name the agents similar and clearly.
1 Like
I’d have to understand your use case a bit more to say for sure, but if you want to submit two agents for one project and make them communicate somehow you can do that!
Another idea that would make it work very seamlessly with the Live Agent Studio is if you somehow included functionality for the agent to recognize which “perspective” the user is interacting with. Either the operator or the support side.
That way you can have just one agent but it can act as both and use a database as the knowledge store to connect the two.