Glossary
Term | Meaning | See |
|---|---|---|
admin | An organization role that can rename the organization and invite and remove members, but not change roles. An admin sees billing only as a billing manager. | |
AI Assistant, Assistant | An assistant that answers visitors' questions from its Knowledge Base, on a website or in Reverb 2.0 help. You build it in WebWorks Platform. | |
Assistant ID | The ID that identifies one Assistant. A Reverb 2.0 target takes it in its Assistant ID setting, and the Embedded Assistant's script tag carries it. | |
billing manager | A member the owner allows to see and manage the organization's billing. | |
citations | The markers in a Reverb Assistant's answer that open the passage the answer came from. | |
credits | The dollars an organization holds to pay for usage. | |
daily budget | The most an Assistant may spend on visitors' answers in one day, counted in UTC. | |
daily preview allowance | The free amount each organization gets every day for answers in Preview. | |
Embedded Assistant | An AI Assistant installed on a website with one script tag. | |
free model | The model an answer runs on, at no charge and with reasoning off, when credits can't pay for it, when a reached daily budget is set to keep answering, or when the Assistant is set to use it. | |
Grounding Knowledge | The published help an ePublisher build produces, uploaded as Knowledge Files: what a Reverb Assistant answers from and cites. | |
In Deployment | The switch that makes an Assistant answer visitors on its Origin Domains. An Assistant with it on is in deployment. | |
included allowance | The dollars a paid plan includes each month, spent before purchased credits and reset at the start of each month of the plan. | |
Instructions | The text that tells an Assistant what it is and how it should answer. | |
Knowledge Base | Everything an Assistant searches to answer a question: imported websites and uploaded files. | |
Knowledge Files | The | |
member | An organization role that can build, test and deploy Assistants. A member sees billing only as a billing manager. | |
organization | What owns Assistants, billing and members. A person can belong to several. | |
Origin Domains | The domains of the sites where an Assistant answers. They also limit the websites it can import and the addresses its answers can link to. | |
owner | The organization role with every permission, including roles and billing. | |
per-visitor message limit | How many messages one visitor may send to an Assistant in a time window. | |
plan | The organization's subscription: Pay-As-You-Go, Pro or Enterprise. | |
plan code | A code that comes with a WebWorks invoice order and puts the organization on a plan when redeemed. | |
Preview | The tab where you test an Assistant before and after it is in deployment. | |
purchased credits | Credits bought by hand or through auto-replenishment, plus the signup credit. | |
Reasoning Fuel | Your own reference files in the Knowledge Base, outside your published content. Answers draw on it without citing it. On the Embedded Assistant, the Sources row never lists it, but an answer can link to an absolute address it contains. | |
Reverb Assistant | An AI Assistant built into Reverb 2.0 help through the target's Assistant ID. | |
Sources row | The list under an Embedded Assistant's answer of the imported pages the answer used. | |
Top concepts | The dashboard's grouping of visitors' questions by what they ask about. | |
Websites | The Knowledge Base source that imports a site's pages. |