Few-shot examples

By the end of this page a phrasing that kept reaching the wrong specialist will reliably reach the right one.

Prerequisites

A system with two or more connected agents (Connect agents).
Admin or Developer role.

What they are

A few-shot override is an example message you attach to one agent, saying: when someone writes something like this, that agent should answer. The router sees these examples while classifying, alongside your members’ skills.

They live on the agent card, under Few-Shot Overrides, so each example is owned by the agent that should win it.

💡

Try the skill first. An example query added to the agent’s own skill helps the router and helps the agent answer. Reach for a few-shot override when the phrasing is genuinely ambiguous between two members.

Add an override

Open the agent card

In Connected Agents, find the agent that should have answered. Expand Few-Shot Overrides — the count in the heading tells you how many it already has.

Type the message

Enter the phrasing as a user would write it, then press Enter or click +.

An agent card with Few-Shot Overrides expanded, listing example user messages with remove buttons

Use the wording that actually failed. “How much did we make last week?” is a useful override; “revenue question” is not — that belongs in the skill description.

Save

Click Save in the header. Remove an example any time with its ×.

How many

Each agent holds up to 10 overrides, and the router uses at most 20 examples across the whole system. Aim far lower — a handful of well-chosen examples per member beats a long list, which costs tokens on every classified turn and can drown out your skills.

When they apply

Overrides are only consulted when the router actually classifies a message. They have no effect when:

the system has one member — that agent takes every message without classification
the message is a greeting, thanks or acknowledgement — those stay with the current agent, with no model call

They also only influence the choice of agent. They never change how that agent answers.

Common issues

The override made no difference — Classification probably didn’t run for that message. See How routing works.
Both agents have similar examples — Contradictory examples cancel out. Keep each phrasing on one agent only.
Routing degraded after adding several — Too many examples, or examples that contradict skill descriptions. Trim to the few that fix real failures.
The add button does nothing — The box is empty, or the agent already has 10 overrides. Remove one first.

LLM settings — choose the model that makes the routing decision.