Trigger by product page
Use safe route, feature, workflow, plan, or role context to match a prompt to the screen where the user is working.
Proactive Help
Canonica can use owner-approved, page-aware triggers to suggest relevant help from the widget when active triggers exist for the current app page.
Canonica product layer
Canonica can use owner-approved, page-aware triggers to suggest relevant help from the widget when active triggers exist for the current app page.
Owner-approved page triggers
Widget skips calls when disabled
Resolved suggestion summaries
Proactive Help
The widget should not guess or interrupt everywhere. Canonica keeps proactive prompts tied to active triggers, safe page context, cached trigger summaries, and approved support content.
Use safe route, feature, workflow, plan, or role context to match a prompt to the screen where the user is working.
Resolved trigger summaries can point to reviewed answers or support content instead of running broad lookup on every page view.
Runtime configuration tells the widget whether proactive help is enabled, so inactive tenants avoid unnecessary API calls.
When no active triggers exist, negative caching avoids repeated backend checks for the same page context.
Allowed origins, blocked routes, and safe context rules still apply before any proactive prompt appears.
If a prompt is missing or weak, feedback and fallback can become governance work instead of invisible analytics noise.
Workflow
Proactive help stays owner-controlled: configure the page trigger, connect it to approved support, let the widget display it only when eligible, and review feedback.
Connect the route or workflow to the product surface where users get stuck.
Define when the widget should suggest help for that page context.
Attach reviewed support content or an approved answer summary.
The widget checks capability state before requesting proactive help.
Use feedback and fallback signals to improve the trigger or support content.
Connected product truth
A proactive suggestion is still support knowledge. It must stay scoped to product context, approved content, widget controls, and reviewable signals.
Canonica can use owner-approved, page-aware triggers to suggest relevant help from the widget when active triggers exist for the current app page.
A proactive suggestion is still support knowledge. It must stay scoped to product context, approved content, widget controls, and reviewable signals.
Owner-approved page triggers
The prompt appears inside the same page-aware runtime controls.
Suggestions can point to reviewed answer summaries instead of free-form guesses.
Triggers stay attached to routes, workflows, and product areas.
Feedback and fallbacks keep proactive help reviewable.
Questions
No. It should appear only when configured and enabled for the workspace, with runtime capability checks preventing unnecessary calls when inactive.
No. Proactive prompts should point to approved support content or reviewable fallback paths. They do not publish new authoritative answers by themselves.
The runtime is designed to skip proactive calls when the feature is disabled and use trigger summaries and negative caching when no active triggers exist.
Canonica works best when proactive help stays connected to widget answers, hosted help, tickets, and answer review.