The buttons disappear once any of the suggested actions is selected.Ī card that can play videos. Presents your user with a set of card actions that represent a user choice. It typically contains text and one or more buttons that the user can use to initiate a sign-in process. It typically contains the list of items to include on the receipt, tax and total information, and other text.Ī card that lets a user sign in. Typically used to visually highlight the buttons for a potential user selection.Ī card that enables a bot to provide a receipt to the user. Typically used to visually highlight a potential user selection.Ī card that contains a single thumbnail image, one or more buttons, and text. Cards adapt to the look and feel of each host channel.Ī card that can play animated GIFs or short videos.Ī card that contains a single large image, one or more buttons, and text. Typically used for cross-channel deployment of cards. Card typeĪn open card exchange format rendered as a JSON object. The following table describes the list of available cards and best practice suggestions of usage for each type of card. Let's take a closer look at cards, their actions, and some recommended uses.Īzure Bot Service cards are programmable objects containing standardized collections of rich user controls that are recognized across a wide range of channels. The type of card you use will be determined by the needs of your application. There's an incredibly wide range of uses for cards to help guide the conversation between your user and your bot. Did they ask for more information on a subject? Cards can provide in depth information using audio or video output, or a receipt that details their shopping experience. If a user has a set of choices for a single item, you can present a smaller single image and a collection of buttons with various options to choose between. If a user needs to select from within a fixed set of items you can display a carousel of cards, each containing an image, a text description, and a single selection button. CardsĬards allow you to present your users with various visual, audio, and/or selectable messages and help to assist conversation flow. Allowing the user to communicate "Hotels" by selecting a button labeled Hotels is easier and quicker than forcing the user to type "Hotels." On mobile devices, for instance, selecting is often preferred over typing. For instance, buttons are a great way to present the user with a simple choice. These same UI controls can also be effective in bots. When a bot is embedded within an app or website, it can represent virtually any UI control, using the capabilities of the app that is hosting it.Īpplication and website developers have relied on UI controls to enable users to interact with their applications. A bot can use a collection of UI controls to mimic an app, or can even run embedded within an app. Rich user controls are common UI controls such as buttons, images, carousels, and menus that the bot presents to the user and the user engages with to communicate choice and intent. For example, GroupMe clients can't display a typing indicator. In some cases, a channel may not support a particular feature at all. In cases where a message contains feature(s) that a channel doesn't natively support, the channel may attempt to down-render message contents as text or as a static image, which can significantly impact the message's appearance on the client. Even when multiple channels support a feature, each channel may render the feature in a slightly different way. However, each channel, such as Facebook, Slack, and so on, ultimately controls how its messaging clients render features. You can create bots with various features such as text, buttons, images, rich cards displayed in carousel or list format, and more.
0 Comments
Leave a Reply. |