> ## Documentation Index
> Fetch the complete documentation index at: https://agenvik.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# AI agent best practices — Agenvik
> Improve your Agenvik agent's accuracy: structure knowledge sources, write clear system prompts, test before launch, and monitor conversations for gaps.
Use this page as a checklist when an Agent is not answering the way you expect, or when you want to prepare a polished launch.
## What you will learn
* How to make Knowledge Sources easier for the Agent to use
* How to write Behaviour settings that create consistent answers
* How to test before launch
* How to use Conversations and Analytics after launch
## Make Knowledge Sources specific
Agents work best when your source content is explicit. Avoid vague statements that require guessing.
Strong source content usually includes:
* Clear product names, plan names, and feature names
* Exact steps customers should follow
* Known limitations and eligibility rules
* Links written as plain visible URLs when the Agent should share them
* Separate sections for pricing, support, setup, and troubleshooting
## Use Q\&A for critical answers
Use **Q\&A** when a question needs a precise, repeatable answer. This is useful for refunds, pricing rules, handoff rules, business hours, and compliance-sensitive responses.
Keep each Q\&A focused. If one answer covers several topics, split it into multiple entries.
## Write Behaviour like an operating guide
The **System Prompt** should explain the Agent's job, audience, and boundaries. The **Guardrails** field should cover things the Agent must avoid or escalate.
A strong Behaviour setup includes:
* Who the Agent helps
* What the Agent can answer
* When the Agent should say it does not know
* How it should ask for missing context
* When it should direct the visitor to support{/* LEAD_GENERATION_DISABLED: original text was "collect a lead or direct the visitor to support" — restore when re-enabling */}
## Choose tone and verbosity intentionally
Use **Friendly** for conversational support, **Professional** for sales or B2B workflows, and **Neutral** for factual help centers. Use **Short** for fast FAQ answers, **Balanced** for general support, and **Detailed** for technical or process-heavy guidance.
## Test with real customer questions
Before launch, test the Agent with questions from actual conversations, support tickets, sales calls, or website search terms.
Test for:
* Accuracy: the answer matches your source content
* Completeness: the visitor gets the next step
* Boundaries: the Agent avoids unsupported claims
* Tone: the response fits your brand
* Recovery: the fallback message is helpful
## Monitor after launch
Use **Conversations** to inspect individual threads and **Analytics** to find patterns across many interactions.
Turn repeated weak answers into better Text sources, Q\&A entries, or Behaviour instructions.
## Next steps
Learn how to add, edit, delete, and train sources.
Review live conversations and identify content gaps.