Field service should connect to orders
An ISP field job is usually tied to a commercial action: install, upgrade, downgrade, relocation, cancellation, equipment replacement, or support dispatch. ISPAgents should connect the order, customer, service, equipment, technician, and billing impact.
Field service workflows
| Workflow | What to track | |---|---| | Installation | Customer, package, equipment, GPS, photos, signal, signature, and activation. | | Relocation | Old site, new site, equipment movement, access update, and billing impact. | | Upgrade or downgrade | Plan change, router/RADIUS policy, customer confirmation, and invoice effect. | | Cancellation | Equipment recovery, final balance, deposits, refunds, and service cutoff. | | Equipment replacement | Old serial number, new serial number, reason, photos, and support history. |
Role-specific dashboards
Owners need backlog and revenue impact. Support needs customer status. NOC needs access and site context. Technicians need assigned jobs. Finance needs stock and billing evidence.
FAQ
Can field jobs trigger access changes?
Yes, but access changes should use controlled workflows through RADIUS, MikroTik, or custom connectors with audit evidence.
Can field service handle cash collection?
Yes. Cash collection should be limited by permissions and reconciled by finance before it changes trusted account state.