tompaana/bot-message-routing

Message routing component for chatbots built with Microsoft Bot Framework C# SDK.

bot-message-routing's Issues

"Agent" using Facebook Messenger fails to send messages to "client"

First off, this package is absolutely wonderful. Great job! It works great if I use the emulator or sms but I've found a scenario where there seems to be a bug.

If I use Facebook messenger to issue the "command watch", I get the expected, "This channel/conversation is now where the requests are aggregated". Then if I use my cell phone, via sms, to request a "human" the process works great, asking to accept the conversation request. Then, after accepting, if I send messages from my cell phone (sms) those messages arrive just fine in Messenger but if I try to respond to the "client" from Messenger I receive:

"You said: hello
Type "command options" to see all command options.
Type "human" to initiate conversation with human agent."

Indicating the conversation is not connected.

Links not working

Hi, I am looking for a simple sample for BOT to Human Handoff (e.g. Agent via Skype). If I try to open following links I get just this Error: Error establishing a database connection
http://tomipaananen.azurewebsites.net/?p=1851
http://tomipaananen.azurewebsites.net/?p=2231
May be you can fix it?
Kind regards Jan

SendMessageAsync should allow use of custom bot credentials

Hi there, we're using custom bot id keys etc. (don't know if that matters). When await _messageRouterManager.SendMessageToPartyByBotAsync(
conversationClientParty, messageToConversationClient); is called it returns fine but it doesn't respond in the channel. (using web chat) I hooked up to the response of it and that is always null when it returns.

How do I get this to respond back to the channel with a please wait?

Also similarly I'm not getting notified on the watching endpoint that there is a request waiting. I'm assuming this is all related?

Optimize DB calls

The database queries should be optimized. We should optimize the number of calls required to execute an operation.

Rename `MessageRouterManager` to `MessageRouter`

Clean AzureTableStorageRoutingDataStore class and moved RoutingDataEntity to Azure folder in Models folder

Enable N:N connections

I can't connect to multiple customer at a time.
Can I do this for multiple users?

messageRouterResult = await messageRouterManager.ConnectAsync(
senderParty,
partyToAcceptOrReject,
createNewDirectConversation);

How to handle multiple messages to single agent scenrio

Hi @tompaana , This package is superb and great work.

Can we handle multiple messages to same agent at a time and agent can answers to them one by one(Scenario which I required is something how we chant Skype for business).

Thanks in Advance.

Thanks,
Satheesh K.

Create a class representing two parties and the timestamp for when the connection was established.

Send a user a message from outside of a dialog

I want to be able to send a user a message from outside of a dialog.
I built out a human handoff API endpoint (HandoffController) which takes in a json body. An agent from there own software built out integration with this API endpoint. Once I receive that message in the controller, i want to be able to send that message over to the user. The json body includes the user_id and the message.
Is there an implementation I can use so I can send that message to the user? I am outside a dialog so I can't use the context/activity to send the message.

How can I accomplish this?

To upgrade Microsoft.Bot.Builder to Version 4.3.2

I already made changes
tbuha@4aa03fc

Replace all uses of 'Party' to the bot framework entity 'ConversationReference'. Need to update code, comments and documentation.

Replace use of Party with 'ConversationReference' entity from Bot Framework and create a separate class with the properties:

• ConnectionRequestTime
• ConnectionEstablishedTime (time of the last event of a conversation)

Refactor AzureTableStorageRoutingDataStore class (simplify adding and removing methods)

Implement basic persistent storage for routing data

Implement IRoutingDataManager interface using Azure Table Storage services. No caching required.

The first class to implement is AzureTableStorageRoutingDataManager

Refactor LocalRoutingDataManager class to work with the new IRoutingDataStore interface

Get Agent watch status

Add a function to check if a watching Agent is available for the handover

MessageRouting fails for come channels in User Handoff scenario

Message routing fails when using the combination of Messenger and Skype.
Example:
Messenger : Customer Service Agent
Skype: Customer

• In Messenger use "command add aggregation" to aggregate all request.
• In Skype request for User Handoff.
• Conversation between Service Agent and Customer is established
• Customer sends message which is received by the Service Agent
• Service Agent sends message which is NOT received by the Customer

When testing the above scenario with Messanger to Bot Emulator or Skype to Bot Emulator it all works fine...

Let me know if you need more info :)

Write initial unit tests

For this it's enough to have E2E tests for MessageRoutingManager class.

Implement the IRoutingDataStore interface in the AzureTableStorageRoutingDataStore class

Create class that represents a connection request

Review documentation