Using the Fallback topic

The Fallback topic gets triggered when Copilot Studio doesn't understand a user utterance and doesn’t have sufficient confidence to trigger any of the existing topics.

There are multiple ways to use the Fallback topic.

Offload single question and answer pairs

If you have a large number of question and answer pairs for single-turn conversations, you can also consider offloading them to an external system and access them through the Fallback topic.

Copilot Studio limits a copilot to 1,000 topics. You can decide to manage exceptions to the Copilot Studio topics that should generally do things for the user through the Fallback topic. With the Fallback topic, you can get answers for users that you retrieve from external systems using Power Automate, by calling a cloud flow from an action node.

Tip

Give your copilot a personality

Question answering in Azure Cognitive Service for Language provides a readily available "chitchat" data source, of various tones such as "professional", "friendly", "witty".

Chitchat lets your copilot answer trivial questions, such As "how are you feeling today, copilot?".

Integrate with generative AI models

You can also use the Fallback topic to call a generative AI model, such as those used by the Azure OpenAI Service, to handle more questions from your end users.

Through the system prompt and prompt engineering, you can also feed the model with instructions, rules and input data before it generates an answer.

Learn from the Fallback topic

You should track what your customers are saying that doesn’t trigger a standard Copilot Studio topic. The phrases can enrich an existing topic’s trigger phrases, typically when the user utterance should have triggered a topic. The phrases can also lead to the creation of new topics to better serve your users as you understand better what they’re trying to accomplish.