A consultant is building a custom Copilot Studio topic for a sales chatbot that answers pricing questions from prospects on a self-service portal. When the topic's confidence in answering a pricing question is low, the design must hand the conversation to a human seller and preserve a record of the exchange for quality review. (Select TWO.) Which two actions should the consultant add to the topic to meet both requirements?

The correct actions are the create-record action that writes the full conversation transcript to a custom Dataverse table for review, and the escalation node that transfers the conversation to a human seller when confidence falls below the threshold. The scenario has two distinct requirements — routing low-confidence conversations to a human, and preserving those conversations for later review — and each requires its own action inside the topic. The escalation node satisfies the human-handoff requirement, while the create-record action satisfies the quality-review requirement; together they cover both halves of the design without either one substituting for the other. The canned-pricing-answer option is incorrect because returning the same answer regardless of confidence ignores the entire premise of the requirement, which is that low-confidence situations need different handling than confident ones, and it does nothing to involve a human seller. The disable-fallback option is incorrect because disabling the fallback topic removes the very mechanism that would trigger an automatic handoff, which is the opposite of what the scenario asks for — it guarantees that low-confidence conversations are never escalated rather than ensuring they are. Neither wrong option contributes to logging a transcript, and neither one provides the required human handoff.