Lessons
Teach the agents about your business, your readers and your standards, so every future prompt follows what you taught.
Lessons are short rules you write for the agents. Active lessons go into every agent prompt for their scope, newest first. Use them to fix a mistake once instead of editing the same thing in every draft. The best time to add a lesson is right after you read a draft and see something the agent got wrong.
Lesson scopes
Each lesson has a For field that decides which agents read it:
| For | Read by | Use it for |
|---|---|---|
| Everyone (business fact) | All agents: research, prompts, briefs, writer, QA, audits, X posts | Facts about your business and customers |
| Writer | Brief and writer agents | Tone, structure, examples, words to use or avoid |
| QA | QA editor | How strict to be, what to check |
| Research and audit | Keyword research, AI prompts and audit agents | Topics to chase or skip, how to weigh data |
Add a lesson
From the Lessons page:
- Open Lessons in the site menu.
- In Add a lesson, choose For.
- Write the Lesson in one or two plain sentences.
- Click Save lesson.
From a ticket:
- Open the ticket.
- In Teach the agents, choose For and write the lesson.
- Click Save lesson. The lesson links back to the ticket, so you can see where it came from.
From a review note:
- On the ticket's draft, find a note in the review panel.
- Click Make it a lesson. The writer follows it in every future article.
Write good lessons
Good lessons are specific and testable. Compare:
| Weak | Strong |
|---|---|
| Write better. | Open each section with the answer in one sentence, then explain. |
| Know our customers. | Our best customers run 10 to 50 person companies. Write for owners who do payroll themselves. |
| Be careful with tax. | Our customers are HR managers, not accountants. Avoid tax jargon. |
| Don't target bad keywords. | Skip keywords about free templates. They bring visitors who never buy. |
| Check facts. | Fail any draft that says we integrate with a tool not listed in the approved facts. |
Tip: One rule per lesson. Short lessons are easier for the agents to follow and easier for you to pause later.
Lessons or settings?
Some rules belong in Settings instead. Settings are structured, so code checks can enforce them.
| Rule | Put it in |
|---|---|
| Prices, plan limits, trial length, features | Approved product facts in Settings > Business profile |
| Things you must never say | Prohibited claims |
| Words to ban | Banned words and phrases (QA fails drafts that use them) |
| Topics to skip completely | Topics to avoid |
| Writing tone | Brand voice, plus Writer lessons for details |
| Reading level, length, image count | Settings > QA rules |
Use lessons for the judgment that settings cannot hold.
Pause or delete a lesson
Each lesson on the Lessons page has:
- Pause: keeps the lesson but stops sending it to the agents. Paused lessons look faded. Click Activate to turn it back on.
- Delete: removes it for good.
Note: Too many lessons make prompts long and can conflict. Review your lessons each month. Pause old ones that no longer apply, and merge ones that say the same thing.
When lessons take effect
Lessons apply to the next agent run. They do not change existing drafts or briefs. To apply new lessons to work already planned:
- Click Rewrite briefs with current settings on the Ticket board, or Rewrite brief with current settings on one ticket.
- Click Rewrite and QA again on a ticket to write a new draft.
Example workflow
- A draft for "payroll software for startups" fails QA twice for using accounting jargon.
- You read the QA report and add a Writer lesson: "Explain payroll terms in everyday words. Our readers are founders, not accountants."
- You click Rewrite and QA again.
- The next draft passes. Every later article also follows the lesson.
Related
Did this page help? Tell us at support@agenticseo.com.