We publish how we govern AI on a production network — what it may do, what it may not, and how each limit is enforced. Read it →
AI on staff for independent operators

It runs the network.
You run the show.

NICK is the AI that runs a small operator's network — 24/7 monitoring and alerting, an AI receptionist, provisioning, remote-hands, and change control. It even produces our cable channel. Built on Chaparral Wireless's real production network, not a vendor demo.

AI on staff. Not AI in charge. — read-only by default, every change human-approved, everything audited.

We built NICK for our own network, and it isn’t for sale. We’re an operator, not a vendor. This page is what it does, what it got wrong, and how it’s governed — published because we couldn’t find it anywhere when we needed it.

One AI. Every desk.

NICK doesn't do one thing. It runs the NOC, answers the phone, fixes the laptop, and airs the channel — and logs all of it, so you stay in control.

N

Runs the NOC

24/7 monitoring and multi-channel alerting — voice, SMS, chat, tickets — with a self-testing probe that proves the alarms actually work.

V

Answers the phone

A bilingual AI receptionist on your real phone system: tickets, balances, modem health, and a live hand-off to a human when it matters.

R

Fixes the fleet

Remote-PC management across staff and customer machines — heartbeat, cleanup, inventory, and repairs, without a truck roll.

P

Provisions subscribers

RADIUS-backed provisioning, DNS/IPAM updates, and a read-by-default bridge to legacy billing so ticket handling can just ask “who is this customer?”

C

Controls change

Every network change gets pre-review against the source of truth, a ticket, a journal entry, and post-change verification. Nothing changes unseen.

6

Airs the channel

NICK produces Paxelle, a 24/7 cable channel on our own plant — AI-produced, human-gated. Proof it can build, not just watch.

It works with the stack you already run. NICK reads the monitoring, inventory, billing and ticketing systems you have today rather than replacing them. There is no rip-and-replace and no migration project standing between you and the first useful answer — we did exactly this on our own network, against systems we inherited and didn’t choose.

It catches what slips through.

The point isn't a smarter dashboard. It's a guardrail that reads the whole network and finds the problem before the phone rings.

