A support desk your customers never have to leave your site for
A knowledge base on your own domain — Categories, articles and a search box — living at yoursite.com, not on a separate helpdesk tool with its own login and its own bill.
A real ticket inbox — Customers sign in, open a ticket, and reply in a thread. You get an inbox with priorities, assignment and canned replies — not an email chain nobody owns.
AI answers from your articles, not the internet — The chat widget on your site answers strictly from your own knowledge base first, and says so honestly when it can't — no guessing, no made-up policy.
Every resolved ticket can become the next article — One click turns a solved ticket into a draft help article. Publish it, and the next customer with the same question finds it without asking.
The knowledge base is also what your AI chat reads from
Every article you publish joins the corpus your live chat widget searches — the AI answers strictly from it, and says plainly when it can't find a confident answer instead of guessing. Customers can also just search or browse by category the ordinary way; either path lands on the same articles, so you write each answer once. An "open a ticket" button sits on every article for the question a search doesn't settle.
A ticket inbox built for actually running a small team
Yes — a ticket ties to a signed-in customer on your site, so they sign in (or register) first. That's the same customer account area your store or booking pages already use, and it's included free.
No. Turn it on under Settings → Modules & features and start writing — it isn't gated to a particular plan or priced separately. Tickets need no toggle at all; they're available by default.
Not fully yet. Articles store content per language, but the article editor currently writes only your site's default language, so a multilingual help center today means translating articles by hand rather than relying on AI to do it for you.