I have been working on azure chat bot using the bot framework SDK v4 and I have ran into an issue. My bot needs to initiate a conversation first. I have seen some examples with proactive bot but that requires us to save the user credentials as a cookie. What I need is a chat bot that sends the first message to user via SMS to initiate the conversation. The bots needs to be able to set the recipient phone number dynamically. I have looked at integrating the Twillio channel to my bot, but the problem is that the user has to initiate the conversation to the Twillio phone number which then forwards the text to Azure chat bot. I was wondering if there is anything out there which will allow the chat bot to initiate the conversation first via SMS and the phone number of the recipient should be set dynamically. Is there anything out there currently on Microsoft stack? Our company has been a long partner with Microsoft so I would like to have the chat bot using the Microsoft Azure Bot Service. Can you please guide me or forward some documentation? Any help would be appreciated.
Related
I am working on creating a bot in Microsoft PowerApps using (Azure QnaMaker, Microsoft Flow Services). Our aim is to integrate this bot in Microsoft Teams to help users in the team to get the answer for faqs. I would like to know how can we send an email of conversation once his conversation is completed with the chatbot.
I have created a bot by following the steps mentioned in the doc.I have authenticated user using oauth 2.0 (auth code grant) as mentioned in the doc and in reverse I got a access token. But when I send message to channel in the teams using (/teams/{id}/channels/{id}/messages) API the message was sent on behalf of me. But I want my bot as the sender of message. Here is the image of the message that I have sent using the above API. and is there any way to send direct message to user as a bot?
Instead of using the Graph, there's another approach using the Bot Framework itself, to send a message to a team channel, a group chat, or a 1-1 conversation. The code doesn't even need to live inside the bot itself, it just needs to leverage the bot framework under the covers (for example, I have several Azure Functions that pro-actively message users). This idea is called "Proactive messaging" and you can read more about it in the docs here.
You do need to get certain fields when the user first installs the bot though, or any time the bot receives a message. I've described that more at Programmatically sending a message to a bot in Microsoft Teams. You haven't said what language you're using, but there are examples for a bunch of them - I can send you links if you let me know what you're using.
I'm working on an integration between Microsoft Teams and Slack.
I'm building a Microsoft Teams application which is connected to a Microsoft Bot.
Additionally, I created a server for:
Listening to messages which were sent by users in Slack (via Slack webhooks)
Posting them in Microsoft Teams conversation as a user message to the bot (outgoing message)
I receive messages from Slack (which were sent by a Slack user) to my server and I wish to post them in Microsoft Teams as messages from the user to the bot and I'm not able to do so.
I'm able to send messages from Bot to user in Microsoft Teams app via Microsoft Bot's "botbuilder" Node.js SDK:
session.send(message);
How can I send the message on the other direction (from user to bot)?
You can't. See this question for more info, but the short version is:
The BotFramework has no direct way to do this.
Even the Teams Graph API doesn't currently support this. They're working on it, but don't have an ETA.
The closest thing to a workaround would be:
User writes message in Slack to Bot
Bot receives message and posts a proactive message in Teams, something like:
User #louis1600 said: "blah blah blah"
Resources:
Proactive Messages in Teams
#mention-ing users in Teams with a Bot
The many other Teams Bot related questions I've answered
I am feeling a little bit lost with Microsoft.
https://dev.skype.com/webcontrol
Skype is telling me that I need a Bot ID (also known as Microsoft App ID).
At the same website is a link labeled with Microsoft App ID pointing to
https://learn.microsoft.com/en-us/azure/bot-service/?view=azure-bot-service-4.0
Do I have to "Create a bot with the Azure Bot Service" so that I get a Microsoft App ID that works with Skype?
Or can I get a Microsoft App ID that is independent from Azure?
In order to have a bot that works with Skype, you need to have a bot channels registration. If you already have a bot hosted elsewhere and you would like to use the Bot Service to connect it to channels such as Skype, Twilio, Messenger etc., you will need to register your bot with the Bot Service. A Bot Channels Registration bot service allows you to use Bot Service functionality. A registration bot lets you connect your bot to channels. You cannot get a Microsoft App ID that is independent from Azure.The Microsoft AppID is the same as the Bot ID that skype wants for the webchat bubble.
Let's think of the following example:
1) I have a certain bot deployed on Azure
2) Bot can be talked via Facebook Messenger and via Skype
3) A certain user talks to the bot via Facebook Messenger and then he leaves.
4)A couple of minutes ago the same user resumes the conversation with the bot, but via Skype.
Is this possible? I assume Bot Framework doesn't have anything included for this, hence, that this isn't posible (as conversations are independent and state changes depending on the channel). Is there any way to identify a user (via some authentication method maybe), and then making this logic again?
Do any of you know any workaround for this?
Thanks in advance!
The Bot Framework Connector service is a component which provides a single API for your bot to communicate across multiple client services such as Skype, Email, Slack. Every bot and user has an account within each channel.
The channel account contains an identifier (id) and other informative bot non-structural data, like an optional name.
And there us unique conversation ID created for each conversation of each user for each channel. And you can customize your channel capabilities as described here.
Regards,
Jyo