AI assistants
One assistant per need: role, tone, knowledge, tools and publishing rules, configured from a single interface and versioned.
Publishing and channels
Widget on your website, public page, internal portal, email, Slack and phone: one assistant, many touchpoints.
<script src="https://app.example.com/api/v1/widget.js" data-chatbot-id="3f2a…c91e" data-button-label="Any questions?" data-button-color="#1460d6"></script>
Channels
The problem
An assistant is only useful if it is available in the right place: on the public website, on the intranet, or in the tools people already use every day.
Each integration should not turn into a development project.
Capabilities
Each capability is shown with its actual availability.
Benefits
Pasting a script into your website is all it takes to display the assistant.
The same assistant and the same sources, whatever the channel.
The widget uses the branding of the organization the assistant belongs to.
One assistant per need: role, tone, knowledge, tools and publishing rules, configured from a single interface and versioned.
One number, one voice, the same knowledge as the chat: the callbot answers calls, routes them by topic and transfers to an agent when needed.
Metrics, conversation review, AI analysis, reports, live takeover by an agent and a multichannel ticket center.
The code to copy, the options and the checks to run.