I built my app with AI. Do I still need AnswerLattice?
Yes, if your product is live, in beta, or close to launch. AI can help you build faster, but users still need support that matches your product pages and stays approved.
FAQ
Plain answers about setup, source intake, widget support, hosted help, approved answers, fallback tickets, pricing, review tools, and data handling.
Use these when deciding whether AnswerLattice fits your product and what to prepare first.
Yes, if your product is live, in beta, or close to launch. AI can help you build faster, but users still need support that matches your product pages and stays approved.
You can, but generic chat is not the same as a support layer. AnswerLattice turns scattered product knowledge into structured widget help, hosted help, tickets, feedback, changelog support, approved answers, and support-gap review.
Start with what you already have scattered around the product: FAQs, tickets, setup notes, release notes, screenshots, recordings, owner notes, and recurring support questions. AnswerLattice helps turn that material into reviewed support knowledge.
Yes. Knowledge Intake can discover bounded public page candidates, import only the pages you select, and accept supported files or pasted product material. It does not crawl your whole site or log into private app areas.
Yes. Owners can add screenshots/images or short support recordings when visual walkthroughs help. OCR and transcription are capped, support-credit logged, and stored as extracted support text for review rather than raw media files.
Provider-backed fallback answers, full-runtime answer tests, the source-backed first-ten starter-answer run, screenshot OCR, and short recording transcription use support credits. Approved or cached widget answers, deterministic checks, draft review, selected text import, publishing infrastructure, and public help browsing do not use credits.
No. Intake creates review drafts for help articles, FAQs, product pages, changelog entries, and approved answers. Owners choose what to accept and publish; official support answers still require owner approval.
No. Approved answers are served first. If coverage is missing, fallback is marked and repeated misses go to review.
Not for idea-only prototypes. AnswerLattice is for working SaaS apps that are live, in beta, or close to launch and have starter support knowledge to review.
How AnswerLattice differs from generic chat, helpdesks, automatic screenshots, and unscoped context.
No. AnswerLattice can assist with user support, but the product is much broader than a chat box: in-app help, hosted help, FAQs, changelog, tickets, feedback, approved answers, and owner review.
No. AnswerLattice is the support knowledge layer behind your help center, widget, tickets, and changelog. Tickets are fallback and signal sources, not the center of the product.
An approved answer is a reviewed support answer tied to documented product details such as a feature, workflow, plan, role, release, state, or product area.
The launch path is built around a short setup: add product details, import starter knowledge, choose important product pages, install the widget, and verify the first answers from the activation dashboard.
Yes. AnswerLattice supports workspace members, AnswerLattice-specific roles, custom permissions, owner-managed passcode reset, and force sign-out. These controls live inside the AnswerLattice workspace.
Your product can pass safe route, page, feature, workflow, role, and plan hints to the AnswerLattice widget. AnswerLattice uses those hints to prefer approved support content mapped to the page where the user needs help.
Yes. Users can upload or paste a screenshot with their question when visual context helps. Widget images are bounded by file type and size and are not stored as persistent files.
No. AnswerLattice does not automatically capture the host app screen or scrape the DOM. Runtime visual context stays explicit and user-initiated.
No. Approved answers are served first. If coverage is missing, fallback can help, but repeated fallback becomes a support gap for owner review.
What happens when coverage is missing and how repeated questions become review work.
AnswerLattice can use fallback, record the missing answer, and turn repeated gaps into draft answers for review. Those drafts require human approval before becoming official support.
Yes. Widget settings include blocked routes and allowed origins so customers can control where the widget appears.
Yes. Hosted Help can publish reviewed docs, FAQs, and changelog content on support domains such as help.yourapp.com. It does not expose authenticated tickets, chat history, or workspace internals.
Yes. AnswerLattice is designed for branded help domains such as help.yourapp.com, docs.yourapp.com, or support.yourapp.com so customer-facing support feels native to your product.
Tickets can include capped and sanitized recent browser context when the user creates the ticket. This helps owners understand broken screens faster while keeping the context tied to the reported issue.
Product owners can manage FAQs and custom owner answers directly. AnswerLattice can also generate article-backed FAQ suggestions during the knowledge workflow, but they stay reviewable instead of publishing automatically.
Yes. Owners can write exact repeated questions and answers, attach articles, tags, and page context, publish them, and let AnswerLattice use them after approved answers and before fallback when the user question matches.
Yes. AnswerLattice can complement ticket tools as the reviewed support-knowledge layer. Broad helpdesk integrations are not currently offered.
Support Board is a private owner and staff workboard for selected support gaps, internal notes, status history, and draft-answer handoff. It helps owners track follow-up without turning AnswerLattice into a project-management tool.
Users can submit ratings, product-area feedback, feature requests, and suggestions from the Help Center. Owners review those items privately and can move useful feedback into Support Board or draft-answer review. AnswerLattice is not a public voting board.
No. Tickets and signals already have their own screens. Support Board is manual-first by default; ticket/signal sync and nightly board preparation stay controlled rollout paths so work is not duplicated or made unnecessarily expensive.
Yes. AnswerLattice supports Slack and email notifications for nightly support-review summaries, coverage drops, repeated workflow failures, and test delivery. Jira, Linear, GitHub, Notion, and custom webhook destinations are not currently offered.
How notifications, runtime context, release review, pricing, and workspace identity stay controlled.
No. Proactive help is configured for specific product pages. The widget only requests or shows configured prompts when the workspace has active triggers. Temporary known-issue notices use the same page-aware runtime and expire or stop after resolution.
No. Runtime paths use compact summaries, cache freshness checks, and approved context. Source data remains inside AnswerLattice. Public bundles do not include drafts, tickets, audit logs, API keys, or private workspace internals.
MCP and agent-context tools stay rollout-gated. AnswerLattice can prepare approved context for authenticated server paths, but public pages do not promise general MCP access or agent-side knowledge writes.
Versioned changelogs can be tied to changed product areas. Before activation, release impact shows directly linked approved answers and current linked Answer Tests for owner review. If those inputs change, the stale preview must be refreshed.
Start with existing docs, setup guides, FAQs, changelogs, and the top recurring support questions. AnswerLattice prepares candidates and drafts for review instead of forcing manual modeling first.
No. Setup starts on a paid plan. Your billing country determines whether checkout uses INR or USD, and plan changes, invoices, credit notes, and support-credit top-ups stay in AnswerLattice Billing. Usage limits protect infrastructure without charging for normal help browsing or approved answers.
No. Widget page context helps AnswerLattice choose relevant support. Workspace identity is resolved through AnswerLattice workspace, domain, widget key, and authenticated scope controls.
Yes. Save critical questions with expected source, answer, fallback behavior, or wording. Canonical-only checks are deterministic; full-runtime checks are capped and use support credits only when they reach provider fallback. Release checks run only linked cases.
No. A failed test can prepare a prior audited answer version as a rollback draft for review. The live answer is not overwritten, and applying accepted content remains a separate owner-approved edit.
No. Known Issue Mode shows an approved, contextual widget notice with an active window and optional HTTPS status link. Permanent approved answers remain unchanged.
AnswerLattice discards verified visitor context such as signed-only identity, plan, role, and locale claims. Safe page context can still provide generic page-aware support, and workspace scope always comes from the widget key.
Nothing in your support data directly. Daily Brief is the read-only opening view inside Support Assistant. It shows up to four focused current decisions from support summaries, or a clear quiet state when the available evidence needs no action, then links the owner to the correct review screen.
Knowledge Map is the owner view of reviewed product relationships, approved-answer coverage, drift, and review state. It uses a bounded relationship summary and does not expose a raw graph or become a diagram editor.
No. Public article navigation is built from safe published headings. Private relationship, source, approved-answer, ticket, and review records do not enter the public payload.
Yes, with export permission. The bounded JSON package includes approved product structure, articles, FAQs, releases, changelog entries, and approved answers. It excludes tickets, conversations, visitor details, secrets, keys, credentials, and raw audit logs.