The AI comes with the operating system. And it already knows your data.
Not a plug-in. Not a separate product. The AI Engine ships with NOS, sees the same records your team sees, and — with permission — acts on any part of them.
- 24 languages
- On-premise by default
- Human-in-the-loop
- Ships free with every NOS install
Three principles the AI Engine is built around.
AI in enterprise software has a trust problem. NOS answers it with three defaults.
Grounded in your data
Every reply cites the NOS record it came from. No open-internet hallucinations.
Human-in-the-loop
Non-trivial actions stop for approval — with the plan attached and reversible.
Every prompt logged
Every question, answer and action is audited under the same identity as manual work.
Ask your network anything.
A conversation box in NOS that speaks the language of your network. Ask it who’s offline in a neighbourhood, why an OLT’s optical budget slipped last week, or to open a maintenance window for tomorrow — and it answers with the data and the change ready to approve.
- 24 languages, out of the box
- Every reply is grounded in your NOS data, not the open internet
- Actions are proposed first, applied only on your approval
The obvious fixes, done for you.
Most of a NOC’s nightly work is small, boring and repeatable — restart a stuck agent, rebind a mismatched ONT, reroute a POP whose upstream is flapping. NOS notices the pattern, files an auto-fix, and closes the ticket without waking anyone.
- Ships with a library of safe playbooks
- Everything it does is logged and reversible
- You write custom fixes in plain English — no code
The right answer, not the loudest alarm.
When something breaks, hundreds of alarms fire. NOS correlates them across NMM, telemetry and topology, walks the dependency graph, and tells you the one root cause — with the affected subscribers already grouped for you.
- Cross-layer correlation across L1–L3 and services
- Impact scoping in seconds — who’s affected, and how many
- Post-mortem draft written for you
A shift you can call.
Dial NOS. Ask what’s broken. Approve the fix. The Voice NOC turns the operating system into an on-call companion — for late-night engineers, for site walk-throughs, for anyone whose hands are full.
- English, Spanish and Arabic today · more languages shipping
- Locked to your operators, with per-user permission scopes
- Every call is transcribed into an auditable NOS record
Reach out before they churn.
CRM records, network signal history and payment patterns feed a churn model that flags subscribers who are quietly slipping — and drafts the outreach your care team sends.
- Per-subscriber churn probability, refreshed nightly
- Suggested actions in one click (uplift offer, care call, plan swap)
- Tracks lift against a hold-out group by default
"Give me the regulator report" — and it exists.
Board packs, regulator submissions, monthly ops digests. Describe the report you want; NOS drafts it against the data, formats it, and files it into your ERP for sign-off.
- Templates for the reports your team already writes
- Every number is traceable back to the query that produced it
- PDF, XLSX and API endpoints — you pick
Every capability, at a glance.
A short reference of what a Standard-edition NOS install carries out of the box.
Ask your network anything.
A conversation box in NOS that speaks the language of your network. Ask it who’s offline in a neighbourhood, why an OLT’s optical budget slipped last week, or to open a maintenance window for tomorrow — and it answers with the data and the change ready to approve.
The obvious fixes, done for you.
Most of a NOC’s nightly work is small, boring and repeatable — restart a stuck agent, rebind a mismatched ONT, reroute a POP whose upstream is flapping. NOS notices the pattern, files an auto-fix, and closes the ticket without waking anyone.
The right answer, not the loudest alarm.
When something breaks, hundreds of alarms fire. NOS correlates them across NMM, telemetry and topology, walks the dependency graph, and tells you the one root cause — with the affected subscribers already grouped for you.
A shift you can call.
Dial NOS. Ask what’s broken. Approve the fix. The Voice NOC turns the operating system into an on-call companion — for late-night engineers, for site walk-throughs, for anyone whose hands are full.
Reach out before they churn.
CRM records, network signal history and payment patterns feed a churn model that flags subscribers who are quietly slipping — and drafts the outreach your care team sends.
"Give me the regulator report" — and it exists.
Board packs, regulator submissions, monthly ops digests. Describe the report you want; NOS drafts it against the data, formats it, and files it into your ERP for sign-off.
Nights got quiet. The AI closes the top ten alarms itself and only pings a human on the eleventh. My on-call engineers actually sleep now.
— Director of Network Operations · national carrier
Read the full deploymentWhat the AI Engine helps you ship.
Questions we get on the first call.
Where does the AI run?
Inside NOS, on your Core. Prompts and data never leave your rack unless you explicitly enable a hosted inference channel for larger models.
What models power the AI Engine?
A small, on-device model handles routine actions; heavier queries route through your choice of frontier model provider. Both options are configurable per tenant and per role.
Can I write my own auto-fix playbooks?
Yes — describe the fix in plain English and NOS turns it into an approvable playbook. Everything logged, everything reversible.
Do I need a separate AI license?
No. The AI Engine ships with NOS. Each edition sets an AI budget (Community and Standard have daily caps; Advanced and Enterprise scale with the operator).
What languages does the Voice NOC speak?
English, Spanish and Arabic today, with more languages shipping each release. Voice access is per-user opt-in and permission-scoped.
Boot NOS. The AI is already on.
Every NOS install ships with the AI Engine active. Configure a Core, download Community, or talk to an AI specialist who’ll walk you through a playbook.