What should a fallback topic in Copilot Studio do?
Why A is the answer
Handle messages that no other topic or knowledge can answer
Fallback gives the user a useful path instead of a dead end.
In detail
- A fallback topic handles messages that nothing else can answer.
- Review what lands there to find missing topics.
Use case
An illustrative scenario, not a real incident.
A user asks something the agent cannot answer. The fallback offers a rephrase or a person, instead of a dead end.
See it in different ways
flowchart TD
A["User message"] --> B{"Matches a topic?"}
B -->|Yes| C["Run the topic"]
B -->|No| D{"Answer from knowledge?"}
D -->|Yes| E["Generative answer"]
D -->|No| F["Fallback topic or handoff"]stateDiagram-v2 [*] --> Message Message --> Topic: a topic matches Message --> Knowledge: covered by knowledge sources Message --> Fallback: nothing can answer Topic --> [*] Knowledge --> [*] Fallback --> [*]
flowchart TD
Q{"Can anything answer it?"}
Q -->|"A topic matches"| A0["Run the topic"]
Q -->|"Knowledge answers"| A1["Generative answer"]
Q -->|"Nothing"| A2["Fallback"]Key point: Fallback handles what nothing else can.
Why the other options are wrong
- B. Replace all of the other topics in the agent
- It does not replace other topics.
- C. Run once a day on a fixed schedule
- It does not run on a schedule.
- D. Publish the agent to a new channel
- It does not publish anything.