Answers to the questions teams ask before they launch.

Chatvox is a team-based AI agent platform for building customer-facing chat experiences. Teams can train agents on business content, deploy them through public chat pages and website widgets, and connect conversations to workflow actions.

The product is a strong fit for marketing teams, support teams, sales teams, and SaaS operations teams that need branded AI chat backed by real content and connected to business workflows.

No. The product is broader than a widget. It combines agent creation, knowledge ingestion, deployment, actions, integrations, analytics, and billing controls in one platform.

The typical flow is: create an agent, add knowledge sources, customize branding and behavior, publish a public chat page or web widget, connect integrations if needed, then monitor conversations, leads, usage, and feedback.

Chatvox supports file uploads, direct URLs, selected website pages, sitemap imports, raw text, Q&A entries, and crawl jobs. This lets teams combine website content, docs, internal references, and controlled answer material in one agent.

Yes. Website sync starts from a URL, discovers internal links, and lets you choose which pages become training sources. Sitemap import is also available for larger or more structured sites.

Each source moves through a processing lifecycle such as pending, scanning, processing, embedding, indexed, or failed. The product shows progress and lets teams understand where a source is in the pipeline.

Yes. Chatvox supports retraining indexed sources, retrying failed ones, bulk deletion, and replacement behavior when source content changes.

Yes. Knowledge is tracked per agent by character count. Current limits are 400,000 characters on Free, 10,000,000 on Starter, 20,000,000 on Standard, and 40,000,000 on Pro.

Chatvox currently supports two customer-facing deployment channels: Public Chat and Web Widget. Both are powered by the same underlying agent.

Yes. Each deployment can use its own model, system prompt, welcome message, suggested prompts, persistence mode, and appearance settings.

Public Chat is best for standalone help pages, support experiences, campaign pages, and any shareable self-service link where you want a branded chat page.

The Web Widget is designed for websites and SaaS products where you want an embeddable chat launcher. It supports display settings, color controls, prompt behavior, and generated embed script output.

Yes. The widget supports allowed embed domains, including exact domains, wildcard subdomains, and localhost. If the allowlist is configured, the widget can be limited to approved origins only.

The current customer-facing actions are Collect Leads, Salesforce Add Lead, Slack Notification, and Custom API. They are configured per agent and can be enabled or disabled individually.

Yes. Free includes 0 actions, Starter supports up to 5, Standard up to 8, and Pro up to 12.

Yes. Native integrations like Slack and Salesforce require Starter or above. They are also connected at the agent level, not only the workspace level.

Yes. Action configuration can be scoped to specific deployment channels, which in practice maps to Web Widget and Public Chat.

That is what Custom API is for. It lets Chatvox call your own HTTPS endpoints so you can connect internal systems, CRMs, ticketing flows, scheduling, or other operational tooling.

Chatvox uses plan-based access with monthly credits, agent limits, team-member limits, action limits, and optional add-ons. Plans mainly control scale and model access, while add-ons extend capacity and branding control.

The Free plan includes 50 monthly credits, 1 agent, 1 team member, 400,000 characters of knowledge per agent, GPT-4o Mini access, and no actions. Free-plan agents are deleted after 14 days of inactivity.

Current add-ons include credit packs, extra agent capacity, white-label branding, and optional auto top-up depending on billing configuration. Add-ons require an active paid subscription.

Yes. Teams can optionally set a credit cap per agent to protect shared workspace usage, limit experimentation on high-cost agents, or allocate budget across agents.

Yes. White-label is a paid add-on that removes Chatvox branding from customer-facing deployment surfaces like the public chat page and web widget.

Yes. Chatvox is organized around teams that can own agents, manage billing, invite members, and share access to the same workspace. The current roles are Admin, Editor, and Viewer.

The product supports standard email and password authentication, password reset, email verification, optional Google sign-in when configured, and two-factor authentication built on Fortify.

Chatvox includes a built-in help flow for support case submission with account selection, related agent selection, issue type, severity, subject, description, and up to three attachments.

Public chat supports request throttling and session proof checks for chat history flows. Widgets support allowed embed domain allowlists. The platform also includes invitation throttling, billing throttling, onboarding throttling, IP bans, and account flags.

Yes. Super admins have access to audit logs, moderation tools, global integration controls, support ticket queues, team management, and trial management.