48 hrs → same day
An undocumented change took about 48 hours to trace — most of it spent finding out what had changed. With every change ticketed, journaled and verified, that diagnosis lands the same day. (Case study, 2026-07-15.)
90 of 232 were false
38% of auto-generated “customer offline” tickets were false positives from a single weak signal. A second live vantage catches them before a truck rolls. (Ticket #141452.)
Numbers from the source
Billing figures are pulled from the workbook cell that holds them — never from memory. No confident, wrong quotes.

We publish how it’s governed.

Your counsel is going to ask what the AI is allowed to do. NCTC, the buying co-op, surveyed its members in May 2026 and found 44% of member companies lack AI governance frameworks (Cablefax, 29 Jul 2026). Ours is written down, versioned, and public — so you can read it instead of taking our word for it.

Read-only by default

Approval is granted per action, never per session — agreeing to one change does not authorise the next. Every network change carries a pre-review, a ticket, a journal entry, and post-change verification.

Enforced, or process — we say which

Every control in the document is labelled as enforced in code or followed by a person, because the difference matters. A rule written in a prompt is a request. Only code is a control.

Including what we don’t claim

The document has a section for the gaps — what isn’t enforced yet, what we got wrong, and what we won’t answer. A governance page with no open items is a marketing page.

Read the governance document →What we’d have had to buy →

Or bring us in as your operator.

CWN Ops is a wireless operator that runs other operators. Take the pieces you need — one project, a long-term NOC, or a tower stood up with you. You’re hiring people, not licensing software — our NOC happens to be AI-assisted, which is our problem to solve, not a product you buy.

N

Remote NOC & ticketing

24×7 monitoring, alarm triage, outage handling, and tier-2 escalation — the same AI-assisted workflow we run on our own subscribers.

W

Wireless engineering

Greenfield design, capacity planning, and migrations on Tarana, Cambium ePMP/PMP 450, MikroTik, and OSPF/BGP transport.

T

Tower & field work

Climber-led installs, sector swaps, alignment, grounding, and post-storm triage across our regional service area.

M

Mobile towers (COW)

Rapid-deploy cell-on-wheels for events, emergency restoration, and pre-build coverage validation.

A

Audit & documentation

Inherited a network nobody documented? We map what you actually own — devices, circuits, credentials, the half-finished projects — and hand you the record. We did it here first.

V

Hosted VoIP / PBX

Carrier-grade PBX on validated trunks, E911 compliance, and tenant isolation. Bring your DIDs or use ours.

Recent work

Real incidents, real fixes — lightly anonymized. What an AI-assisted operator actually does on a Tuesday.

SMTP abuse hunt · ~20 min

From abuse-bot email to four named offending customers in twenty minutes

An RBL listing landed for our cable NAT egress IP. NICK verified it via DNS, traced the IP to its loopback on the edge router, set a 2-minute passive filter for outbound SMTP, surfaced four customer IPs sending raw mail traffic, flagged the most suspicious destination, and stood up a weekly DNSBL monitor across 10 blocklists. Zero customer-impacting actions without sign-off.

multi-system stitchalways-confirm
Vendor incident · 13-day case unstuck

Three base nodes offline. Vendor case stuck on a red herring. NICK reconciled seven systems.

Truth was scattered across a vendor portal, the NMS, IPAM, conntrack, OSPF, the customer ticket, and the vendor case. NICK authenticated to the vendor API, wrote a 30-minute state monitor, matched serials to physical interfaces, and produced one reconciled hand-off that unblocked the support thread. The monitor is still running.

vendor translatorpersistent monitoring
Inherited network · audited

The new owner needed to know what they actually owned

Indexed the prior tech’s history (owner-approved), walked every repo, found a large unreviewed branch with multiple credential exposures, surfaced in-flight projects nobody knew existed, and delivered a three-paragraph executive summary. No finger-pointing — just inventory.

multi-system stitchdiscreet
Onboarding · end-to-end

An ops manager emailed about a new hire — NICK caught four errors nobody asked it to look at

Matched naming convention, picked the license, pre-staged MFA, replied with a first-sign-in walkthrough, then proactively audited the relevant Teams membership and surfaced four discrepancies between what was described and what was actually in the directory. Zero round-trips through the owner.

inbox-to-investigation
Real SMS · live

NICK texts staff, takes replies, and holds policy

Staff allowlist, name-based addressing (numbers never reach the model), per-staff scope, after-hours approval windows by tier, per-recipient personas, an audit trail of every send, and a single-file kill switch. The mature version of “AI that pages your team.”

off-hours watchfield-tech coach
Legacy billing · bridged, not replaced

A billing platform from 1998 now answers Python calls

Most regional operators run a billing system from another decade with no API. NICK reverse-engineered the CGI executables behind it, exposed them as one cohesive read-by-default surface, and left writes to a human. Now AI ticket handling can ask “who is that customer” in one call.

billing-ops bridgevendor translator

The NICK suite

A coordinated team of AI personas built for operators. Each one has a job, a scope, and the right tools — not a generic chatbot.

Prime
NICK
Suite coordinator and operator-facing assistant.
NOC
NICK NOC
Network ops and alarms. Full visibility on the gear; write access gated behind approval.
Field
NICK T
Tech-on-truck assistant for tower & install crews.
Voice
Zia
Customer-facing voice: IVR, dispatch, callbacks.
Cable
NICK C
Cable plant: coax, fiber, amps, HFC.
Hosting
NICK H
Compute / VM / hosting operations.
Customer
NICK S
Subscriber-facing replies, scoped & safe by design.
Business
NICK B
Owner-facing back-office reports and finance prep.

Built by operators, not by a vendor.

CWN Ops is the services arm of Chaparral Wireless — a regional WISP / cable operator running production Tarana, Cambium, MikroTik, Harmonic CableOS, and a hosted VoIP stack. Every tool we sell is something we run on our own network first.

If you’re a WISP or small ISP that needs senior help on the gear, fewer pages at 2 a.m., or a path to lighter ops without hiring a NOC — we should talk.

Why operators call us

• You can’t staff overnight NOC anymore.

• Your tower lift is in two weeks and a sector died.

• You inherited someone else’s network and need an audit.

• You want AI working for ops, not bolted on top.

• You’re chasing BEAD/NMConnect dollars and need build-out muscle.

Tell us what’s hurting on your network.

For the services above — NOC, engineering, tower work. Calls are free and we’ll tell you straight whether we can help or you’d be better served elsewhere. If you just want to talk about the AI side, that’s free too and there’s nothing to buy.

Email noc@cwn-ops.com Read how we govern it