Support areas

Support tools

Launch support before users arrive.

Turn scattered docs, tickets, releases, screenshots, notes, and repeated replies into widget help, hosted docs, tickets, feedback, changelog support, and reviewed answers.

Create workspace

Demo Install Use Cases

Resources

Setup guides

Evaluate & trust

Prepare your support inputs before setup.

Use the pre-onboarding package to organize scattered docs, tickets, FAQs, screenshots, recordings, release notes, and repeated replies.

Resource

Safe Page Context

Use page hints that help support answers without sending tenant IDs, user IDs, account records, tokens, or billing data.

Reading time

5 min read

Updated

2026-06-02

Action

Read developer doc

Read developer doc Create workspace

Quick answer

Safe context describes the page. It does not identify the tenant, user, account, payment record, or private customer payload.

Allowed context

The widget can use stable product-page hints such as path, title, feature, workflow, role, and locale. These values help answer selection without turning browser context into account identity.

path: current app path without secret query values
title: readable page name
feature or workflow: billing, onboarding, settings, release, or support area
role and locale: broad support hints only

Blocked context

Do not send tenant IDs, store IDs, user IDs, emails, phone numbers, or names.
Do not send tokens, cookies, JWTs, service keys, secrets, or payment data.
Do not send raw customer records or private account metadata.

Screenshot boundary

Screenshots are explicit user input. AnswerLattice public copy should keep that boundary clear: upload or paste is allowed when the user chooses it; automatic capture is not part of the public claim.