You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have implemented the "tompaana" solution for bot-agent-handoff (1 to 1 conversation) in C#, but how can I establish a "1 to n" scenario (i.e. one agent handling multiple users after bot escalation)?
The text was updated successfully, but these errors were encountered:
You’d probably need to modify the Bot Message Routing code (https://github.com/tompaana/bot-message-routing) to support 1:many connections. You should ditch the NuGet package and add the project as such to your solution if you haven’t done so already. Note that that is just my quick guestimate - it could be that the router is fine and you need to something on the sample side.
I don’t doubt there is this limitation with respect to 1-to-N functionality and while I can't say out-of-the-bat where the blocker is, I believe it should be easy to overcome. I suggest you do some digging and when you find the solution, would be nice if you reported it back here to help others with the same need.
@tompaana, Thanks for your reply. Will you further provide any support in achieving 1
to n communication. Because I'm finding difficulties in customizing the
code.
I have implemented the "tompaana" solution for bot-agent-handoff (1 to 1 conversation) in C#, but how can I establish a "1 to n" scenario (i.e. one agent handling multiple users after bot escalation)?
The text was updated successfully, but these errors were encountered: