Field work needs controlled context
Technicians should not need full admin access to complete jobs. ISPAgents should give them limited, role-specific workflows tied to the customer, service, equipment, site, and job outcome.
Technician app capabilities
| Capability | Operational value | |---|---| | Assigned jobs | Installs, relocations, upgrades, downgrades, service checks, and equipment swaps. | | Customer context | Address, contact, package, access state, support notes, and safety instructions. | | Evidence | Photos, GPS, notes, signal readings, signatures, and closeout status. | | Stock usage | CPE, routers, ONTs, antennas, cables, and serialized assets used on the job. | | Cash collection | Controlled payment collection with receipt and finance review. |
Permission model
Technicians should see only the jobs and data they need. Sensitive finance, router, RADIUS, and customer actions should stay behind role permissions and approval rules.
FAQ
Should technicians manage routers from the app?
Only through controlled actions. Risky network changes should require role permissions, previews, approvals, and audit evidence.
Can the app track equipment?
Yes. Equipment used during the job should move from technician stock to the customer or site record with serial-number evidence when available.