Deliver governed answers across native chat, the web widget, Teams, Slack, Chatwoot and API. Guide intake and support human handover where configured.
Use free-text questions or configured starter forms to collect the information needed for the topic.
Let users inspect sources, review suggested follow-ups and interact with supported answer formats.
Use configured Chatwoot / OMNI handover when the conversation needs an agent, with ownership respected.
Collect the context a team needs through configurable starter forms, with required fields, validation and progress indicators. Topics can start with a form, combine forms with free text or use a form-only entry flow. Administrators control the fields and topic attachments.
Transfer configured Chatwoot / OMNI conversations to agents using handover keywords or AI-assisted assessment of requests for a person, frustration or repeated problems. Agent ownership is respected, and supported resolved conversations can return to the AI when the customer comes back. Handover must be enabled for the channel.
Offer relevant next questions that continue the user's line of thought. Suggestions prepare the next step for review rather than sending it automatically; topic controls and privacy checks govern their availability.
Opt-in native-chat topics can show sortable tables, progress checklists and labelled-figure tiles, plus eligible read-only overview, comparison and chart cards. The embedded widget keeps plain answers; shared and administrator views disable card controls.
Select a row, step or figure to prepare a relevant follow-up. The user reviews it and presses Send before normal search and answering resume. Computed analytics cards use existing answer content rather than a second model restating the figures.
Generate calculators, explorers, forms and decision aids from a validated component catalogue, with a sandboxed app option for supported bespoke experiences. Users choose whether to bring results back into the conversation; governed toggles and a global kill switch control availability.
A Customer Support skill acknowledges the issue, answers from the knowledge base, guides users through steps and checkpoints, and identifies when escalation is needed.
Validated navigation buttons can open cited sources, conversation files or earlier questions. Enabled native-chat experiences can share limited context about the open source, files panel or interactive experience with the assistant.
Refined native-chat and widget layouts improve input controls and mobile presentation. Source chips offer desktop hover details and tap-friendly mobile references. Minimise generated visuals to restorable chat chips; images use compact tiles or galleries. Charts, diagrams, maps, timelines and equations retain zoom and download controls.
Availability depends on topic permissions, platform configuration, supported models and deployment. Confirm the required workflow with representative sources during evaluation.
Bring representative sources, a useful business question and the controls your organisation needs.
