How it works

How Anchor works

How does this work? Anchor is a branded assistant that answers from a document portal — your organisation library plus this site’s own library. It does not search the open web.

A visitor asks a question in the website messenger. Anchor retrieves matching passages from pages, PDFs, videos, topics, and local documents you added. Every grounded answer cites those passages. When nothing in the library matches, it refuses instead of guessing.

Local documents live in the database. This running app can also ingest its own origin so the assistant reads the live pages. Other private hosts stay blocked.

The sample chat on this website is the same widget customers embed. It is connected to the Anchor website site library, not to every affiliate at once.

Organisation and site libraries

Retrieval is scoped with organisation id and either this site id or organisation-level rows where site id is null. Shared policies belong in the organisation library. Affiliate or brand pages belong on that site only.

A visitor on one property does not receive another property’s pages. Widgets never union every site into one public brain.

The document portal in the app is the organisation library. Open a site to add that property’s library. Both are used together when someone chats on that site.

How the widget is installed

The customer embed is a script tag: widget.js with data-widget-key set to that site’s widget key. Paste it before the closing body tag. The widget checks the page Origin against the site allowlist. Chat from the Anchor app origin is also allowed.

Allowed origins must include the host that loads the messenger. Pause a site to hide the launcher; conversations stay in Inbox.

Plans and isolation

How much does it cost? Pricing is monthly in US dollars. Starter is $49 per month for one site and 1,000 chats. Growth is $199 per month for five sites and 10,000 chats. Scale is $599 per month for twenty-five sites and 50,000 chats. Affiliate networks buy more sites, not a second product.

Plans: Starter is one site. Growth is five sites. Scale is twenty-five sites. Monthly chat caps apply per organisation. Plan and subscription status are written only by the Stripe webhook, not from the dashboard.

Handover lets a visitor ask for a person. That request is stored on the conversation for the same organisation, site, and visitor. NPS scores are stored the same way.

Do not tell visitors to paste API keys or database passwords into the chat.