Site Chat is the Anhora widget on your storefront. Visitors ask on the page they are already on. Answers come from the knowledge you connect, in the voice you set — not from a generic chatbot overlay.
Site Chat is the visitor-facing assistant that lives on your site. One embed, on a domain you verify. Greeting, colors, and rules come from your project — so the conversation feels like the store, not like a third-party bubble. It is the first surface most shoppers meet: product questions, shipping and returns, “do you have this in stock,” without sending them to a search box or a ticket form. It is not a helpdesk you log into. It is not the Telegram bot, and it is not the Slack inbox. Those are extra channels you can attach to the same assistant later.
The widget sits in your layout and follows the brand you configure. Shoppers should recognize the store, not a bolted-on chat vendor.
Products, documents, FAQs, and site pages you connect are the source of truth. The assistant is not free to invent SKUs, prices, or policies you never published.
A Site Chat goes live after you verify the hostname. Anhora will not treat a random Origin header as proof that the widget belongs on a site.
A compact chat on the storefront. Questions about what you sell, how you ship, and what happens after checkout — answered from the sources you chose to share. When the assistant should not guess, it stays inside that knowledge. When a person should take over, the thread can move to your team inbox. The shopper keeps talking in the widget; they do not have to know whether someone replies from Slack.
Pasting the embed does not import your CMS. Knowledge is a separate connection — Payload, WordPress, or a push from your own backend. The install guides cover the snippet and those sync paths. Telegram is optional: the same Site Chat can talk to shoppers in Telegram after you enable the channel. That setup lives on the Telegram page, not in the website snippet. If the team should answer live, connect Slack as the inbox — or a Telegram forum if that is how you work.
HTML snippet, Payload, WordPress, Next.js, and NestJS — pick the path that matches your stack.
Welcome text, tone, and business rules update from the dashboard. You do not redeploy the storefront every time the assistant should say something differently.
Knowledge emerging from light
Private Beta is application-only. Tell us about the site you want to verify and we will follow up.
