Setting Gerry up

The panel's Setup screen is five steps, in order, and each one has to finish before the next means anything. This walks through the demo tenant doing exactly that.

1. Your search page

The address of the page where your visitors filter — the one with the results and the filter panel on it. Your key is already allowed on that domain from when your tenant was created; this step just tells Gerry where to look.

2. What Gerry found

Gerry reads that page and drafts a site map from it: the filters it can see, how each one is expressed in the address, how to read the count and the rows. Anything wrong is yours to correct afterwards, in Site map reference — either the form or the raw JSON.

3. Does it work on your site

Every filter the map declares is tried against your live site, the same way the nightly check does (see Checks): does the search page answer, does each filter's URL answer, can the count and the rows actually be read off the page. This is the same check you can re-run any time a filter starts misbehaving.

Setup steps 1 to 3 in the panel: search page address, what Gerry found, and the results of checking every filter against the live site — Steps 1–3 on the demo tenant. Step 3 found one failing check out of eight — a facet group it could not match — while the search page, the filters, the count and the rows all read clean.

4. Put it on your site

One line, with your key already in it. Paste it once, before the closing </body> tag, on every page where Gerry should appear. Nothing else on the site changes, now or later. The same line lives on Site & key below, in case you need it again.

5. Your first visitor

This step waits on something outside the panel: an actual visitor clicking the orb. The panel polls quietly while it is open and lights up the moment your script has been seen live. From here, conversations start showing up in Conversations.

Setup steps 3 to 5: the check detail list, the install snippet with the site's key in it, and confirmation that the first visitor has been seen — Steps 3–5. Step 4 is the exact script tag; step 5 turns green the moment the widget has run on the live site at least once.

Everything else in the panel

Setup gets Gerry talking. The rest of the panel is where you keep it dialed in.

Site & key	The public key, the install snippet again, and the allowed-origin list — the actual protection behind a key that is otherwise public. Add every hostname Gerry should run on, including staging.
Assistant	The assistant's name, the site's name, its persona and domain in your own words, the first message, the spoken language, which other languages it also answers in, the greeting (language step, ask-for-a-name) and its voice per language. See Languages and the greeting.
Appearance	How the widget looks and where it sits, with a live preview beside the form. See What Gerry shows on the page.
Site map	The same map Setup drafted, editable as a form or as raw JSON. See Site map reference.
Checks	The nightly run's history, expandable per item. See Checks.
Conversations	Every conversation: when it started, how long it ran, the visitor's name if they gave one, the language spoken, the page it happened on and how it ended.
Insights	What visitors asked for and what Gerry did about it, across the last 30 days. See Insights.
Leads	Requests a visitor asked Gerry to hand over, with what they filled in.
Plan	This month's usage against the plan, and the plan catalogue. See Plans & limits.

The Site and key screen: the public key, the install snippet, and the allowed-origin list — Site & key. The key is public on purpose — the allowed-origin list underneath it is what actually protects a tenant's minutes.

The Assistant screen: assistant's name, site name, persona and domain text area, first message, and spoken language — Assistant. The persona is a short paragraph in your own words — what the site sells, where to steer the visitor, what tone to take.

The Conversations screen: a table of past conversations with their start time, duration, visitor name if given, spoken language, page and how each ended — Conversations on the demo tenant. Most visitors here spoke Turkish; two gave their name because `askName` is on for this tenant.

← How it works Site map reference →

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