AI agents for customer support · Part 4 of 14
Writing knowledge an AI agent can use
How to find the answers nobody wrote down, write each one so the agent can use it, and take your macros apart.
The short version
Your agent can only answer from what you wrote down, and it often reads one piece of an article, not the whole page. Five steps get your knowledge ready for it:
Step 1Find the answers nobody wrote down
When your knowledge has no answer, the agent should hand the customer to a person (part 2). Each of those hand-overs names an article to write. So does every reply your team sends from memory, with no article behind it.
Today
The agent finds nothing
A customer asks a new question. The agent searches your knowledge and hands over.
A person answers from memory
Written down as an article
with an owner
Next time
The agent finds the article
A customer asks the same question, and the agent answers alone.
Step 2Write one answer per question
Title each article with the question as customers ask it, and answer it in the first sentence. Then write out every condition: who it applies to, by when, and the exceptions. An agent can’t apply “usually”.
As often written
Returns policy: we usually accept returns on most items within a reasonable time. Some exceptions apply. Contact us for details.
An agent would have to guess: usually, most items, a reasonable time, some exceptions, contact us.
Written for the agent
- Question
- Can I return a sale item?
- Answer
- Yes, within 14 days of delivery, if it is unused.
- Conditions
- Items marked final sale: no returns. Personalised items: no returns.
- Steps
- Start it from your order page.
Step 3Make every piece stand alone
Many agents search your knowledge in small pieces and answer from the best matches. A piece that leans on the paragraph before it loses its meaning. So name the subject in every paragraph, and put in words what a picture or a table shows.
The article: Changing your order
You can change the address until the order is packed.
After that, it can’t be changed. Ask the courier to redirect it. the piece the agent finds
What the agent reads
Changing your order: after that, it can’t be changed. Ask the courier to redirect it.
After what? What can’t be changed?
Written to stand alone
Once an order is packed, its delivery address can’t be changed. Ask the courier to redirect the parcel.
Zendesk describes its own generative AI this way: your articles are split into chunks, and each reply is written from the article’s title and the chunks that match best. Its guide asks writers to repeat the noun rather than write “it” or “they”.
Zendesk help, “Optimizing your knowledge content for generative AI”Step 4Take your macros apart
A macro is written for a person who has just done something. It confirms an action, sets a tone, and often carries a note meant only for your team. Keep its facts as articles. Its limit is a rule (part 1, step 5), and the confirmation should come from the tool that acted.
Macro: refund for a damaged item
Hi {name}, sorry it arrived damaged.
Set the tone once, in the agent’s settings.
I’ve refunded {amount} to your card.
The agent says so once it’s done (part 7).
You’ll see it in 5 to 10 working days.
A fact the customer needs.
Internal: up to €30, then the team lead.
A limit, checked before it acts (part 8).
In July 2025 Gorgias took macros out of its AI Agent’s knowledge. They had been potentially useful in fewer than 1% of the messages it answered, often led to inaccurate answers, and are “usually written as confirmation messages rather than guidance”.
Gorgias, product update, 23 July 2025Step 5Keep one answer, with an owner
When your help center, your website and an old PDF all answer the same question, the agent may quote any of them. Keep one answer, delete the others or point them to it, and name who changes it on the day the policy changes.
Three answers to one question
“How long do I have to return this?”
- Help center
- 30 days
- Website FAQ
- 14 days
- A PDF from 2024
- within a month
The agent may quote any of them.
One answer, with an owner
- Answer
- 30 days from delivery
- Owner
- the returns lead
- Last checked
- 1 October 2026
- Everywhere else
- deleted, or links here
Next in this series
Part 5: RAG for support teams, in plain words. See all 14 parts.
Where Himmel fits
The limits you take out of your macros are rules, not knowledge. With Himmel, your team confirms them in plain words, and the agent’s tool checks them before it acts.
Sources
- Zendesk help, “Optimizing your knowledge content for generative AI”, read on 19 October 2026.
- Gorgias, “Update: Macros aren’t used as a knowledge source for AI Agent”, 23 July 2025.
