A Copilot Studio topic calls an action that requires three inputs: customer ID, product SKU, and order date. Instead of asking for each in separate turns, you want the agent to collect all three in a single conversational exchange if the user provides multiple pieces in one message. Which feature enables this?
Select an answer to reveal the explanation.
Short Explanation
Slot filling lets the agent grab several required values from one user message, so if someone says their customer ID, product SKU, and order date together, you get all three inputs filled at once. Entities tell the agent what to look for, so it only asks for what's still missing.
Full Explanation
Slot filling in Copilot Studio refers to the agent's ability to extract multiple required inputs from a single user utterance. When a question node is configured with an entity type, such as Number for customer ID, Product for SKU, and Date for order date, the agent performs entity extraction on each user message. If the user provides multiple values in one message, multiple slots are filled simultaneously. The agent only asks follow-up questions for slots that remain unfilled, which creates a natural, efficient conversation; if the user volunteers all information upfront, no additional prompting is needed. The condition-node approach that checks whether variables are populated before moving to the next question is a manual implementation of the same concept, but it requires complex branching for every combination of what the user might have provided, while slot filling automates this elegantly. The Power Automate flow approach that parses the user message and returns extracted values adds unnecessary round-trip latency and complexity, because entity extraction is built into Copilot Studio's NLU layer and no flow is needed. The 'All Required' node type in the topic canvas that batches multiple question nodes into one does not exist as a Copilot Studio canvas element. For the exam: slot filling means entity extraction fills multiple action inputs from a single user turn. Configure question nodes with appropriate entity types. Built-in entities include Number, Date/Time, Age, Currency, Email, and URL. Custom entities can be created for domain-specific values like product SKUs.