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
Questions founders ask before adding AnswerLattice.
Plain answers about setup, knowledge intake, team access, in-app help, hosted help, approved answers, Support Board, owner answers, screenshots, pricing, data handling, and fallback tickets.
Setup, fit, and source intake
Use these when deciding whether AnswerLattice fits your product and what to prepare first.
Can I use ChatGPT or a normal chatbot instead?
You can, but generic chat is not the same as a support layer. AnswerLattice connects the widget, hosted help, tickets, feedback, changelog, approved answers, and support gaps.
What if I do not have documentation yet?
Start with FAQs, setup notes, release notes, and recurring support questions. AnswerLattice helps turn that material into reviewed support knowledge.
Can AnswerLattice import my website or docs?
Yes. Knowledge Intake can discover bounded public page candidates, import only the pages you select, and accept supported files or pasted source material. It does not crawl your whole site or log into private app areas.
Can I upload screenshots or recordings during intake?
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.
Do imports use support credits?
Selected text sources, public help pages, and normal widget loading do not consume credits. Paid intake media extraction, AI-assisted answers, fallback handling, and review work can use support credits so processing remains bounded.
Does Knowledge Intake publish answers automatically?
No. Intake creates review drafts for help articles, FAQs, surfaces, changelog entries, or approved-answer proposals. Owners accept and publish selected items; official support answers still require owner approval.
Will AnswerLattice make up answers?
No. Approved answers are served first. If coverage is missing, fallback is marked and repeated misses go to review.
Is this for prototypes?
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.
Approved answers and product boundaries
How AnswerLattice differs from generic chat, helpdesks, automatic screenshots, and unscoped context.
Is AnswerLattice a chatbot?
No. AnswerLattice includes AI-assisted support surfaces, but the core product is a support layer: in-app help, hosted help, FAQs, changelog, tickets, feedback, approved answers, and owner review.
Is AnswerLattice a helpdesk?
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.
What is an approved answer?
An approved answer is a reviewed, scoped support answer tied to product truth such as a feature, workflow, plan, role, release, state, or product surface.
How quickly can a small SaaS team start?
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.
Can I invite my team into AnswerLattice?
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.
How does in-app context work?
Your product can pass safe route, page, feature, workflow, role, and plan hints to the AnswerLattice widget. AnswerLattice uses those hints to prefer support content connected to that product surface.
Can users attach screenshots in the widget?
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.
Can AnswerLattice capture screenshots automatically?
No. AnswerLattice does not automatically capture the host app screen or scrape the DOM. Runtime visual context stays explicit and user-initiated.
Does AnswerLattice answer every question automatically?
No. Approved answers are served first. If coverage is missing, fallback can help, but repeated fallback becomes a support gap for owner review.
Fallback, tickets, feedback, and support work
What happens when coverage is missing and how repeated questions become review work.
What happens when AnswerLattice does not know the answer?
AnswerLattice can use fallback, capture the miss as a signal, and route repeated gaps into reviewable proposals or draft answers. Those drafts require human approval before becoming authoritative.
Can I hide the widget on specific routes?
Yes. Widget settings include blocked routes and allowed origins so customers can control where the widget appears.
Can AnswerLattice publish a public help center?
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.
Can I use my own support domain?
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.
Do tickets include debugging details?
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.
How are FAQs created?
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.
Can I add my own repeated answer?
Yes. Owners can write exact repeated questions and answers, attach article, tag, entity, and page context, publish them, and let AnswerLattice use them after approved answers and before fallback when the user question matches.
Can AnswerLattice work with an existing helpdesk?
Yes. AnswerLattice can complement ticket tools as the reviewed support-knowledge layer, but public website copy does not promise broad helpdesk integrations while those paths are rollout-gated.
What is the Support Board?
Support Board is a private owner/staff workboard for selected support gaps, internal notes, status history, and answer-proposal handoff. It helps owners track follow-up without turning AnswerLattice into a project-management tool.
What happens to feedback and feature requests?
Users can submit ratings, product-area feedback, feature requests, and suggestions from the Help Center. Owners review those items privately and can move useful signals into Support Board or answer-proposal review. AnswerLattice is not a public voting board.
Does Support Board sync every ticket or signal?
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.
Can AnswerLattice notify my team in Slack or email?
Yes. AnswerLattice supports Slack and email workflow notifications for support review events such as digest summaries, coverage drops, repeated answer failures, and test delivery. Broader adapter integrations should stay controlled rollout until they are safe for every workspace.
Operations, pricing, and runtime safety
How notifications, runtime context, release review, pricing, and workspace identity stay controlled.
Will proactive help interrupt users everywhere?
No. Proactive help is configured for specific product pages. The widget should only request or show configured prompts when the workspace has active triggers and approved support summaries for that page context.
Does every widget load scan all support data?
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.
Can coding agents use AnswerLattice through MCP today?
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.
What happens when a product release changes an answer?
Changelogs can be tied to product surfaces and affected answers. Stale-answer and release-impact checks then show which support content needs review.
What should I import first?
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.
Is pricing per resolved question?
No. Public packaging is predictable monthly pricing in INR. Beta setup can start free, paid plans and support-credit top-ups live in AnswerLattice Billing, and usage limits protect infrastructure without punishing support deflection.
Does widget context decide workspace identity?
No. Widget page context helps AnswerLattice choose relevant support. Workspace identity is resolved through AnswerLattice workspace, domain, widget key, and authenticated scope controls.