Congratulations on completing power automate section and first four sections of the course database data base. Security. Power Apps, which included canvas models and portals, and Power Automate Now we are getting into very interesting topics. We’ll talk about “power virtual agents,” which are basically catboats powered by big data, artificial intelligence, and machine learning (AI and ML). So let’s get started. Thank.
2. Overview & Topics
This lecture will introduce us to powerful virtual agents or bots, and we’ll talk about topics that are at the core of any bot we create. So let’s look at the overview. So you can create bots from your Power Apps UI. You have here catboats where you can create a list but you have a different URL power VA for bots itself.
So you have a complete UI for the bot. So here, if you click on this link, you can create a new bot and see your existing bots. These are your bot’s settings. So in general settings, you can import, export, or delete a bot. So here you can only create and see, and here you can delete. Then, when you have a bot, in case a customer is not satisfied with the conversation and wants to talk to a real person, this is the setting where you can transfer the conversation to an agent, and it has built-in integration with Dynamics 365 Omni Channel for customer service.
Then you have system fallback settings. So default behavior is it will ask the same question two times and then it will escalate to the live agent. But you can add a fallback topic where, if a bot is not able to understand, what is the fallback topic? This is the home screen, where you can see some videos and things like that, and this is the hide Rob Bot and test your bot screen, where you can look at your bot. Now let me hide the bot. So these are all the topics you will see. Topics are of two types. One is systemic and another is lesson topics. So these are lesson topics, and these are system topics. Then you have some predefined entities, like age, city, and color, which the bot will understand, and then you can create your own custom entity. Also, you have analytics, which are analytics on your bots.
So analytics are having you have four tabs summary, customer Satisfaction sessions and Billings and then you have your analytics on your topics also. So here you can go to a topic called “analytics.” Here you can publish your bot and then check it out on a demo website. Here you can manage your bot with details on which channels it is using, security skills, and AI capabilities. So we look at the settings. This is used to customize and delete a bot. Now bot is basically an AI which simulates human conversation through chat interface and bot listens to keywords and phrases and then based on those keywords and phrases what customers typing in it will answer back. So the bot will continue to check if customer questions have been answered and then refine its selection of topics to solve customers’ problems.
So it will switch between topics based on what the customer is asking, and if you go back here and look at your report, you have this but for tracking between topics. So if you enable it, what will happen is that it will show you if it is switching from one topic to another. This is your bot interface, as we saw; this is where you can see all the bots. Here you can do settings like Delete. This is your home page list of topics. list of entities like city zip code analytics on your bot, you can publish it and see it on the demo website, you can manage the skills and other security settings, you can hide and show your bot, and here you can test your bot. So bot panel on top right you create and open existing bots across your environment settings again top right provides access to different power virtual agent settings such as fallback topics transfer to agent settings home on left hand side top takes you the main page.
On this page you can find tools to assist with creating public and monitoring performance of your bot Learning content and training videos can also be accessed, and then you have topics, which are used to access all user and system topics available for the bot. Entities provides access to all pre-built and custom entities that are available, so you have quite a few rebuilt entities and you can build your own custom entity. Then, analytics provides details that are related to the performance and usage of bots, and then we saw that we have analytics on bots as well as topics. Publish provides tools to publish your bot and deploy different channels and assists in management items such as which channel board is deployed, authentication, and skill management. Test and hide your board wheel. You can engage your bot in real-time, and the Test Board Panel lets you test your buttocks to ensure that they are performing as expected. So let us try out.
So what I have done is I have come here and created a new board. This is my test board, and let’s check it out. So if I say five, it will process this phrase and reply to me. So this is the reply, and this is the topic. So it has picked up the trigger phrase from here and shown me this message and these three messages. So let me say that I want to talk about order. It is a greeting topic. So if I click order, it goes to some other topic that is configured about orders. And he says, “To which state are you shipping?” So let me say Washington. If I say Washington because I have this pick configured for Washington, it will take me to Washington, and it is asking me, “What do you want?” So let me say I want a laptop computer now.
It is on lesson three as of now. And it takes me to my laptop computer. So it has done. It has added laptop computer to my cart and says if it is if it answers my questions. It has taken me to end of conversation topic and I say yes. When I say yes, it takes me to a survey, so it takes me to the “confirmed success” topic. So let me mark it as 4, and it is asking if I can do something else, so I say no, and my conversation ends here. So it is going to be a goodbye topic. All these topics are available when I click on this. So here we have created a test board. When you create a test board, it will ask for language and environment. And then we have run the test bot without doing any coding or configuration, using the topics that are available by default in the default installation. And we have seen how we are converting with the bot and how, based on the inputs we are typing in, it is using different topics available for use now.
Topics consist of two key elements: trigger phases and conversational nodes. So if I go to a topic, let me hide the boat so I am more focused; if I go to a non-topic that has a trigger phase, let me go to both. So each topic has trigger phrases and a message it will respond. So trigger phases are the phrases, keywords, and questions that are entered by users and relate to a specific issue, and conversation notes are how the bot should respond. So a board can have up to 1000 topics. We have a single digit number of topics by default, and each created bot will include several predefined topics to help you get started. So we have two types of topics: lessons and systems. So these are all lesson topics, and below them you see a different icon. These are all systemic topics. So system topics are always on and lesson topics youkan switch them on and off based on your preference. So lesson topics are procreative user topics that can help you understand simple and complex ways of using nodes to create bots. Conversation and system topics are prepopulated to represent common use cases that can occur during a bot conversation.
So these are four lesson topics. Topic one goes through the conversation and creates a conditional branch that’s displaced. Torah. So what it is doing is letting us go to topic one, and I go to Think Canvas, so these are triggered phrases, and it is talking about store hours. so it says okay I’m happy to help with store hours and it gives me this message and ends the conversation. So it has two stores, and it gives me that information. Let us go to lesson two and I go to Othrinkanverse so it talks me about store location near mesa it says okay I can find store location near you and it gives me three options.
So we have three stores; it gives me three options: “These are the three stores; which location do you want?” and stores this information in a variable based on my answer. If it is equal to these three, then it gives me a corresponding location and uses a variable here, and then it ends the conversation. So similarly lesson three we can go to earth’s adverse directly from the topic, what it does is it is asking to buy the items so it says which item, which state you will be shipping and then we have options for states. So if it is one of these states then there is nothing, but otherwise in all other conditions, it says there is a shipping charge and is it acceptable? If it is okay, then it asks me, “What do you want to buy?” These are my options for buying stuff. And then, based on what I am buying, it will show me a message, it will tell me that I have added it to the cart, and it will end the conversation.
And the last lesson topic says, “Which is the best product for me?” So it asks me which type of user I am, and based on that, it shows me a different message. Then it asks whether we want it, and based on the answer, it shows me a corresponding message, ending the conversation. So we looked at four lessons provided by default. So lesson one goes through the creation of a simple topic with one conditional branch that displays store hours. Lesson two is a topic with a variable that shows me stored locations based on preferred customers and preferred store locations, and it uses this variable. Then lesson three is about conditions, variables, and prebuilt built entity. So it uses a US state entity where it is asking me which state Washington is, etc.
And based on that, it is calculating the shipping charge. So it goes through the creation of a topic that includes an unconditional branch, a variable, and an entity, and then based on the state, it is telling me if the postage will be charged or not. And in lesson four, we have used a custom entity. It goes to the creation topic with a conditional branch, a variable, and a custom entity. We have looked at these four lessons, which are prebuilt in chats; these are all system topics, and you will see we have a number of trigger phases or not-trigger phases for each of the topics, so we have topics like greetings, escalating, and the conversation being confirmed as successful. Failure, goodbye, Start over, and thank you. So each topic that you define should include some trigger phases. Trigger phases are examples of text, such as questions or references, that each bot will respond to in this dialogue, so they contain trigger phases.
But you see here, we don’t have a trigger phase because it will just show a message and finish the conversion. So when converting conversation will consist of two nodes trigger phase that will trigger the topic and initial message that will be provided to the user. Conversation nodes help define the path that the conversation will take, and conversation nodes can display messages, ask questions like “say it” or “give a zip code,” and then run some actions.
3. Suggest Topics
So we had one topic left from the previous lecture, which is suggesting topics. So we’ll talk about it. If you go to Topics, you have the option of suggesting topics here. Here. What you can do is you can put up any URL and add it. This way, you can add multiple URLs and start. So what this will do is look at this web page and import information from the web page under Suggested Topics. So you don’t have to feed in those values manually. Once you have all these values, you can select any topic. And if you say “add two topics,” it will move this from suggested to existing. So this 14 will increase, 109 will decrease. We’ll see it in just a moment. So it has been added, and it has become 15 908. What you can also do is select something and delete it, so it will be deleted. So that way, you can manage your topics automatically from a webpage. So that’s all we wanted to learn from the last lecture. Thank you.
4. Create Bot
In this lecture, we’ll create a sample robot. So this is how we create our first bot, test it, and enable tracking between topics. So this is what we have already done. What we’ll do is we’ll make a copy of topic and modify its we’ll make a copy of lesson to Topic and name it as Get Store Location. Then we’ll add a location for Bellevue, add a message for its address, and link it to end the conversation. Then we’ll enable our new topic and test it. Then we’ll publish our bot and test it on a demo page. And then we will remove the topic and test it again. See if it is reverting back to the old functionality. So this is our bot. So let’s look at the existing topics. So this is lesson two. What we’ll do is we’ll make a copy of this topic then we’ll name it as Get Store Location.
So this is a copy. We’ll edit it and name it “Get Store Location,” save it, and then we’ll add a location value. So for that, we have to go to the authoring canvas. Here are these three locations. Let us add a location once we do that. What it does is automatically add a condition for value, and we can add a message for the store location. Then we can end the conversation with the survey. So this is done. Now we’ll have to go back to topics and enable it. So this is our new topic. We’ll enable it; it is enabled, and we’ll turn off this existing topic. Now we are all set to test our bot. So let us say track between topics and let us start, let us say Store Location and see here it has given me an option of Bellevue which we have just added and we get it now we can also publish it. Once we publish it, we can see that it has given me an error. Once we publish it, we can go to a demo website and look at our bot. This is a Devon website, and this is our test port. So we can test it again here. So it has given us the option of mailing here. So now what we can do is go back to Topics, hide the bot, disable our new topic, and then we’ll label the old topic again.
So once we do that, we can again test our bot. Then, for location, it is still giving us the option. Maybe it will take some time to update. So let me try again. Let me take it out. Sometimes it takes some time. So we have done this. This is a question. We added an option here. So different node types can be inserted based on what you want to display or capture, and options are represented as buttons in the chat conversation window. This is the condition. We added a condition, and for the condition we added a message, and we have already seen this track between topics. So that’s about it about creating our onboard. Thank you. Okay, so what had happened is that this was not enabled and disabled properly. That is why it was giving an error. It was still showing the option of a value. So I have now disabled this topic and enabled the old one again. And I’m running it ask for store location and it is devoted back to the old three options. All right then. See you in the next lecture. Thank you.
5. Integrate Flows
In this lecture, we’ll create a power virtual agent and integrate it with power flow. So let’s get back to it. We’ll create a new topic, we’ll name it as get feather and add a few trigger phrases like the what’s the weather whether can you tell me the weather? I would like to now let’s go tithe authoring converse visa lot some error came. So after the trigger phases we’ll add a message, we’ll hide the bot add a message I can help you with that I just need some additional information right when we ask a question we’ll add a note. Ask a question and we’ll say which city do you leave it and it says we’re using prebuilt entity called city and we’ll rename the variable as city. Then we’ll add another question and ask him, “What is yours?” Again we’ll use entity called zip code and make the variable name as. Now, after this, what we’ll do is create a flow to get actual weather information. So call an action, and here we create a flow. It will take us to our automated flows, and here we’ll use MSN to get actual weather information. So for input we’ll get text and we’ll say city and then one more text code then we’ll add an action. And here we use MSN weather to get the forecast for today.
And here we’ll give him the location. Location will be city and zip code, and then for return values, we’ll say a summary, and that will be a summary. Then we’ll say one more text for location and select location then a number for rain cancer. So now we are done with our flow. We’ll save the flow and then go back to virtual agents. So we got these two parameters from the flow for citing, and we are giving these parameters back. We’ll go back so we have come back here, and then we’ll add a node, and when we call an action, we’ll see that we have our created flow here. So we are selecting this. So city is going as city and zip code is going as chip code. Then we are returning these three values and let us show a message. We will say today’s forecast for city and location is a day summary, and in terms of range, it is a percentage. We are now done with our bot; we are saving it, and then we should be able to test it. Let us say hi here; ask for weather, and it’s asking for city. Let us give it New York not asking for zip code. Let me enter the zip code, and I’ll get back my forecast. So it is mostly cloudy; the high is 60; and the suffering is 100%.
So we used “call in action” to integrate flows with our work bot. This is the flow trigger phase initial message. gas two questions pass these two parameters to the flow, which used MSN to return these three parameters, and we showed a final message. This is a flow. It got city and zip code as parameters called MSN to get the up today’s, forecast and return these three values. So power virtual agents include following features to make it even more powerful. We can initiate power automation flows. We can pass conversations to live agents, and we can pass them to Omni channel Dynamics 365. So here we have seen transfer agents, and here we have Dynamics 365. Then we have automatic topic creation, which extracts content from existing support pages such as FAQs and converts it into bot topics. So this we saw in topics. If you go to topics, we have this suggestion of topics, which will automatically get it from a web page. And then we’ll also power automate provides following trigger and action power virtual agents. It is passing the variables to power flows and returning values to power virtual agents. It’s getting back the values from flows to power virtual agents. So in this lecture, we initiated flows from our dot. Thank you.
6. Node Types
In this lecture, we’ll talk about node types and some other miscellaneous topics. So first are the node types. There are six types of node types here, so let us look at them. If you go to the topic and click here, you can add a note type. So first, let’s ask a question. So if you ask a question, maybe, what is the city? And then you have multiple options here, so let me choose city, and it saves the city as a variable. So I can edit this variable and name it “city.” Once this variable is there, it has two types: topic or bot. So if it is topic scope, then this variable is limited to this topic. If it is bot scope then this variable can be accessed during a conversation by other topics also.
So name is city, type is city. If you say go to source, then what it will do is go to the node where the variable is defined first, and if the variable is used in multiple places, all those places will be listed here. So we talked about question nodes and variables. Let us choose another node. We’ll say “add a condition.” So here’s the added condition. So if the variable says city is equal to Washington, then do some activity; otherwise, it goes here. If it is Washington, it goes to its branch; otherwise, it goes to this branch.
So that was a condition type node, and if I say, “Call an action,” the action will initiate a Microsoft Flow, so it is loading and it will initiate flow. So this flow we have created, it talks to MSN. weather, and we can create a new flow here. I can also say, “Show a message,” and I can say, “You have selected Washington in this message.” I can also use my variables. So instead of saying Washington, I can say the city here. And then I need not say Washington. It uses variable to display the information and next node type isI can say I want to go to other topics it shows me in the list of all the topics and I can go to some other topic say I go to simple topic and then this node finishes here so I can also say and the conversation and the conversation I have two options. and with the survey or transfer to Agent, let’s say and with a survey shows me survey with five stars or if I say transfer to agent it shows me a message before that it will show to the user before it goes to the agent. So these are all the node types here: ask a question, which has three fields. First is ask a question is a question test.
This is identity, which defines an answer such as multiple choice options or a number string, and this is how the response is saved as a variable, then we add a condition. So for a variable, we can add a condition, and branching conditions are automatically created based on options defined. And based on these conditions, you can flow further. So this variable is equal to Seattle. Then call an action that calls a Microsoft Flow. It’s called Microsoft Power Automate Flow. For example, we did a flowto call MSN Weather Connector.
Then show a message, show a message, and here we can use variables. Also, our message displays a message to the user and includes basic formatting and numbering. We can go to another topic, end the conversation using a survey, or transfer to an agent. So that was all about node types. Then we have some entities—some predefined entities in bots. So these are all the entities. So these predefined entities can be used like age, Boolean, city, color, continent, country, date and time, duration, email, event, language, money, ordinal number, ordinal organization, percentage, person name, phone number, point of interest, speed, state status, temperature, and URL usage. type, weight, chip, and code So these are commonly used entities that we need, and they have been predefined for us. We can always go and add a custom entityalso, so we can add a custom entity.
We can name it, say, PCtypes, and we can enter L. Now we can add synonyms. So maybe I can enter if somebody types “all” by mistake; it will take it as Dell. And here, smart matching is on. So it uses AI to correct any spelling mistakes automatically. So I can save this, and it will show me the list of entities. So while it is saving, we did this and defined a custom entity. We looked at synonyms and smart matching. So what doesn’t have to find the exact match.When smart matching is turned on, the board will automatically autocorrect misspellings. For example, softball will be matched tobaseball and synonym often is similar tosmart matching, only differences in synonyms.
We actually provide the alternate word. So let’s see if our table is created now. So it is being created; we’ll close it, and we have it here in PC type. And you see, PC type is a closed list, while all others are pre-built, and it has my name here now with the concept of slot filling. So if the board is asking which equipment you’re looking for and I say tracking, it will automatically match tracking to hiking if I say hiking. So because tracking was defined as a synonym, slot filling replaces hiking within the variable. Suppose customers are tracked in the first message itself. Then the question asked for product type is “skip.” The variable is automatically populated with the category, so it automatically does not ask the question.
Even so, that is proactive slot filling. Then we talked about this. These are variables. So topic variables are used within topics. Bot variables are used across topics, but bot variables cannot be carried across customer chat sessions. So if the two customers are talking, then their variables will be defined separately, and you should have a bot variable that you should be using across all topics. In case you have a duplicate Bot variable it will give you an error then go to source goes tithe not where variable was initially created and used. By displace all the topics where variables are used, you have fallback topics. So the default variable is that if it cannot determine the user’s intent, it will ask the same question again.
And in case it doesn’t get an answer, it will escalate to “live.” Agent, if you define a fallback topic and what will happen, you can add a topic here, and if the board cannot determine the user’s intent, it will go to the fallback topic for prompting the customer. Then we have these four types of errors. node entire node is errors errors and highlighted in red field some required data is missing expression expression may be invalid and variable deletion. Like we told you, we deleted a variable, and other places where it is used are highlighted in red. So the variable has become orphaned and needs to be replaced or removed. So we talked about some pretty useful topics here, like node types and others. See you in the next lecture. Thank you.
7. Bot & Topic Analytics
We’ll talk about analytics in this session. There are two types of analytics. One is bot analytics, and then you have topic analytics. If you go to the analytics tab here, you have four tabs: summary, customer satisfaction, sessions, and billing. In the Summary tab, you see total sessions, engagement rate, how much his customers engaged, how many of his queries were resolved, how many were escalated, how many were abandoned in between, and what is the C set for this bot? Then you have engagement and session outcomes. So by date, how many are engaged and not engaged? It is basically a detail of this particular chart. And then you have the session outcomes of resolved, escalated, and abandoned. So Resolved is this one, escalated is this one, and Abandoned is this one.
And this is for resolved, escalated and abandoned. Now, for Resolved, Escalated, and Abandoned, you can also see the topics that are having the most impact. So far, the weather is having a -2% impact on resolution. Lesson three has a minus one impact on escalation, and lesson three has a minus four impact on abandonment. The next one is customer satisfaction. So these two topics are having an impact on customer satisfaction. So for this session, how many sessions; resolution rate; abandonment rate; escalation rate; and CSAT impact? Now, you can go to this topic’s analytics using this link. Also here you see CSAT score over time. This is the average CSAT, and then this is the CSAT service completed and incomplete. If you go to sessions, you can download an Excel sheet from here that’s not showing anything. And if you go to billing, each session is marked as a billing session. So a total of two billing sessions changes100% and this is billing sessions over time. Now those are all bought analytics, but you have topic analytics also.
So if you click Go to Topics, you have the option to go to Analytics. and if you click that, you will come to the screen. Now. This is topical analytics. So for this topic, total sessions, average CSAT resolution, escalation, and abandonment rates, this is the impact of this topic on the total. So, the impact of this topic on CSAT resolution, escalation, and abandonment, and then volume by day, So, this is the entire analytics report. So we have four reports: summary satisfaction sessions, billing, and training. Summary Type provides detailed overview information such as the number of sessions, engagement rate, resolution rate, escalation rate, and abandonment rate. You will notice that these are only four or five KPIs that are getting displayed in all the tabs. Customer Satisfaction Reports have identified which topics are having the most impact. It will identify the topics that are having an impact on The Customer Satisfaction Sessions tab gives you flexibility to download raw data, so it will download it as an Excel sheet, and we can do our analysis here. It has a link to complete transcript also.
And the Billing tab shows billing interactions between customer and bot. Now, this is the screenshot of the Summary tab. You have summary charts and then engagement over time. It shows you engaged users and engaged sessions, then session outcomes, which can be resolved, escalated, or abandoned. And then you have topics topics which are having impact on resolution, topics having impact onEscalation and topics having impact on abandonment. This is a customer satisfaction report. So Customer Satisfaction based provides detailed view of customer satisfaction survey data. So. Customer satisfaction, driver charts Basically, this is the one where it identifies topics having an impact on customer satisfaction. So it uses AI to group related support topic cases at topics and then impact of each topic. Then you accumulate scores over time. So it has average CSET score scores over time.
So these are scores over time. Then you have the average CSET score and the CSET survey response rate. So this is the response rate, and this is the average C-set score. And these are your sessions tab you can download and CSV file it will give you a session ID. When the session was started, what was the initial user message, what was the last topic discussed, and what is the whole chat transcript? It is like user says and then what he has said and then Bot says then what he has said then this is the session outcome resolved, abandoned, escalated and engaged. And this is the topic idea where you can look at the topic in detail. So the session ID is a unique identifier for each session. The start date and time is when the session started, and the initial user message is the first message. Topic name is the last author topic and chart transplanted is by User says bot says and conversations are separated by Simon Collins and Bot Says does not include options presented to the user. An outcome can be resolved, escalated, abandoned, or unengaged. Topic ID is a unique identifier for the topic. Now this is the billing tab: total sales, total percentage, impact, and billing by this. Then this is the screenshot for topic analytics.
So this is topic volume by date, and these are for that topic’s total sessions, CSAT resolution, escalation, and abandoned rate, as well as the impact of that topic on CSAT resolution, escalation, and abandonment. You will notice that these KPIs are being repeated. So this is the topic, and this is the impact, so the topic summary chart shows the topic’s performance impact. The summary chart shows the impact of the topic on KPI, and then you have topic volume by day, which shows the number of sessions for that particular topic. So we briefly covered analytics reports in this session, which talks about bot and topic analytics. Thank you.
8. Security & Sharing
We’ll talk about security and sharing options in this lesson, so you have to assign a bot author security role to the environment, and by default, each bot comes with twelve topics, of which only four can be turned off. The remaining topics cannot be turned off or deleted. So if you go to topics here you see that these topics cannot be turned off or deleted and you have these topics some came and some we created during our sessions which can be turned off or deleted also.
So you have a delete option here, but if you don’t have this delete option here and currently you cannot export or import topics, the only way to export topics to another environment is to use solutions and migrate the entire chatbot, which will include the topics automatically. Now sessions can end for following three reasons. One is that the user ends the chat session and the board doesn’t receive any new messages for more than 30 minutes, and if the session goes on for more than 60 minutes, then it starts a new session. And if the session has more than 100 tonnes, one tonne is basically when the bot is saying something and the customer is saying something. After 100 tons, the new session starts. So the three security rules are: bought author, bought bot contributor, and bought transcript viewer.
So once you share your bot, if you go to the home page, you have the share option on the top, and here you can add an email to whom to share it too. So once you share the bot, a person can view, edit, configure, share, and publish the bot but cannot delete it. It will also give environment maker role to that particular person because user needs the security role to work with bots in power virtual agents then you can also enable bot transcript. The user will be able to view transcripts of chat sessions, so he will be able to see actual chat sessions that have happened. Coming to security, we have access and authentication options that control who can access, and we have three types here: one is all bot managers. This selection will allow all users who have the “manager” role to chat with the bot, and then you can have everyone in the organisation chat, so everyone in the organisation will be able to chat and those outside the organisation will get an error message. Okay, the three options for authentication are no authentication any user who has linked to the board can chat with only four teams means the board will work on team channels and therefore user has to be signed in to access the bot and third is manual.
So if the authentication setting is configured to manual, the service provider can be either your ad or your active directory view, and if authentication-private provider is set to generic author, the only option is your ad. So when you create a power virtual agent bot, it is immediately available on the demo website and in custom channels to anyone who knows the bot ID. And these channels are available by default. So we talked about security and sharing in this lecture. Thank you.
9. Channels – Teams
In this lecture we’ll talk about integrate with Teams and other channels. So you can deploy your chatbot to Teams, your own website, Facebook, and many other channels where a user can interact with your bot. So first, we’ll talk about adding your bot to the Teams channel. So what you’ll have to do is if you go to manage these are the various channels you can deploy your bot to. You can deploy to Teams, you can run bourbon from Teams, your demo website, custom website, your own website, mobile app, Facebook, Skype, Cortana, Slack and there are many other options for that. What you will have to do is go to Teams and enable it, and then you have to go to Teams and install App Studio. In App Studio, you have to create a new app and configure your test bot here. Look at the steps. So this is related to the objective of adding catboats to Teams and other channels. So first we’ll look at Teams.
For Teams, you first publish your bot, then go to Channel Steams, click on Teams, and you have to turn on Teams. Once you turn on Teams, it will give you the screen for your bot’s details. Then you will have to get your bot ID.For bot ID, what you have to do is enter channels, click on Mobile Channel, and you will get your bot ID here. Now this information is used to install your bot on a mobile device, and this is the code you need to embed to enable your Chabot on a mobile device. Then you go to Teams and look for App Studio. Once you look for App Studio, you will get this, and you can add it to your Teams channel.
And once you do that, it will show you the screen, and you have to click on “Create a new app.” So once you click on “Create a New App,” it will give you the screen, and you have to give your short name and app ID. Once you do that, then you have to click on Bots and then click on Set up an Existing Bot, give an ID here, and select Scope as Personal. And after you have done that, you click on “Test and Distribute” and install your bot on Teams. Once you install it, you will be able to run your bot from Teams. So these are the screenshots. Here you go to App Studio, create a new app, go to App Details, and give it a name and App ID. Then go to “Boards.” Click on Setup, then give a bot ID here. click on existing bot bot ID here and scope as persons. Then go to Test and Distribute and install your bot. So that’s about it. For installing your bot on Teams channel, we have looked at how to install it on your mobile
Then you have an option for Custom website in your channels itself. So if you click on that you’ll get a code which you can embed in your own website page. Then you can look at installing your bot on a demo website. It’s automatically configured for demo websites, and you can change the welcome message and conversation starters. You can also share this URL with anybody, and he or she will be able to go to this URL and test your bot on a demo website. So these are the various channels available, and we have looked at teams, a demo website, a custom website, and a mobile app in detail. And you can look at all these options by clicking on them. Thank you.