IT support
An IT support chatbot for your teams
The agent guides your colleagues from your internal procedures, opens a ticket in your tool once they confirm and hands straight over to your team when the matter is sensitive.
Free · 30 conversations/month
Tier-1 IT support
Forgotten password, VPN refusing to connect, access to an internal tool: tier 1 is repetitive, and it keeps your technicians from the real incidents.
Password, VPN, printer, access to a piece of software: a large share of tier-1 requests is answered by a procedure already written. While your technicians handle them one by one, the real incidents wait. The agent answers straight away with your procedures, and what needs a technician lands in your ticketing tool.
Visitor: I can't connect to the VPN anymore.
Agent: If the reset changed nothing, I can open a ticket for the IT team.
Ticket opened in your tool, once confirmed
What the agent does
- Walks the user through it step by step from your internal procedures.
- Opens a ticket in your tool, if it exposes an HTTP API, once the user confirms.
- Starts a dedicated flow on a keyword such as “security incident”, which hands straight over to your team.
- Shows only on the sites you allow, your intranet for instance.
What the agent does not do
- The widget does not tell the agent who is writing: it sees neither an employee's rights nor their equipment, and checks nothing in your directory.
- On WhatsApp and the other messaging apps, the agent opens no ticket: an action that changes your data is not offered there. It is in the widget, once confirmed.
- The figures of the Analytics screen cover your whole workspace: they cannot be filtered agent by agent.
- Starting point
- A blank agent, fed with your procedures.
- What you plug in
- Your internal procedures, your ticketing tool's API, the widget on your intranet.
- Plan and channels
- One agent is enough for IT support, from the Free plan. With the Pro plan, you keep separate agents for IT, HR or your customers, each with its own documents.
Setting it up, in four steps
Import your procedures
Internal guides, IT FAQ, how-tos: as PDF, Word, Excel or Markdown. This agent's documents are seen by none of your other agents.
Connect your ticketing tool
If your tool exposes an HTTP API, declare the call that creates a ticket: the agent offers it, and the user confirms before the ticket is opened.
Plan for emergencies
A no-code flow can start on keywords, such as “security incident” or “hacked account”, and hand straight over to your team.
Publish on your intranet
Paste the widget's script on your intranet, and allow only its domains: up to 20 addresses per agent.
Frequently asked questions
Can the chatbot create tickets in our tool?
Yes, if your tool exposes an HTTP API. The agent offers to open the ticket, and the user confirms in the widget before it is created. When it hands over, the agent can also create a Zendesk ticket or a Salesforce case.
Can we limit the chatbot to our intranet?
You limit the widget to the domains you allow, your intranet's for instance: placed on another website, it does not show. It is not access control: the widget does not identify the employee and the agent answers everyone the same way. Only give it procedures that all your staff may read.
How do I keep it from making up a procedure?
The agent answers from your documents, and an anti-hallucination net, on by default, compares its answer with your documents and can remove what they do not confirm. On the Quality page, the knowledge gap detection brings out the recurring questions your procedures did not cover: those are the ones to write.
Ready to deploy your AI agents?
Create your account for free. 30 conversations a month, forever.
1 free AI agent
· Designed in France · Data partitioned per organisation ·