Every line answered when the map lights up: status given consistently from YOUR information, structured outage reports taken, emergency language transferred immediately by your rules.

Start, stop and transfer requests handled end to end: details collected, appointments booked into real synced calendars, confirmations sent in the customer’s language.

Due dates, payment locations, rebate programs, deposit rules: answered instantly and identically every time, from YOUR approved information — never a guess about your tariffs.

The monthly reliability report, the weekly vegetation-management status, the storm after-action draft — assigned to the AI like to an operations analyst, executed on schedule, fully auditable.

“When did we last replace the regulator at substation 7, and what did the crew note?” — answered in seconds with the work orders attached, instead of an afternoon in the records room.

Every AI-drafted report, summary and cross-check lands in Output awaiting review. Nothing operational moves without your qualified people’s decision.

PDFs, scanned as-builts, settings sheets, photos from the field, decades-old typewritten memos — the ingestion pipeline turns what the utility holds into queryable knowledge.

No source in your library, no claim: the AI cites the drawing, the memo, the manual — or says it cannot answer. On a grid, a guessed setting is not an option.

A CSR asks about a rebate program; a relay tech asks about settings history: each gets answers scoped to their role, enforced server-side, redacted at the field level.

Reliability report, inspection summary, after-action draft, regulatory-filing prep: work types molded to your utility, with default libraries and examples per type.

The AI’s workload is managed like the team’s: one-click views show what is urgent, late, today and tomorrow — the filing deadline never slips silently.

Reasoning streamed as it works, sources cited, milestones tracked, linked to the asset and the calendar — supervision on the record, interruption one click away.

Switching and clearance procedures, minimum approach distances, PPE matrices, storm playbooks: one library, current revisions on top, superseded versions outranked.

“What is the minimum approach distance at 69 kV?” — the current document, cited, in seconds, on the tablet in the bucket truck. Retrieval is instant; the qualified worker still makes the call.

Work types carry their default procedures: the AI drafting an inspection summary reads from the current inspection procedure — by construction, not by memory.

New CSRs, operators and field staff learn your systems, tariffs and procedures through guided training on your own documents — productive in days, not a season.

“How do I process a service transfer with an outstanding balance?” — asked to the assistant, answered from the procedure, without pulling the senior CSR off her queue.

Private chats work on any device with a login — the how-to knowledge follows the apprentice to the substation, the service center or the storm room.

An outage record opens: the affected-area notice and the restoration update draft themselves from your approved language, queued for approval — minutes after the lights go out.

Pole and substation inspection reports arrive from the field: filed to the asset record, defects summarized and routed to engineering with photos attached.

The monthly regulatory data pull, the quarterly reliability summary: compiled by the AI on schedule, filed to Output for the compliance manager — never reconstructed at deadline.

Customers on the affected feeder, accounts eligible for the rebate, addresses in the planned-work zone: audiences built from your own records — no list exports to a third-party tool.

Notices written the way customers actually read them — what is happening, when, what to do — in the customer’s own language, in your utility’s voice.

Contact preferences and opt-outs are enforced by the system, not by memory. Every send is on the record — evidence when the regulator asks who was notified, and when.

Zanus reads, drafts and answers. It does not switch, dispatch or control. Data from your operational systems flows in through connectors and the intake pipeline — documentation out, decisions human.

Customers, assets and documents mapped field by field, with a dry-run preview before anything writes — push, pull or two-way, your choice per field.

A full API for the rest of the stack: meter-data exports, inspection apps, custom tools — data in, results out, under scoped keys, every sync on the audit record.

The server redacts what a role cannot see — a contractor sees their work packet, not the network; a CSR sees the account, not the infrastructure documentation.

A searchable log of every audited action: who opened the one-line, who changed the procedure, when — personnel-access evidence ready in minutes, not weeks.

The identical OS runs on hardware you own inside your perimeter: air-gap capable, USB updates, no recurring fees — for the documentation that must never touch the internet.

Ask the chat: “I want to report a streetlight out on Elm Street” — watch it take a structured report like your best CSR on a quiet day.

Ask: “how would you draft the monthly reliability report?” — it walks the workflow it would run in your tenant, grounded, cited, sign-off included.

The full demo loads a utility tenant with sample records: reliability reporting, procedure answers, outage notices — your operation’s world, working.