A developer wants to collect a customer's preferred contact method (Phone, Email, or Chat) and their availability time using a structured form within a Copilot Studio topic, rather than through sequential text question nodes. The agent runs in Microsoft Teams. What is the best approach?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Adaptive Cards are the Teams-native way to present structured forms — one card collects both fields at once, user hits Submit, and your topic variables get all the values in one shot. Answer: B.
Full explanation below image
Full Explanation
Adaptive Cards are a cross-platform card format supported natively in Microsoft Teams. They can contain multiple input fields (text, choice sets, date/time pickers, toggles) and a submit action that returns all field values at once to the Copilot Studio topic.
Option B is correct. The developer creates an Adaptive Card with a ChoiceSet input (Phone, Email, Chat options) and a Time input. The card is sent via an 'Ask with adaptive card' or 'Send a message' node. When the user fills in the fields and clicks Submit, Copilot Studio automatically maps the submitted values to topic variables that the developer configures. This provides a much better UX than sequential questions — the user sees and fills the entire form at once.
Option A is incorrect. Sequential question nodes work but create a multi-turn conversation for what could be a single interaction. Each question requires a round-trip message, which is slower and less efficient than a single card submission.
Option C is incorrect. Launching a Power Apps form from within a Teams conversation is technically complex, requires the user to navigate to a separate experience, and is not a natural fit for an in-conversation data collection scenario.
Option D is incorrect. Microsoft Teams does not render arbitrary HTML in chat messages. Teams supports Adaptive Cards and a subset of Markdown, but raw HTML forms are not rendered — they appear as plain text.