Office-wide outages and phishing clicks paged to on-call
A clinic loses its internet with patients in the waiting room, or a bookkeeper clicks a fake bank email at 4:45. The engineer on call is on the line in minutes and already knows which it is.
Many users down, a server or internet out, a ransom message or a suspicious click.
Asks how many and since when, gives your first instructions, pages and transfers on-call.
An urgent ticket, an engineer paged with a summary, and the caller never left waiting.
How it works
- Hears it's urgent
Everyone offline, a server unreachable, the phones down, a ransom note, or "I clicked a link and entered my password".
- Asks the few questions
How many people, since when, what lights are on the modem or server, what exactly they clicked or typed.
- Says what to do now
From your runbook: unplug the network cable on that computer, don't turn it off, don't click anything else, don't restart the server.
- Pages on-call
The engineer on the schedule gets a page and a call, and the caller is warm-transferred with a private summary.
- Opens the urgent ticket
Under the client, marked by your rules, with every answer and the time it started.
- Keeps the office calm
If more people from the same office call, they hear it's already being worked on and who has it.
Example call
- CustomerHi, it's Nadia at Pine Ridge Physio. I think I clicked something bad. A page asked for my Microsoft password and I typed it.
- AI agentThanks for calling right away, Nadia, that really helps. Is that computer still connected to the internet?
- CustomerYes. It's the front desk one.
- AI agentPlease unplug the blue network cable from the back of it, but leave it turned on. Don't log into anything else from it.
- CustomerOkay, it's unplugged.
- AI agentPerfect. I'm putting you through to Kyle, our on-call engineer, now. He'll take it from here.
- AI agent(privately, to Kyle) Pine Ridge Physio, Nadia at front desk. Entered her Microsoft 365 password on a phishing page about 4:40. Front desk computer unplugged from the network, still on. Connecting.
After the call: Kyle picks up knowing it's a credential phish, not malware, and resets Nadia's password and sessions within ten minutes. The urgent ticket has the time, the page she saw and the steps already taken.
What your team gets
- On-call paged only for real outages and security scares
- First steps from your runbook given before the transfer
- Urgent tickets with the start time and every answer
- Other callers from the same office told it's in hand
- After-hours escalations by each client's agreement
Questions
How does it tell an outage from one broken computer?
It asks how many people and which systems. Your rules decide what pages on-call.
Will it tell the caller to run a fix?
No. It only gives the first steps your runbook lists, like unplugging the network cable, then hands off.
What happens at 2 a.m.?
The engineer on call is paged and called by your schedule, and the caller is put through.
Does it promise a response time?
Only the one in the client's agreement, and only if you've told it to.
Hear it on your phone
Request a demo call and the agent phones you, set up for IT support like yours.