Relay Dashboard

Basics

Site nameWidget enabled

Website lock

The embed key only works on these origins. Add one per line (include https://).

Allowed originsAllowed URL patterns (optional)

Use * as wildcard. Leave empty to allow all paths on allowed origins (unless landing-page-only is enabled below).

Embed mode

Choose how Relay appears on your site — chat widget, text highlighter, or both.

Chat widgetBottom chat bar for open-ended questions.Text highlighterHighlight any text → Ask Konsole for summarize, explain, translate, or extract.BothEnable the chat widget and the text highlighter together.

Widget layout

Choose how the chat bar appears on landing pages vs inner pages. Landing URLs default to each allowed origin homepage when patterns are empty.

Landing pages

Floating search barCentered floating search dock — best for landing and hero pages.Footer barFull-width condensed footer bar — best for inner app and content pages.

Inner pages

Floating search barCentered floating search dock — best for landing and hero pages.Footer barFull-width condensed footer bar — best for inner app and content pages.

Dock position

LeftDock anchored to the bottom-left corner.CenterDock centered at the bottom of the page.RightDock anchored to the bottom-right corner.

Landing page URL patterns

One per line. Pages matching these patterns use the landing layout above; all other allowed pages use the inner layout. Leave empty to treat each origin homepage as a landing page.

Widget behavior

Control where the widget loads and whether it captures the screen for AI analysis.

Landing pages onlyBlock internal pages (dashboard, app routes). Widget only appears on your public landing URLs.Landing URL patterns

One per line. Leave empty to allow only each origin homepage (e.g. https://acme.com/).

Screenshot analysisOn dashboard or data-heavy pages, capture a screen snapshot and send it to the vision model so answers cite real numbers and tables.Off-topic redirect to KonsoleWhen visitors ask about unrelated topics, decline to answer and offer a button to continue on Konsole for open-ended, multi-modal chat.Verify email & phone in chatWhen visitors share contact details, check format (typos like gmial.com, incomplete numbers) and ask them to fix invalid entries before saving to leads.Auto-detect booking links on pageScan the visitor's page for Calendly, HubSpot, BookFlow, and other schedulers. Turn off to use only the default booking URL below.Offer manual booking fallbackWhen sharing a booking link, also offer: "Alternatively, share your name and phone number and I'll book it for you."Default booking URL

Calendly, HubSpot meetings, or Google Calendar link. Used when auto-detect finds nothing on the page, or as a fallback when auto-detect is off.

Advanced

Premium capabilities for data-heavy pages. Available on Growth plans and above.

Data InsightsWhen answers involve metrics, counts, or comparisons, the assistant renders colorful inline charts and tables in the chat — not just plain text.

Widget appearance

GreetingPrimary color

Auto-match site brandingReads theme-color, CSS variables (--primary, --brand), button colors, and body font from the host page. Primary color below is the fallback when this is off or nothing is detected.Konsole lander URL

Where "Powered by Konsole" links to.

AI persona

Controls how the assistant behaves. It reads the current page content to answer questions.

Persona presetModel (optional)

Server uses RELAY_LLM_PROVIDER_ORDER (default openai, then konsole). Set OPENAI_API_KEY or KONSOLE_API_KEY on relay-api. Voice mic uses RELAY_STT_PROVIDER_ORDER (default sarvam, elevenlabs, whisper) — set SARVAM_API_KEY, ELEVENLABS_API_KEY, or OPENAI_API_KEY on relay-api.

Konsole

Settings