Skip to main content
Classic AI sources are the factual knowledge base for the legacy AI setup. Add sources before you enable automatic replies in Classic AI.
Move existing Classic AI automation to AI Agents over time, not only new work. Follow the migration guide to transfer knowledge safely and retire overlapping Classic AI behavior once the replacement is proven. Start with Getting started, and use the Classic AI agent list only during migration or for necessary source maintenance.

​
Choose a source

​
Add website content

Website sources accept a root domain, sitemap, or specific page. With Smart Sync enabled, Chatarmin CX checks them weekly for updates.
1

Open Sources

Open the Classic AI agent list, choose your agent, then go to Sources → Website.
2

Add the website

Add a root domain such as https://example.com, a sitemap such as https://example.com/sitemap.xml, or a specific help-center section.
3

Review indexed pages

Remove pages the AI should not use and add missing pages manually.
4

Test after the first sync

Ask questions that should use the website and confirm the answers.
Classic AI website source with indexed pages

​
Add files

Use files for stable knowledge that is not available on a public page, such as compatibility tables, sizing guides, warranty details, or internal fulfillment rules.
1

Open Files

In your existing Classic AI agent, go to Sources → Files.
2

Upload a focused file

Upload a PDF, DOCX, CSV, or TXT file. Keep one topic per file.
3

Test the content

Ask questions the file should answer before relying on it for automatic replies.
Large or mixed-topic files can reduce answer quality. Split them by topic before uploading, or contact support for help preparing a large knowledge base.

​
Add Q&A

Use Q&A for repeated questions with one clear answer. For example:
  • How long does shipping take to Germany?
  • Can I return a worn item?
  • What size is Medium in EU sizing?
  • Do you ship internationally?
  • Is this promotion code still valid?
1

Open Q&A

In your existing Classic AI agent, go to Sources → Q&A.
2

Write the question

Phrase it as a customer would.
3

Write the answer

Keep it direct, complete, and ready to reuse.
4

Test variations

Ask the same question in a few different ways and confirm the AI finds the answer.

​
Add guidance

Use guidance when a customer question depends on a broader policy rather than one fixed answer. Good topics include return conditions, sizing, payment methods, loyalty programs, and delivery timelines.
1

Open Guidance

In your existing Classic AI agent, go to Sources → Guidance.
2

Choose one policy topic

Create a focused entry such as Return policy or Size guide.
3

Explain the decision

Include the policy, relevant conditions, exceptions, and when Classic AI should not answer.
4

Test real variations

Test customer messages that should use the guidance and edge cases that should not.

​
Best practices

  • Prefer a sitemap when your site has many pages.
  • Remove expired campaign pages and old file versions.
  • Keep files short and topic-specific. Split large, mixed manuals by topic.
  • Keep one customer question per Q&A entry and use customer language.
  • Maintain policy facts in one source instead of duplicating them.
  • Use guidance when an answer depends on several conditions.
  • Test the AI on real tickets before turning on auto-reply.