Is Canonica a chatbot?
No. Canonica includes AI-assisted support surfaces, but the core product is a support knowledge control plane: page context, canonical answers, drift checks, and owner-reviewed governance.
FAQ
Questions founders ask before installing Canonica
Practical answers about setup, widget behavior, pricing, support gaps, and product separation.
Is Canonica a helpdesk?
No. Canonica 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 a canonical answer?
A canonical answer is an approved, 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.
What makes Canonica page-aware?
Your product can pass safe route, page, feature, workflow, role, and plan hints to the Canonica widget. Canonica uses those hints to prefer support content connected to that product surface.
Does Canonica answer every question automatically?
No. Approved canonical answers are served first. If coverage is missing, fallback can help, but repeated fallback becomes a support gap for owner review.
What happens when Canonica does not know the answer?
Canonica 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 Canonica 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. Canonica 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 directly. Canonica can also generate article-backed FAQ suggestions during the knowledge workflow, but they stay reviewable instead of publishing automatically.
Can Canonica work with an existing helpdesk?
Yes. Canonica can complement ticket tools as the governed support-knowledge layer, but public website copy does not promise broad helpdesk integrations while those paths are rollout-gated.
What happens when a product release changes an answer?
Changelogs can be tied to product surfaces and affected answers. Drift 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. Canonica 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 Canonica Billing, and usage limits protect infrastructure without punishing support deflection.
Does Canonica use MenuList data?
No. MenuList is a separate product and one client/test-host use case. Canonica workspaces, dashboard, widget, scheduler, and Firebase data stay under Canonica product boundaries.