What Gerry can't do (yet)

The honest page. Everything below is a real limit today, not a hedge — better you learn it here than from a support conversation.

It answers from the page, not from your whole site

Gerry reads what a page marks for it — a site map's own selectors and the structured data on the results page it's looking at, or, in code mode, whatever context() returns and elements marked data-katman-context (see Security & privacy, rule 5). There is no site-wide knowledge search: Gerry can't answer a question whose answer lives on a different page than the one it's currently looking at — a shipping policy on /help, a spec sheet on a different product's page — unless that page's own content is what's marked or on screen. It talks about the catalogue in front of it, not your whole site.

A site whose results are drawn by its own JavaScript falls back to a page load

Soft navigation (see How a filter is applied) only works when a filtered page's raw HTML actually contains the results. A single-page app, or any list your own script draws in after the page loads, has nothing in its fetched HTML to swap — a map for a site like that declares navigation: "reload", and Gerry falls back to the old behaviour: a real page load, which ends the call. The first filter is the last thing said in that conversation; the visitor has to click Gerry again afterward.

Three languages

English, Turkish and German — see Languages and the greeting. A fourth language is a code change on our side today, not a panel setting.

No phone, no chat window

Gerry is a voice widget embedded on a web page — there is no phone number to call and no text chat interface. If a visitor wants to type instead of talk, or call in from a phone, that's not something Gerry does today.

Questions: hello@heygerry.io. These pages describe what is built today; nothing here is a promise about what is not.