Customer support needs one clear route through.

Customer questions often begin in one system and need an answer from another. A visitor writes from a website, an account holder asks inside a product, an operator needs details from a CRM, and an automated answer depends on maintained documentation. The support experience breaks down when each transition starts a new record and the customer has to reconstruct the story.

Chateor is designed to keep that story together. It combines customer chat, a shared queue, conversation statuses, operator ownership, roles, AI assistance, an automatic AI agent, knowledge bases, analytics, the Client API, and webhooks. The goal is not to make every business process happen inside the support platform. It is to give each question a clear route to the right answer or responsible person.

• Website and product conversations enter defined channels.
• Messages, context, status, and ownership remain connected.
• Teams choose where AI helps and where people decide.
• APIs and webhooks connect work that belongs in another system.

Chateor is not intended to replace a company’s CRM. The CRM can remain the primary source for customers, contracts, sales, and orders. An ecommerce platform can continue to own purchases and fulfillment. An account system can continue to control subscriptions and access. Chateor manages the support conversation and provides documented paths for exchanging the context, messages, replies, and status events that connect those systems.

This boundary keeps the support layer focused. A website team can install the widget without building a custom conversation interface. A product team can use the server-side Client API when support must live inside an existing application. Operators can work from one workspace, while signed webhooks return replies and state changes to the external workflow that needs them.

• The website widget is a ready-made public support surface.
• The Client API supports custom server-side experiences.
• Signed webhooks return support events to external products.

A shared conversation is useful when responsibility is visible. Chateor uses workspaces, channels, roles, permissions, statuses, and responsible agents to organize how a team handles requests. Workspace owners decide who can administer settings, manage users, access conversations, connect knowledge, or control integrations. Audit history and conversation records support operational review by authorized people.

Security is shared between the platform and its customers. Chateor provides account, workspace, integration, and conversation controls; customers manage their users, website deployment, source material, credentials, retention choices, and the content they choose to process. Strong unique passwords, two-factor authentication, least-privilege access, secure secret storage, signed webhook verification, and timely removal of former users all remain part of a sound deployment.

• Roles and permissions separate administrative responsibilities.
• API keys can be managed independently from user passwords.
• Knowledge and AI participation are configured per support route.
• Human review remains essential for high-impact decisions.

Questions about Chateor, product fit, integrations, data handling, or security can be sent through the support widget on chateor.com. The current product material does not publish fixed pricing or package composition, so commercial terms should be discussed according to the size of the team, expected conversation volume, required functions, and integration needs rather than inferred from undocumented assumptions.

Technical teams can begin with the website widget, Widget JavaScript API, or Client API documentation. Organizations evaluating security and data practices can review the public Security page, Privacy Policy, Cookie Notice, and Terms of Use before creating a workspace.

• Product and commercial questions: use the support widget on chateor.com.
• Security concerns: follow the reporting guidance on the Security page.
• Technical implementation: use the public documentation linked from this site.