Core concept: Conversations
A conversation is a chat session between a visitor (or API client) and one of your deployed assistants. Each conversation stores message history, metadata, and optional analytics signals.
What Chatevo stores
Section titled “What Chatevo stores”| Field | Purpose |
|---|---|
| Messages | User turns, assistant replies, tool calls |
| Citations | Which knowledge-base chunks supported an answer |
| Rich content | Carousels and cards from verified tool JSON |
| Deployment link | Which widget or API deployment handled the session |
| Timestamps | Created, last activity |
Conversations persist in PostgreSQL. They are scoped to your organization — tenants never share data.
How conversations start
Section titled “How conversations start”- Widget — A visitor opens the chat bubble; Chatevo creates or resumes a session via a client-side conversation ID.
- Direct API — Your server creates a conversation with the Conversations API, then posts messages to it.
See Conversations API and Widget messages.
Multi-turn context
Section titled “Multi-turn context”Later messages include recent history so the Intent Analyzer and Query Strategist understand follow-ups like “What about the premium plan?” or “Check order #4821 instead.”
Retention of old conversations may be trimmed by retention_days on RAG or search settings. See RAG settings.
Viewing conversations
Section titled “Viewing conversations”Editors and admins can browse conversation history in the dashboard for QA and support handoff. Viewers have read-only access where your plan allows analytics.
Usage metering
Section titled “Usage metering”Each assistant reply that runs the full pipeline counts toward your plan’s monthly message quota. Test-panel messages in the dashboard also count. Monitor usage under Usage and quotas.