Sanaf AI
Start free
IT Operations

iLert, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your iLert account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • IT Operations
  • Connects with a key
  • 8 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What iLert is

iLert is an incident response platform for managing alerts, on-call schedules, escalations, incidents, and status pages.

You paste in a key from your own iLert account. It is kept encrypted, and you can withdraw it from inside iLert whenever you like.

How a run works

One message in, the work done in iLert.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in iLert. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own iLert account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

8 tools it already has

What it can do in iLert

These are the ready-made tools your AI employee already has in iLert. It is not limited to them, but it never has to be taught these.

  • Get AlertGet one iLert alert by its numeric ID, optionally expanding escalation rules, the next escalation user, or custom details.
  • Get Current UserReturn the authenticated iLert user, including identity, role, timezone, and active team context. Use this to verify who the API key represents before incident-response work.
  • Get IncidentGet one iLert status incident by numeric ID, optionally including subscription state, affected teams, or history.
  • List AlertsList iLert alerts with optional state, source, escalation-policy, responder, and report-time filters. Returns one page and a continuation cursor.
  • List IncidentsList iLert status incidents with optional lifecycle-state, affected-service, and report-time filters. Returns one page and a continuation cursor.
  • List On CallsFind who is on call for selected escalation policies, schedules, users, and a time window of at most three months. Returns one page and a continuation cursor.
  • List ResourcesList one incident-response resource catalog: services, teams, escalation policies, or maintenance windows. Use returned IDs as filters or references in alert, incident, and on-call
  • List SchedulesList iLert on-call schedules, optionally expanding current or next shifts and schedule definitions. Returns one page and a continuation cursor.
Access, and who is in charge of it

You stay the boss of your iLert account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own iLert account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in iLert is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in iLert and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about iLert

Can an AI employee really work inside iLert?
Yes. It signs in to your own iLert account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of iLert?
No. Nothing moves and nothing is replaced. Your records stay in iLert, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my iLert account?
You paste in a key from your own iLert account. It is kept encrypted, and you can withdraw it from inside iLert whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in iLert?
It has 8 ready-made tools in iLert today, among them Get Alert, Get Current User and Get Incident. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use iLert and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in iLert and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in iLert?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in iLert is written down with what it did and when.