Route, feature, workflow, role, and plan hints guide the answer.
In-app support widget
In-app support widget for AI-built SaaS.
Install one widget that uses safe page context, optional user-attached screenshots, approved answers, owner FAQ answers, changelog entries, and fallback signals so users get help related to the screen they are on.
Approved answers and owner answers before fallback.
Screenshots are user-attached; context never decides workspace identity.
Question flow
Why was I charged again?
AnswerLattice turns a generic support gap into a reviewed answer that matches the current product page.
Problem
A generic widget sees the question but misses the screen. Billing, onboarding, team settings, and release pages need different answers, and visual errors sometimes need a screenshot the user deliberately attaches.
Generic answer
Please check your billing settings or contact support.
AnswerLattice answer
You are on Billing. Your plan renews monthly, failed invoice retries follow the configured retry window, and payment can be updated from Settings -> Billing.
Owner review
The widget serves approved answers first, then matching published owner answers. Missing coverage is marked as fallback and repeated gaps become review work. Screenshots are explicit user input, not automatic runtime capture.
Setup path
Reviewed support stays the authority.
The setup path keeps source material, page context, and owner approval connected before answers become official.
01 / Support setup
Start with the support material you already have.
Docs, product pages, FAQ notes, tickets, and repeated replies become a reviewable setup path instead of scattered founder work.
Create an AnswerLattice workspace.
Create the support workspace and connect it to the product.
Add billing, onboarding, settings, or release surfaces.
Keep this setup step tied to reviewed support material and product pages.
Install the widget script.
Keep this setup step tied to reviewed support material and product pages.
Pass safe route and workflow context.
Keep this setup step tied to reviewed support material and product pages.
Let users attach screenshots only when visual context helps.
Keep this setup step tied to reviewed support material and product pages.
Review fallback gaps and approve better answers.
Use missing answers and feedback to improve the next support pass.
Explore AnswerLattice
The same loop across setup, widget, hosted help, tickets, and review.
Each product area has a dedicated page so founders, support teams, product teams, and engineers can evaluate the part they care about first.
Set up support
Create your workspace, add team access, teach AnswerLattice from starter sources, and map the pages where users need help.
In-app help widget
Install one widget, pass safe page hints, accept explicit screenshot context, control allowed domains, and answer users inside your app.
Help center and tickets
Publish docs, FAQs, custom owner answers, and release notes; manage fallback tickets, feedback, ratings, and feature requests from one connected support layer.
Review approved answers
Review drafts, repeated misses, stale answers, coverage, and readiness before support becomes official.
Turn this support gap into a reviewed AnswerLattice setup.
Start with the demo, then prepare source material so the first workspace has pages, docs, FAQs, and owner-approved answers to review.