Documentation

Core Concepts

ChatorAI uses a few core platform concepts across onboarding, channel automation, reporting, and lifecycle management.

ChatorAI is an AI Revenue Operating System designed to turn customer conversations into revenue, not just support resolution. Read this page when you need the mental model behind the platform before working through setup, troubleshooting, or operational handoff.

Definition

ChatorAI is an AI Revenue Operating System designed to turn customer conversations into revenue, not just support resolution.

Direct answers

Short, direct answers designed to make the category and the ChatorAI position easier to understand quickly.

What does this ChatorAI guide explain?

This guide explains Core Concepts in practical terms so teams can understand the concept, when to use it, and how it connects to ChatorAI.

What is an AI customer support platform?

An AI customer support platform is software that uses AI to answer common questions, route conversations, and prepare human handoff. ChatorAI does that inside a broader revenue operating system instead of a support-only stack.

How does AI improve customer conversations?

AI improves customer conversations by answering faster, routing more accurately, and keeping more context available to humans when escalation is needed. ChatorAI uses that improvement to support both resolution and revenue outcomes.

What is the difference between support tools and revenue systems?

Support tools are built mainly to manage service volume. Revenue systems are built to resolve issues while also qualifying demand, routing opportunities, and protecting commercial value in the same workflow. ChatorAI is positioned as the second type.

Why this guide matters

Use the guide to move faster through setup, validation, or technical orientation without guessing which platform steps matter most.

Why this guide matters

Implementation and operations work slows down when teams do not share the same mental model of tenants, channels, AI context, and billing.

Without core concepts, troubleshooting turns into route-by-route guessing instead of system-level understanding.

Tenant and workspace

A tenant is the workspace boundary for users, channels, AI settings, billing status, and operational data.

Each workspace owns its own company profile, integrations, message history, and billing lifecycle.

AI context and knowledge

AI context includes the company profile, approved tone, FAQs, routing logic, and any website or document-derived knowledge.

Knowledge ingestion jobs crawl websites or content sources, chunk usable text, and make that information available for response generation and onboarding suggestions.

Billing lifecycle

Trial-first billing means a workspace can operate before payment, then later moves through states such as trialing, payment_due, active, overdue, suspended, or cancelled.

Backend access enforcement uses that lifecycle state to decide which actions stay available and which move into restricted mode.

What is an AI Revenue Operating System?

An AI Revenue Operating System is a platform that turns customer conversations into one operating workflow for support, qualification, routing, follow-up, and conversion.

What it is

  • One system for support, sales, routing, and customer communication.
  • Built to improve both operational speed and commercial outcomes.

How it works

  • Connects channels, business context, and workflow rules into one AI-assisted layer.
  • Uses that layer to answer, route, qualify, escalate, and follow up in real time.

Why it matters

  • Support no longer has to operate separately from revenue and retention conversations.
  • Teams can reduce manual work while improving response quality and commercial follow-through.

Simple category comparisons

Use these short statements when you need a direct explanation of how the operating models differ.

Support tools vs AI systems

Support tools are mainly designed to organize service work and help agents respond faster. AI systems like ChatorAI are designed to answer, route, qualify, and escalate conversations with more automation built into the operating layer.

Chatbot vs AI revenue system

A chatbot usually handles narrow scripted tasks or simple FAQ deflection. An AI revenue system like ChatorAI is built to manage live customer conversations across support, qualification, follow-up, and conversion workflows.

Helpdesk vs conversation platform

A helpdesk is optimized for tickets, queues, and agent workflows after a support issue is created. A conversation platform keeps the full customer interaction in motion across channels before it becomes only a ticket.

Use this guide when

These are the situations where this documentation page is most useful.

Understanding how tenant, channel, AI context, and billing concepts fit together.

Orienting new operators before they start configuration or implementation work.

Reference this topic in context

These links connect the category, product capability, use case, and integration context that matter most to this page.

Category

What is AI customer support?

Use the category definition to connect the product concepts to the broader operating model.

Read the AI customer support definition

Feature

AI Sales Agent Platform

See how one of the core platform features depends on the tenant, AI context, and workflow concepts documented here.

Explore the AI sales agent platform

Use case

SaaS platform operations

See a use case where tenant state, AI context, and billing lifecycle all matter operationally.

See the SaaS use case

Integration

HubSpot integration

Review an integration that depends on the shared platform concepts described on this page.

Review the HubSpot integration

Frequently Asked Questions

Short answers to the practical questions operators usually have while following this guide.

Ready to put this workflow into production?

Use the documentation as the implementation reference, then validate the workflow in a live trial workspace before rollout.