Robin analyses recurring trends in your tickets and suggests what would have resolved them: knowledge base articles, scripts, definitions, and playbooks. This is the page that tells you what Robin could not answer well, and what to add so that it can.
Before you begin
Important: Full admin permissions are needed to access AI Center.
Navigate to Actionable insights
From the sidebar, go to AI Center > Optimize > Actionable insights.
The number beside Actionable insights in the menu is how many suggestions are waiting for you.
How the page is organized
Three tiles at the top of the page track where each suggestion stands. Select a tile to see what is in it.
| Tile | What it holds |
|---|---|
| Suggestions | New recommendations waiting for review. |
| Saved for later | Suggestions you have parked rather than acted on or dismissed. |
| Created | Suggestions you have turned into an article or a script. |
Each suggestion in the list shows what Robin proposes to create, tagged with its type, and a count of the tickets or devices behind it. Use Insight type to filter the list to one kind, and Load more insights to see beyond the first page.
There are four insight types:
| Type | What Robin is proposing | Where it lands once created |
|---|---|---|
| Article | A knowledge base article for a question that keeps coming up without documentation behind it. | Your knowledge base |
| Script | A script to automate a fix your team is performing manually. | Your script library |
| Definitions | A company term or an internal software name Robin has seen in tickets but does not recognize. | AI Center > Optimize > Definitions |
| Playbooks | A repeatable workflow for a scenario that recurs with the same handling each time. | AI Center > Optimize > Playbooks |
Suggestions
Suggestions are generated from recent account activity. Expand one to see the detail behind the recommendation before you decide.
The review button matches the insight type. In each case, review what Robin has drafted, then click Create.
- Article: Click Review article, then Create to add it to your knowledge base.
- Script: Click Review script, then Create to add it to your script library.
- Definition: Click Review definition, then Create to add it to your Definitions.
- Playbook: Click Review playbook, then Create to add it to your Playbooks.
Important: Review before you create, particularly for playbooks and definitions. A definition changes how Robin interprets every request in scope, and a playbook changes what it does. Neither is limited to the ticket the suggestion came from.
What you create moves to the Created tile, and the count beside Actionable insights in the menu drops.
You can also postpone a suggestion or dismiss it, using For later or Hide.
Tip: A script you create here is not yet available to Robin. Enable it on the script itself, in Admin > Monitoring and automations > Scripts. See Robin: AI assistant for end users.
Saved for later
Suggestions you have postponed, so you can review them when it suits you. From here you can review and create them, or hide them if they are no longer needed.
Created
Everything you have turned into an article or a script, as a record of what has been acted on.
When there are no insights
A new environment shows Nothing to report... yet while Atera gathers data. Insights are built from your ticket history, so an empty list on a new account is expected rather than a fault.
Tip: If the list stays empty on an established account, the likely cause is that ticket history has not been indexed. Insights need something to analyze.
