The command menu provides a list of words or phrases you want your bot to always respond to. Remember, in this context, the bot is available to the entire team, not just the channel.Ĭhat tab: Opens the space to talk with your bot (applicable only to personal apps).Ĭustom tabs: Opens other content related to your app.Ībout tab: Displays basic information about your app.Ĭhat bubble: Bot conversations use the Teams messaging framework.Īdaptive Card: If your bot's responses include Adaptive Cards, the card takes up the full width of the chat bubble.Ĭommand menu: Displays your bot's standard commands (defined by you). Channel: People can interact with a bot in a channel.Group chat: People can interact with a bot in a group chat by the bot.It's the same experience as using a bot in a personal app. One-on-one chat: A user can initiate a private conversation with a bot.Personal apps: In a personal app, a bot has a dedicated chat tab.You can use bots in the following contexts: Bots can proactively notify users about changes or updates to your app via chat. Users can chat with a bot to get their questions answered or type commands to have the bot perform a narrow or specific set of tasks. Mobileīots integrate directly into Team’s messaging framework. This also gives you the option to implement role-based views for your tour. In channels and group chats, a tour should open in a modal (also known as a task module so it doesn’t interrupt ongoing conversations. Including buttons the let users try bot commands is encouraged. In a personal app, a carousel can provide an effective overview of your bot and any other features of your app. Tours should be accessible without having to sign in. For example, include screenshots of your message extension. If applicable, they’re also great for describing your app’s other features. A tour is the most effective way to describe what your bot can do. You can include a tour with welcome messages and if the bot responds to something like a “help” command. You can simplify the authentication process using single sign-on (SSO).ĭon’t forget: In the bot command menu ( What can I do?), you must also provide a command to sign out. When a person messages a bot, sign in may be required use all its features. Carry that thinking into your bot design. In real life, if you entered a room full of people you’d introduce yourself instead of welcoming everyone who’s already there. Your bot's introduction should be slightly different in channels and group chats compared to a personal space (like a personal app). Welcome message in channels and group chats If possible, these suggestions should return stored responses without having to sign in. The message includes a greeting, what the bot can do, and some suggestions for how to interact. In personal contexts, welcome messages set your bot's tone. This initial exchange helps people understand what to do with the bot, find out its limitations and, most importantly, get comfortable interacting with it. It’s critical that your bot introduces itself and describes what it can do. With an in the new chat or compose box (the following example shows how you can do this in a group chat). Using the app flyout by selecting the More icon on the left side of Teams. Users can access bots that were added on desktop with an can add a bot one of the following ways: Get the Microsoft Teams UI Kit (Figma) Add a botīots are available in chats, channels, and personal apps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |