Building good agents
A good agent handles exactly one recurring task, has clearly structured instructions and has been tested with real cases.
An agent is only as good as its instructions and its knowledge. This guide covers which task suits an agent, what instructions that work look like, and how to test and maintain an agent. Setting one up is shown in Creating an agent.
The right task
A good candidate comes up several times a week, is done by several people, has a recognisable result (a quote, a reply email, minutes) and relies on documents that fit in a brain.
One agent, one task. A "customer service agent" for everything collects rules over time that contradict each other. Two agents such as "Email replies" and "Complaints" work more reliably. If a task needs no fixed rules or documents, a saved prompt is enough.
The quickest start is one of the ten Agent templates or the Describe tab, where you say in your own words what the agent should do. Both give you a draft: always read the instructions under Configure before you save.
Instructions that work
Structure instructions into role, task, audience, tone, rules and output format. Describe produces the same structure, and it helps everyone who maintains the agent later.
- Concrete beats adjectives. "At most 150 words, no stock phrases" rather than "professional".
- Say what happens when something is missing. "If details are missing, ask instead of estimating" is often the most valuable rule.
- Name your sources. "Fees only from the 2026 fee schedule", and add the brain under Knowledge.
- Stay short. Every extra rule competes with the others. Facts belong in the brain, not in the instructions.
Conversation starters show in the empty chat what the agent is for. Write them the way your team would write ("Draft a quote for a new engagement", not "Help"), with placeholders such as {{client name}} for what is missing.
What goes where
| Content | Where | Why |
|---|---|---|
| Procedure, tone, rules, format | Instructions | Applies in every chat |
| Price lists, policies, handbooks | A brain under Knowledge | One place to maintain, citations, access per person |
| Letters, quotes, presentations in the company layout | Company template | An admin uploads it once, it is ready in every chat |
| A form only for this agent | Files on the agent | Attached to every chat, visible to everyone who uses it |
| Up-to-date public information | Web search | Turn it on only where it is needed |
| Email, calendar, cloud files | Connectors | Everyone uses their own connection |
An agent never widens access: everyone only gets answers from brains they can read themselves and uses only their own connectors. For an agent with one clear task, choose Only these under Connectors, for example only Outlook for an email agent.
Testing and maintaining
- A test set of five to eight real cases: two typical requests, one incomplete, one edge case, one the agent should refuse, one with personal data. Run through it in the Preview after every change, each time after Start over. See Testing an agent.
- Test first, then save. Saved instructions apply at once in every chat with the agent, ongoing ones included. Under History, Restore brings back an earlier version.
- Bigger rebuilds on a copy with Duplicate.
- One person responsible collects feedback, and every request the agent got wrong goes into the test set.
Name the agent after its task ("Quote agent", not "Lea's bot") and share it only after testing, see Sharing and using agents.
Example: an email reply agent
For the customer service team of a joinery. Copy the text into the Instructions field and adapt it.
**Role**
You are the email reply agent in the customer service team of Holzwerk Brunner GmbH, a joinery.
**Task**
You draft replies to customer emails: appointment requests, questions about ongoing orders, care of wooden surfaces and complaints. Staff check every draft and send it themselves.
**Audience**
Private customers and architecture firms.
**Tone**
Friendly, personal and brief. Always formal address. No stock phrases.
**Rules**
- Facts on delivery times, warranty and care only from the Customer service brain. If nothing is found, say so in the internal note, not in the reply.
- Do not invent prices, dates or commitments. Where a date is needed, say that we will be in touch.
- Complaints: thank them, briefly summarise the facts, ask for photos. Do not admit fault, do not offer compensation.
- Threats or letters from lawyers: no draft, only a note to involve management.
**Output format**
1. Subject line
2. Reply draft of at most 150 words
3. Below a line: "Internal note" with open items and the sources usedAdd the brain "Customer service" under Knowledge, turn Web search off and choose Only these with Outlook under Connectors. A quote agent is shown in Writing quotes with an agent, an agent for HR questions in A handbook for the whole team.
Frequently asked questions
They are probably not allowed to read the brain. The editor shows a note when an attached brain is readable by only a few people. Share the brain, see Access and sharing.
Next steps
Choosing the right model
Start with "Default", switch to a stronger model for difficult or long tasks and to an economical one for simple bulk work.
Building a good brain
One brain per audience, only current documents, clear instructions, the right access and real test questions, then answers and sources are right.