{"id":494,"date":"2020-04-16T13:12:23","date_gmt":"2020-04-16T20:12:23","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/microsoft-copilot\/blog\/copilot-studio\/customize-the-bot-behavior-when-no-intent-is-triggered\/"},"modified":"2024-06-05T05:41:28","modified_gmt":"2024-06-05T12:41:28","slug":"customize-the-bot-behavior-when-no-intent-is-triggered","status":"publish","type":"copilot","link":"https:\/\/www.microsoft.com\/en-us\/microsoft-copilot\/blog\/copilot-studio\/customize-the-bot-behavior-when-no-intent-is-triggered\/","title":{"rendered":"Customize the bot behavior when no intent is triggered"},"content":{"rendered":"
The bot triggers corresponding topics based on the user\u2019s input. If the bot can\u2019t determine the user\u2019s intent, it will prompt for a topic again. After two prompts, the bot will escalate to a live agent.<\/p>\n
On some occasions, you may want to customize the bot behavior when no intent is triggered. For example\u00a0like searching knowledge base articles or routing to existing bot services. This can be achieved by adding the System Fallback Topic\u00a0<\/strong>from Settings.\u00a0<\/strong><\/p>\n Once the System Fallback Topic is added, you can find it alongside with other system topics in your topic list. You can edit it just like you can edit other system topics — add or remove nodes, redirect to other topics, call services using Power Automate or Bot Framework Skills. There’s a\u00a0{x} UnrecognizedTriggerPhrase <\/strong>variable in the topic which carries the last user utterance. It can be used as a context when calling other services.<\/p>\n