Skip to main content
Puntego reads its settings from the workspace configuration returned by /boot, so you change the guide’s behavior from the dashboard without editing your site or redeploying.

Appearance

Set the guide’s look from Dashboard → Settings → Brand → Appearance: whether it follows your site’s colour or your brand colour, a separate button colour, a launcher logo and a light, dark or automatic theme. The preview beside those settings is the real widget on a sample page, dressed in your draft. Like every Brand change, they stay in the draft until you publish; then new page loads pick them up. The choices on your install (below) still win on the pages that use them.

Colour: your site’s, by default

The guide wears your site’s primary colour without any setup. When it starts, it reads the colour of your primary buttons (for example .btn-primary, [data-variant="primary"] or the most common coloured button on the page), your --primary/--brand CSS variables, your theme-color meta tag or your link colour. It reads only computed colours, never text or form values. If your page gives no colour, the guide uses a neutral blue. The accent is resolved in this order, first match wins:
  1. appearance.accent from Puntego.init() or <PuntegoProvider>, or data-accent on the script tag;
  2. the --puntego-accent CSS property on your page;
  3. the brand colour, when an operator chose Use a brand color in Dashboard → Settings → Brand → Appearance (before that choice existed, any brand colour other than the provisioning defaults);
  4. your page’s primary colour, detected at runtime;
  5. neutral blue (#2563EB).
Set accent: 'auto' to skip step 3 and always follow the page. Contrast is handled for you. Buttons use an action colour derived from the accent: your exact colour when white text on it reaches 4.5:1, otherwise the same hue made darker (or lighter in dark theme) until the label clears WCAG 2.2 AA. Focus rings and the launcher mark stand at least 3:1 against every surface of the guide. A button colour set in Brand → Appearance drives the buttons (with the same contrast derivation); a launcher logo set there (HTTPS only) replaces the pointer mark in the launcher button. Questions that ask the visitor for approval or permission (approving a change, allowing page context or the microphone, confirming an important click) never use the accent: their button is neutral ink, dark in the light theme and light in the dark one, so a red or orange brand never makes a question look like an error.

Theme

theme: 'auto' (the default, unless Brand → Appearance picks Light or Dark) follows your page live, with no reload: the colour your page paints behind the guide, a dark/light class or data-theme attribute on <html> or <body>, and your page’s color-scheme together with the visitor’s system preference. Pass 'light' or 'dark' to pin the guide to one theme; a theme set on the install always wins over the Brand setting.

Font

The guide uses your visitor’s system font by default (system-ui, San Francisco, Segoe UI, Roboto and so on): it loads instantly and reads well on any site. In Dashboard → Settings → Brand → Appearance → Font, Use my site’s font makes the guide use the font your page’s text is set in. The font option on your install and the --puntego-font-family CSS property (below) still win on the pages that set them.

Highlight style

How the guide marks things on your pages (outlines, dashed areas, arrows, numbers and notes) is set in Dashboard → Settings → Brand → Appearance → Highlight style. Clean, the default, draws crisp lines in your accent colour; Hand-drawn sketches the same marks, like notes on a screenshot. Only the stroke changes: every mark stays attached to its element as the page scrolls or changes, keeps the same contrast in light and dark themes, is announced once to screen readers, and appears without animation for visitors who ask for reduced motion.

Launcher

Dashboard → Settings → Brand → Appearance → Launcher sets how the launcher looks and how it first appears on a page. These are Brand settings, not install options, and like every Brand change they reach visitors when you publish.
  • Launcher style: Ink, the default (dark on light pages, light on dark ones), Brand color (your brand colour, with text that stays readable on it) or Light.
  • Entrance: Takeoff, the default (the cursor leaves the launcher, flies an arc, waves and comes back), Edge light, Subtle, Greeting, Unfold, Stroke, Glint, Glance, Converge or None. An entrance lasts a few seconds at most, stops as soon as the visitor interacts, never takes focus, never plays in the same page load as the first-run moment, and becomes a short fade for visitors who ask for reduced motion. On touch screens, where the cursor does not fly, Takeoff plays as Greeting.
  • How often: Smart, the default (up to 3 times, at least a day apart, until the visitor first opens the guide), First visit, Every session or Every page load (never when moving between pages of a web app). On visits where the full entrance does not play, the launcher fades in. Smart and Every session remember what already played in the visitor’s browser storage.
  • Greeting: the line the Greeting entrance types beside the launcher, up to 60 characters of plain text, written once per visitor language (English, Spanish, Portuguese, French, German and Italian). Your workspace’s default answer language comes first; the others are under Other languages. A visitor reads the version in their language; a language you leave empty uses its default: “I can guide you through this page.”, “Puedo guiarte por esta página.”, “Posso te guiar por esta página.”, “Je peux vous guider sur cette page.”, “Ich kann Sie durch diese Seite führen.” or “Posso guidarti in questa pagina.”.
The preview beside these settings opens on the launcher of a desktop page at full size; Replay entrance plays the entrance again, and Answer switches to a sample answer.

Cursor

Dashboard → Settings → Brand → Character offers six pointers, all of which aim at what the guide shows: Dart (the default), Classic, Needle, Nib, Comet and, under “With personality”, Companion. Workspaces that used one of the retired presets (Halo, Ring, Bracket, Pulse, Whisper) now show Dart, and Arrow became Classic. From the Starter plan you can upload your own logo there instead, and the guide uses it as its cursor and launcher mark. Upload an SVG when you can: it is used as drawn; other images are vectorized first. Every upload passes a content check before visitors see it, and you confirm you have the rights to use the mark.

The appearance option

A later init({ appearance }) replaces the previous value without a reload. Invalid fields are ignored one by one, so a typo never breaks the others. The script tag takes the same values as data-accent, data-theme, data-font and data-radius. In React, pass the same object as a prop; a changed value is applied live:

CSS custom properties and parts

The guide renders in a closed Shadow DOM, so your page CSS cannot reach its internals. Style it through this stable contract instead: Target parts on the guide’s host element, [data-puntego="assistant"]:
The guide mounts directly under <html>, so a property declared on <body> or on an app wrapper does not reach it. The answer card’s footer is not a part: it carries the AI-answer label and, on plans that show it, the “Powered by Puntego” line, and both stay as the guide renders them. A part rule can read the guide’s own tokens: --gp-accent, --gp-accent-strong, --gp-action, --gp-action-hover, --gp-on-action, --gp-focus-ring and --gp-radius-card. Class names inside the guide are not part of the contract and change between releases. If you restyle colours through parts, you own their contrast.

”Powered by Puntego”

On the Free and Starter plans the answer card’s footer carries a small “Powered by Puntego” line; from Growth up it is removed automatically. It follows your current plan, so it comes back if the workspace moves to a plan below Growth. Keep the public install snippet stable. Change runtime behavior through workspace settings, not by rewriting the script tag on every deploy — that keeps your install reviewable and lets non-engineers adjust the guide. See Install for the snippet and its data attributes.

Assistant entry

By default the launcher opens a compact ask bar. A question becomes a pill above one answer card: the answer, its sources behind an “N sources” toggle, up to three follow-up questions and at most one primary next step (for example Got it or Start tour). The card’s footer always says it is an AI answer, and its ⋯ menu holds the controls that do not need to be on screen all the time: copy, try again, “This didn’t help…”, a new conversation, memory and privacy, pointing at something yourself, talking to a person (when enabled) and turning Puntego off. The full conversation is one click away from the question pill. To open the conversation panel directly instead, set data-launcher-entry="panel" on the script tag or pass it at init:
The init option wins over the attribute, and the attribute wins over the default (askbar). The talking cursor (data-launcher-mode="cursor") always opens the panel, and privacy-only or consent-pending sessions always show the panel, because that is where those controls live. Choose how visitors are told about the guide from Dashboard → Settings → Privacy. A same-request legal acknowledgment confirms you have reviewed the notice your visitors will see.
Global Privacy Control opt-out is always honored, independent of region. Consent follows your configured workspace mode — a missing visitor country does not force a stricter mode.
For what is and is not redacted before model and guardrail calls, see Privacy and PII.

Voice

Voice is optional and off until an owner or admin turns it on in Settings → Guide behavior → Voice. While it is off the widget shows no microphone and every voice request is refused. Production requires a configured hosted provider; when credentials are missing, voice stays unavailable and the guide continues in text mode. The internal mock is limited to development and tests. Visitors on your live site can talk to the guide on Growth and higher, within the plan’s monthly voice minutes; with voice overage turned on in Billing, extra minutes are billed in packs up to the cap you choose. On Free and Starter the live site shows no microphone, and you can still try voice yourself in the dashboard Preview and in test mode, on a monthly allowance listed on the pricing page. Visitors hold the microphone in the ask bar to talk, or tap it to start and tap again to stop (Space held on the focused microphone works the same way, Enter toggles it, Escape cancels). Their words appear in the ask bar as they speak and are never sent on their own: the visitor checks them, edits them if needed and sends them like typed text, and the answer is read aloud. Each visitor agrees to a voice notice before their microphone is first used. Puntego does not store the audio; only the text the visitor sends joins the conversation. When the microphone is blocked or unavailable, the widget says so and how to type instead. Speech providers never receive a reusable credential from the visitor’s browser. For OpenAI realtime transcription, Puntego starts each call from its own servers, meters it by its real length against the workspace’s voice allowance, and ends it from the server when the visitor withdraws voice consent, an owner or admin turns voice off, the allowance runs out, or the visitor stops talking. The bubble experience is the cursor launcher’s fallback: on touch-primary or narrow (under 768px) screens, the cursor mode switches to the bubble. The default floating launcher keeps its floating button on those screens.

Feature flags

These environment flags govern rollout at the worker: See Boot errors for the full set of /boot responses.

Observability

Puntego scrubs personally identifiable information from error reports before they leave the app, so you can monitor application errors without exposing visitor data. Roughly 10% of route traces are sampled, and raw request bodies, visitor data, and prompt text are not captured by default. Model traces stay isolated per workspace and redacted at the worker; the dashboard only renders the redacted summaries the worker surfaces. Operator traces never become a second copy of raw visitor data.
Operator note: error reporting is wired through SENTRY_DSN_DASHBOARD (server and edge) and NEXT_PUBLIC_SENTRY_DSN_DASHBOARD (browser). To turn it off, blank both DSNs and redeploy.

Next steps

Install attributes

Set launcher mode, routes, voice, and wake behavior on the script tag.

Privacy and PII

See consent enforcement and exactly what is redacted.

Domains

Allow the origins where the guide may mount.

Security

Review the trust model behind boot, chat, and traces.