Troubleshooting

The guide does not appear

Verify the current hostname is on the tenant domain allowlist.
Confirm the DNS TXT verification step succeeded for that hostname.
Check that the boot script has the correct data-app-id and data-gp-api.
If your site uses strict CSP, pass the nonce with both nonce and data-nonce.

Confirm the worker /boot request succeeds.
If GP_KILLSWITCH=true is active, the embed silently no-ops by design.
If consent mode is opt-in and the visitor has not accepted, the guide will not collect or respond.

Voice is optional and can be disabled at the tenant level.
On touch devices the runtime uses the bubble fallback instead of the desktop cursor metaphor.
If hosted voice providers are unavailable in local development, the worker degrades to the internal mock voice.

Puntego is honest about scope. In v1, these surfaces are outside the runtime’s full line of sight:

Canvas or WebGL-heavy apps: Figma, Miro, Google Sheets, game UIs, and other canvas-first products push the runtime into degraded mode because the underlying controls are not available as normal DOM targets.
Cross-origin iframes: Stripe Elements, Intercom widgets, embedded YouTube or Maps, reCAPTCHA, and any other third-party iframe are invisible to the guide because of the browser same-origin policy.
Closed shadow DOM: if a component hides its internals inside closed shadow DOM, the guide cannot inventory or point at those internal controls.
Auth-walled content the visitor cannot see: the runtime only guides the current surface in front of the visitor. It cannot see content the visitor has not loaded or is not allowed to access.

Prefer real DOM controls for the critical path you want Puntego to guide.
Keep payment fields, support widgets, and CAPTCHA flows outside the “point here next” promise.
If your product relies on a canvas-first experience, treat Puntego as a typed assistant first and a pointing guide second until the surface is redesigned.