Chateor
Bring website chat, knowledge-based AI answers, and your support team into one shared workspace—without losing the customer’s context.
Customer questions can begin in a website widget or in a product connected through the Client API. Each conversation keeps its messages, channel, customer context, ownership, and status together so the next person—or the AI agent—can continue without asking the customer to repeat the story.
Teams use Chateor to receive requests, organize a shared queue, assign responsibility, preserve conversation history, and automate repeatable answers. It works alongside your CRM, account system, ecommerce platform, or internal tools rather than trying to replace them.
Add a support widget to your website with a JavaScript snippet. Configure language, colors, display mode, and optional anonymous usage statistics. Pass order numbers, customer identifiers, product names, plan details, or other context into a new conversation so the team starts with useful information.
Connect knowledge sources to a channel and choose how AI should participate. It can help prepare replies or automatically answer suitable questions. When a request needs judgment, access, or a human decision, the conversation can move to an operator with the existing history and context intact.
Operators work from a shared conversation workspace with clear statuses and responsibility. Roles and permissions control access to channels, users, knowledge, billing, settings, and audit information. Notifications help the right people see new requests, assigned conversations, and AI handoffs.
Use the Client API to create conversations and send customer messages from your own application, account area, CRM, or service portal. Signed webhooks deliver operator replies, AI messages, and status changes back to your system. Separate API keys can be revoked without affecting the rest of the workspace.
Install a ready-made customer support widget. Use JavaScript to control its behavior and pass useful page or customer context into the conversation. Chateor keeps the public chat connected to the team that owns the answer. It does not become an isolated browser interaction.
Use the server-side Client API when support needs to live inside an account area, application, CRM, or service portal. Customers can keep using your product. Signed webhooks return operator replies, AI messages, and status changes to the workflow that needs them.
Organize channels, shared conversations, statuses, responsible agents, roles, permissions, knowledge, and AI handoffs in one workspace. Ownership stays visible. The team does not have to replace the CRM, ecommerce platform, billing system, or other tools that already hold business data.
Chateor publishes information about workspace access, account protection, API credentials, signed webhooks, AI controls, privacy, browser storage, and shared responsibility. Teams can review those boundaries before deployment. They can use the support widget to ask product, integration, security, or commercial questions.
Create a workspace, connect a channel, and choose where AI helps and where people take over.