Developer Doc

Verify the widget before you call support live.

The install is not finished when the script tag exists. Verify script loading, dashboard-owned route rules, safe context, and blocked surfaces.

Script

Loaded once from the v1 URL

Origin

Allowed in the dashboard

Routes

Blocked routes stay blocked

Implementation notes

Keep the install small and verifiable.

AnswerLattice developer docs focus on the v1 widget contract, dashboard-owned route settings, safe browser context, and verification.

Script checks

Install the widget once in the app shell.

  • Use the stable v1 script URL.
  • Keep the widget key in a public client-safe environment variable where possible.
  • Avoid per-page duplicate script tags.

Runtime checks

Confirm runtime state from the product and the AnswerLattice dashboard.

  • Open the product on an allowed origin.
  • Navigate between app pages and confirm context updates.
  • Open blocked routes and confirm the widget is absent or hidden.
  • Return to AnswerLattice and check the latest runtime status.

Failure checks

The widget should fail closed when install values are missing or blocked.

  • Missing widget key should not expose private data.
  • Blocked routes should not mount support UI.
  • Forbidden context fields should not be sent.