Overview
Intent prompts describe what each intent means. When classification goes wrong, the fix is usually a change to one of those prompts — but working out which prompt and what change has always meant reading through misclassified mail and making a judgement call. Auto-tuned intent descriptions close that loop. Axon watches how your requests are actually classified, finds the patterns your prompts don’t cover yet, and proposes specific wording changes — along with the mail it learned from and the accuracy improvement it expects. Nothing changes on its own. Every proposal is yours to review, edit, test, and accept.Auto-tuned intent descriptions are part of Axon Premium. There’s nothing to switch on — if your organisation has Premium, it’s already running. See Included vs. Axon Premium.
What you get
Three things work together on every intent.How suggestions build up
Suggestions are grounded in your own corrected mail, so they need evidence before they can say anything useful.1
Axon collects examples
Every time someone corrects or confirms an intent in Flow, Axon keeps that mail as an example for the intent. This happens continuously, as part of real-time learning.
2
The intent reaches 50 examples
Once an intent has gathered 50 examples, it has enough evidence for Axon to reason about, and suggestions unlock for that intent.
3
Axon proposes a change
Axon looks for patterns your prompts don’t cover yet and creates a suggestion set for you to review.
You don’t have to wait for the monthly run
Axon reviews your intents on a monthly cycle, but that isn’t the only way suggestions appear. An intent unlocks as soon as it has gathered 50 examples — so if your team has been correcting heavily, suggestions can show up well before the month is out. In practice: the busier an intent is, the sooner you’ll see a proposal for it.If your classifications have been stable, there’s nothing to suggest and no set is created. Organisations with few corrections may not see suggestions for a while — that isn’t a fault, it means Axon has no evidence that anything needs changing.
When to use it
Reach for suggestions when Axon doesn’t feel like it’s improving — when the same kind of request keeps landing in the wrong place even though your team has been correcting it. That’s the signal that the problem is the intent’s definition rather than one sender’s phrasing. Examples alone can’t fix a definition; a prompt change can. It’s also worth checking after you’ve worked through a backlog of misclassified requests, or after adding intents that overlap with ones you already have.Prompt history
Every time an intent prompt is saved, Axon keeps the previous version. Open an intent and look next to the Instruction Prompt label — if the intent has earlier versions, you’ll see a Prompt history button with the number of versions. Click it to open the history. On the left is the list of saved versions, newest first. Select one and the right-hand side shows how it differs from the prompt that’s live today. Each version tells you:
The newest version is marked Latest.
Revert to an earlier version
Select the version you want and click Revert to this version. This brings the old wording back into the prompt editor. Reverting requires Editor access to Axon, and you can’t revert to the version that’s already live.What’s next
- Prompt suggestions — review, edit, and accept a proposed set.
- Testing prompt changes — see the impact before anything goes live.