Core concepts
The vocabulary the rest of the docs assume — organisations, workspaces, chatbots, conversations, messages, leads, contacts, credits, and plans.
evoriqa is multi-tenant, and a handful of terms describe how your data is organised, billed, and isolated. This page defines them once so the rest of the documentation can use them freely.
The tenant hierarchy
Two objects sit above everything else: an organisation owns one or more workspaces, and every other record belongs to a workspace.
Organisation
An organisation is the billing entity. It is either a direct customer or a reseller, and it owns one or more workspaces. Plans and invoices attach at the organisation level, so a custom deal or a billing waiver applies to the org rather than to a single workspace. White-label branding — the app name, primary colour, email sender, support URL, and "Powered by" toggle — is also set at the organisation level and applies to all of its workspaces; a reseller organisation additionally carries a logo, colours, and a custom domain across the many client workspaces it owns. When an organisation's last workspace is deleted, the now-empty organisation is removed too, so "owns an organisation" stays in step with "owns a workspace".
Workspace
A workspace is the tenant that everything scopes to. All data is isolated by workspace, and a workspace holds its own chatbots, knowledge base, conversations, leads, contacts, and team members. A user can belong to several workspaces and switch between them from the dashboard, but can own at most one workspace of their own.
Inside a workspace
Chatbot
A chatbot is one configured AI agent. A workspace can have multiple chatbots (the number is capped by plan), and each has its own name, system prompt, tone, greeting, fallback message, language, and AI model settings. Every chatbot has a unique public ID that powers its embeddable widget, and an allowed-domains list that restricts where it may run.
Conversation
A conversation is a thread between a visitor and a chatbot. Full history is kept per chatbot and per workspace, with transcripts you can read back, and each conversation carries a status such as open, closed, or needs-human. A conversation can also produce a lead, which links back to the conversation it came from.
Message
A message is a single turn within a conversation. Replies stream token by token for a responsive typing experience, visitors can leave thumbs feedback on a message, and each message is tagged with an intent, a sentiment, and a lead score.
Lead
A lead is a captured sales contact — name, email, phone, company, and message — gathered from the widget form, the agent's capture_lead action, or the public lead API. Every lead carries a pipeline status that moves through new → contacted → qualified → won / lost, can be assigned to a workspace member, and links back to the conversation that originated it.
Contact
A contact is a persistent record of a customer's identity across conversations, leads, and channels. Repeat visitors with the same email collapse into a single contact with merged history and a rolling lead score, so you see one person rather than many disconnected sessions.
Billing
Credit
A credit is the unit of AI usage. Usage is metered into credits mapped to real provider cost and drawn down across chat, voice, and actions. Each paid plan grants a monthly credit allowance, and credits are the spend gate for paid plans; the Free plan instead runs on a flat monthly message quota. One-time top-up packs never expire. When a workspace exhausts its credits or quota, visitors get a friendly "assistant is unavailable" reply rather than a raw error, and human handoff keeps working.
Plan
A plan is the subscription tier that sets a workspace's limits and its credit allowance. Customer plans are Free, Starter, Pro, and Business, each enforcing limits on chatbots, knowledge sources, team members, upload size, and branding removal, and billed monthly or annually. Resellers subscribe to separate reseller plans that let one organisation provision many client workspaces from a shared credit pool.
Every price, credit allowance, and limit lives in a single runtime catalogue, so the enforced limits and the pricing page always agree. Check the billing page in your dashboard for the numbers that apply to your workspace.
Where each concept lives in the dashboard
| Concept | Where you see it |
|---|---|
| Organisation | Settings → branding, and the billing page |
| Workspace | The workspace switcher in the top bar; Settings |
| Chatbot | Chatbots, and every tab beneath one bot |
| Conversation | Inbox, and Conversations history |
| Message | Inside a conversation thread |
| Lead | Leads, as a pipeline board and a list |
| Contact | Contacts, with merged history per person |
| Credit | Billing → usage, and the credit balance in the top bar |
| Plan | Billing → plan |
Where to go next
- What is evoriqa? — the product in
one page.
- Quickstart — put a live widget on your
site in five steps.
- Chatbot settings — every option a chatbot exposes.
- Credits and top-ups — how usage is
metered.
Last updated