Unmet questions
An unmet question is one the agent couldn’t answer with confidence. This is the most valuable view in the dashboard, because it’s a direct feed of where your players are stuck and your game or your agent came up short.
Why they happen
Unmet questions fall into a few buckets, and the view labels each one so you can act on it.
- Outside the game. Questions about future updates, other games, or real life. Nothing to fix; the agent was right to decline.
- Behind a spoiler line. The player asked about content past your spoiler line, and the agent held back. If that content is now common knowledge, move the line.
- A real gap. The question is fair, in-scope, and the agent still couldn’t answer. These are the ones to send us.
- Too vague. The agent couldn’t tell what was being asked. Often these resolve themselves when the player rephrases.
What to do with them
Work the list top to bottom, by frequency. The bucket tells you the move.
| Bucket | Your move |
|---|---|
| Outside the game | Ignore, or add an escalation route if players keep asking your team things. |
| Behind a spoiler line | Adjust the spoiler rules if the content is no longer a spoiler. |
| A real gap | Send it to us via Slack or support@atcampfire.xyz. |
| Too vague | Usually nothing. Watch for a pattern. |
A real gap that a lot of players hit is worth flagging fast. We can often close it in a data refresh.
Turning them into product insight
The best use of this view isn’t fixing the agent, it’s reading your players. A question players keep asking that the agent can’t answer, and that the game doesn’t make clear either, is a design note. Some studios export this list weekly and bring it to their team. See exports and sharing.