LuxAgents
An agent for every job. A person for every decision.
Agents cover the life of a fiber network, from the first survey to the monthly filing. Each works on its own desk, with its own tools, and your team decides what it may do without asking.
The roster
Sixteen agents. Each does one job.
Built-in limits
An agent cannot be talked into another job.
The tools of each job go to one agent. The server refuses the rest.
Its jobWalled off
| Agent |
|---|
Pick a column to see who holds that power.
The roster
Agents across the life of a network.
Filed the way the product files them: planning the network, building it, running it, and the office behind all three.
Plan — before a shovel moves
Survey
Turns an area into walkable survey work orders. Field captures come back as typed layers.
Design
Designs the fiber network: architecture, placement, cable layers, BoM and BoQ.
Expansion
Finds where to build next: demand, serviceability and spatial statistics over market data.
Build — from design to the ground
Splice
Compiles splice diagrams from the design: closures, splitter assignment, TIA-598 continuity.
Riser
Designs riser diagrams: fiber-to-unit assignment, spare policy, cable sizing and splits.
Project Manager
Plans the build: the schedule, crew lineups and work-order sequencing.
Permitting
Prepares right-of-way permit packages per street, tracks submissions and expiries, and names what blocks a street.
Operate — the live network
Ops
Runs the day live: crews on the map, assignments, arrivals.
NOC
Watches the live plant: alarms, outages, repairs.
Warehouse
Tracks materials, assets, procurement and stock levels.
Back office — money, customers and regulators
Finance
Follows the money: budgets against actuals, payroll review, contractor certificates and invoices.
Billing
Keeps the subscriber ledger honest: folds the cycle, reconciles payments, sweeps collections.
Spatial Analysis
Answers spatial questions over your own data: demand, serviceability, clusters on the live map.
Retention
Watches churn risk on the subscriber ledger and proposes save offers.
Wholesale
Keeps the partner book honest: lines per partner, what a period cost and why, which outage reaches a partner.
Compliance
Tracks regulator obligations and deadlines, and folds coverage and build data into draft filings.
Scope
Each agent can only do its own job.
Every agent has walls: tools the server removes before the model ever sees them. The Design agent is the only one that can change the network. Ops is the only one that can dispatch crews. The NOC is the only one that can act on subscriber devices.
Walls remove tools; they don’t just hide buttons
A read-only role gets the agent without its write tools
Agents cannot edit the rules that govern them
Control
Proposals wait for a person.
Governed actions across billing, permits, stock, network devices and filings ship as proposals. They wait in one Inbox, and Confirm runs the approval as you, on the record. A person holding the grant can let an action run on its own. The high-risk ones are for an Owner or Admin only, and a machine never flips its own switch.
One Inbox for every agent’s proposals
Autonomy set per action, by the people who hold the grant
Two pole-loading actions stay with a person, always
Transparency
See every step the agent took.
An agent’s session shows what it read, what it ran and what it wants to write, step by step. You choose how far it goes before it stops: approve every write, approve writes and heavy computation, or let it draft freely and review at the end.
Every tool call visible in the session
Stop, correct and continue in the same chat
Write modes: plan, ask or auto
Your agents
Make an agent your own.
Start from any agent and give it a name, a model, your instructions and a scope. An instance is never wider than the agent it came from, never wider than the person who made it, and never more automatic than your organization allows.
Your instructions and your model choice
Limited to the classes of data you allow
Bound by the same walls and approvals
Voice agents
Agents that answer the phone, and say so.
Put an agent on a phone number. It opens every call by saying it is an AI voice agent, hands off to a person when asked, and keeps a transcript rather than audio. Before an outbound call it checks do-not-call, consent and calling hours, then files the call as a proposal.
Built on any agent you can already create
Handoff, disclosure and audio-off checked before publishing
Tested against simulated callers before it goes live
Questions
How the agents stay in their lane.
What does an agent actually do?
Desk work: it drafts designs, splice plans, permit packages, schedules, purchase orders and answers, on the same record of your network your team uses. Your crews do the physical work.
What stops an agent from going too far?
Two things. Each agent is only given the tools of its own job, and the server refuses everything else. And every action starts as a proposal a person decides. An agent never files, pays, digs or promises alone.
Who decides what runs on its own?
You do. Actions start as proposals. An agent can never switch itself to automatic, and the actions with real consequences, like submitting an application or issuing a purchase order, can only be turned on by an administrator.
Can we limit who uses which agent?
Yes. Access follows your roles. A person whose role may read an agent but not drive it keeps the conversation but loses every action that writes.
Do agents learn from our data?
Your data is never used to train models. It is encrypted in transit and at rest and isolated per workspace.
Agents draft. Your team decides.
Pick the job you want off your desk.
Tell us which work your team spends its week on. We’ll show you the agent that drafts it, and where your people sign off.