Multiple topics need the same "verify employee ID" conversation steps before continuing. What is the best authoring pattern in Copilot Studio?
Select an answer to reveal the explanation.
Short Explanation
Put the shared verification in one reusable topic and call it from the others. That way you update the steps once instead of chasing copies when policy changes.
Full Explanation
Reusable topics and redirects reduce duplication and centralize common sub-dialogs like identity verification, address capture, or confirmation. The reusable employee ID verification topic, called or redirected from other topics with inputs/outputs, is correct because it preserves context and data handoff. Duplicating the verification nodes in every topic raises maintenance cost and inconsistency risk. Using a separate Microsoft Form the agent cannot read breaks flow and may not return data cleanly. Putting steps only in analytics custom events without user interaction performs no verification. Exam tip: reuse via redirect/child topics and variable handoff.