Answer common questions
Resolve supported product, pricing, policy, setup, and process questions.
Give visitors fast answers grounded in current Product, Blog, and Knowledge sources. Keep citations visible, decline unsupported questions, and hand off with context when human help is needed.

The assistant should answer only within website support scope and decline or escalate when approved evidence is missing.
Resolve supported product, pricing, policy, setup, and process questions.
Retrieve fresh, public, site-scoped evidence and show source context.
Escalate uncertainty, sensitive requests, or visitor preference with context attached.
A scoped public support assistant, not a general-purpose AI chat box embedded on a website.
Provide a site-aware conversation entry point that follows tenant brand and locale.
Generate responses from approved evidence and preserve citations.
Search, review, assign, reply, hand off, close, export, and delete conversations.
Escalate based on uncertainty, question type, visitor request, or workspace rules.
Use a minimal safe CRM projection without exposing full private notes.
Respect the current locale and retrieve the correct site-scoped evidence.
Resolve context, retrieve fresh evidence, stream a scoped answer, and preserve the conversation for review.
Identify site, locale, conversation, safe customer context, access, limits, and credits.
Search only current public sources permitted for the site.
Stream a cited response or escalate when the assistant should not answer.
Start with frequent, well-documented questions and expand only when knowledge and handoff are reliable.
Answer approved questions about features, specifications, plans, and next steps.
Resolve common account, policy, setup, billing, and troubleshooting questions.
Collect visitor details and intent for a useful follow-up.
Serve global visitors in the selected locale with the correct evidence.
The assistant must not become a route to unrelated AI work, private data, other tenants, hidden provider details, or unsupported claims.
The planned assistant retrieves current, approved, site-scoped Product, Blog, and Knowledge sources.
Yes. Human handoff is a core part of the design.
The planned flow can collect approved contact fields and link the conversation to CRM when available.
It is in development as a credit-using Pro capability.
Continue with the most relevant parts of the Cogo Site workflow.
We use cookies
We use cookies to enhance your browsing experience and analyze site traffic. By clicking 'Accept', you consent to our use of cookies. Learn more about our cookie policy