Best practices

Improving your AI Agent isn’t just about adding more articles—it’s about structuring Knowledge so it reflects how people actually ask questions. When your content is clear, focused, and written in natural language, the Agent can provide more accurate answers and create a smoother experience for users.

The examples below show how to organize Knowledge in ways that reduce frustration, cut down on unnecessary handoffs, and help your Agent feel more helpful and human.

Example: Payment troubleshooting

Users often ask why their payments are being declined, and the AI Agent points them to a generic Common Payment Issues article. While the article is technically accurate, it doesn’t always provide the exact answer users are looking for—leading to unnecessary frustration or escalations.

You can improve the experience by restructuring your knowledge base:

  1. Split the generic article into focused ones, such as Card declined at checkout and Fixing payment verification errors.
  2. Use clear titles and keywords so the Agent can select the right article based on specific user phrasing.
  3. Include examples and common causes in each article, like insufficient funds, expired cards, or incorrect billing info.
  4. Write articles in plain language with clear steps users can try before escalating.

For example:

By organizing your knowledge this way, the Agent can surface more relevant answers, helping users resolve payment issues quickly and reducing reliance on support teams.

Example: Refund guidance for teen users

Younger users frequently ask how to get a refund from third-party apps or vendors. Since the knowledge base doesn’t include a relevant article, the AI Agent escalates these conversations by default—even when the answer is simple and well-documented elsewhere.

You can improve this by updating your knowledge base:

  1. Create a short, friendly article that explains how to request a refund from a third-party seller (e.g., How to get a refund from an app store or game platform).
  2. Use approachable language that reflects how younger users naturally ask for help (e.g., I want my money back from a game or I bought something by accident).
  3. Include platform-specific instructions where possible (e.g., links to Apple, Google Play, or in-game refund request forms).
  4. Add relevant tags and keywords so the Agent can find and serve the article when users ask in casual or informal ways.

By providing clear, age-appropriate guidance, you empower the Agent to respond helpfully—reducing handoffs and improving the experience for younger users.

For example:

Next steps: To improve this experience further, apply Personalization to detect the user’s age group (e.g., based on app usage context or declared info), so the Agent can tailor its tone and resources accordingly. Also, consider using Coaching to guide the Agent to suggest the newly created article when users mention refund-related terms in informal language.

This combination ensures the Agent not only finds the right information but delivers it in a way that resonates with younger users.