From ITOM error to ServiceNow incident, in one conversation.
Ask about Discovery, MID Servers, Event Management and more. Get answers cited from the product documentation, Community articles — and when the docs aren't enough, the assistant raises the incident in ServiceNow for you. From there, check its status, add an update, close it, or reopen it - all in the same conversation.
- Answers grounded in the official Servicenow ITOM documentation
- You confirm every incident before it is created
- Incidents are raised under your own ServiceNow user
- Check status, close it, or reopen it - all in the chat
From the documentation
- MID Server — Configuration parameters
- MID Server — Troubleshooting
- Priority
- P3 · Moderate
- Caller
- Abel Tuter
- State
- New
Example conversation
Ask about any part of ITOM
- Discovery
- CMDB
- Service Mapping
- Event Management
- Asset Management
- Cloud Operations
- Automation
From question to resolution
Find the information you need, understand what is happening, and raise the incident when the documentation is not enough — without switching between tools.
Ask your ITOM documentation
Ask in plain language about Discovery, CMDB, Event Management, MID Servers and more. Every answer shows the documentation sections it came from, so you can verify before you act.
Start from a screenshot
Paste or attach an error screenshot and get the relevant troubleshooting steps.
The full lifecycle, not just creation
The assistant offers to create a P3 or P4 incident, always asking first. After that, check its status, read the latest work notes, close it once it's fixed, or reopen it if it isn't - all in the same conversation.
Raised as you, not a shared account
Register with your ServiceNow username. Every incident is created with you as the caller, so it lands in your queue and your history.
Less searching.
More solving.
Spend your time fixing the problem, not hunting through pages of documentation.
- 1
Describe the issue
Type the problem in plain language, or paste an error screenshot.
- 2
Get an answer with sources
The ITOM documentation and Community articles are checked first. You see the answer and the sections it is based on.
- 3
Escalate when you need to
Still stuck? Confirm, then choose P3 or P4. If you pick an unsupported priority, you are simply asked again.
- 4
Incident created
The incident is created in ServiceNow with you as the caller, and you get the incident number back.
- 5
Stay in the loop
Come back anytime to check its status and work notes, close it once it is fixed, or reopen it if it is not.
Things you can ask
Real questions ITOM admins and operators run into.
- Why is my MID Server showing as Down?
- A Discovery schedule finished but found no CIs. What should I check?
- How do I set up an event rule for a monitored server?
- What credentials does Discovery need for Windows servers?
- How do I fix duplicate CIs in the CMDB?
- What is Software Asset Management?
- What's the status of my incident?
- Close my incident, the fix worked.