One order, eight handoffs
An ISP installation workflow connects the commercial promise to a tested service at the right address. Keep one order reference across the quote, job, equipment record and invoice, whether your team uses a spreadsheet, paper job sheet or operations software. The workflow below is vendor-neutral operating guidance; the product readiness section describes the separate ISPAgents scope.
Lead → quote/payment → service order → scheduled job → on-site checks → evidence and acceptance → activation/invoice → follow-up.
For example, a customer pays an installation deposit on Monday and books Thursday morning. That payment clears the commercial gate; it does not prove coverage or working service. If Thursday’s optical reading fails the approved design, the technician records the reading, holds completion and assigns the fault to the NOC. Finance receives the actual activation date after a successful retest, not the original appointment date.
For the identity handoff, read one subscriber, one device identity. For equipment qualification, use the TR-069 device compatibility guide.
1. Lead and coverage pre-check
Owner: Sales gathers the request; the NOC or survey team confirms feasibility.
Record: Customer contact, installation address and location, requested plan, access technology, candidate serving site or distribution point, available capacity, site access restrictions and survey outcome. Mark coverage as provisional until the required survey is complete.
Common failure: A map pin inside a coverage area becomes a promise even though the actual property cannot receive the proposed service.
Preventing check: Confirm the exact building and route. For wireless, review the proposed path and whether an on-site survey is needed; for fibre, confirm the planned drop route and serving port capacity. Name the person approving the coverage decision before promising an appointment.
2. Quote and payment before installation
Owner: Sales agrees the scope; finance verifies the payment or approved credit terms.
Record: Accepted quote version, equipment ownership, installation charge, recurring plan price, deposit or prepayment requirement, payment reference and balance due. Separate an installation deposit from recurring service charges.
Common failure: A forwarded payment screenshot is treated as cleared funds, or a technician collects an amount that finance has already received.
Preventing check: Finance verifies the reference in its payment records, links it to the order and records who cleared the commercial gate. If the agreed terms allow installation before payment, record the named approval and amount outstanding. Give the technician a collection instruction, not a guess.
3. Create the service order
Owner: Operations creates the order and assigns a single accountable owner.
Record: Customer and service identifiers, site, approved quote, plan, access method, scope of work, equipment reservation, payment clearance and completion criteria. Keep later scope changes against the same order reference.
Common failure: Dispatch receives only a chat message and installs the wrong plan or at the wrong address.
Preventing check: Read back the site, plan and equipment against the accepted quote. Resolve duplicates and missing approvals before turning the order into a field job. Keep order state, job state, payment state and service state distinct.
4. Schedule the job
Owner: Dispatch coordinates the customer and technician; the technician confirms readiness.
Record: Appointment window, customer contact, technician, access arrangements, reserved serialised equipment, tools, planned duration and escalation contact. Record a reason and next owner for a reschedule.
Common failure: The technician arrives without the correct CPE or ONT, or cannot enter the property.
Preventing check: Confirm customer availability and stock before dispatch. Review the site-specific work and safety procedure with an appropriately trained installer. Give the technician a job sheet they can consult when connectivity is poor, with no shared administrative passwords on it.
5. Technician on site: build, identify and test
Owner: The technician installs and records evidence; the NOC validates access and exceptions.
Record: Arrival time, installed model, serial and relevant MAC address, serving site or port, physical checks, access identity reference and dated test results. Distinguish the WAN MAC from a Wi-Fi or LAN MAC.
- CPE mounting: Follow the approved installation design and manufacturer procedure. Check mounting, cable routing, weather protection and power before testing. Record deviations for approval.
- Wireless alignment or ONT optical check: Record the actual signal measurements and serving radio, or optical receive reading and serving port. Compare them with the approved link design and the specific equipment limits; a single universal threshold is not a substitute for those limits.
- Device claim by serial/MAC: Compare the physical label with inventory and the service record. Resolve a duplicate or unexpected customer assignment before claiming the device for this job.
- PPPoE or hotspot credentials: Use the approved subscriber identity and profile. Keep passwords in the authorised credential system, not photos, chat or the printed checklist. Confirm the expected session or authorised access with the NOC.
- Speed test: Use the operator’s agreed test method, preferably a wired connection where possible to separate access performance from Wi-Fi. Record downlink, uplink, latency, test endpoint, connection method and time; compare against the agreed acceptance criteria.
Common failure: A radio shows a link, but the wrong subscriber profile is active or the customer cannot reach the internet.
Preventing check: Match equipment identity, subscriber identity and serving point, then verify usable internet and the service test. Escalate a failed reading or session with the evidence and a named owner; do not mark the job complete just because the device powers up.
6. Photos and customer signature
Owner: The technician assembles the handover record; the customer confirms acceptance or records an exception.
Record: Necessary installation photos, device-label evidence, test results, work completed, equipment handed over and customer acceptance with date. Follow the operator’s consent and retention process; keep passwords and unrelated personal details out of photos.
Common failure: A signed sheet has no test result, or a photo shows a different device from the one assigned.
Preventing check: Match evidence to the order and installed serial. Explain the result and any limitations to the customer before requesting a signature. If acceptance is refused or the customer is absent, record the reason and next action instead of inventing acceptance. A signature does not override a failed service test.
7. Activation and first invoice
Owner: The NOC confirms service activation; operations closes the work; finance checks the first bill.
Record: Activation timestamp, confirmed plan and access result, completion evidence, billing start date, installation charge, recurring charge, deposit allocation and invoice reference. A temporary test session is separate from the final approved activation.
Common failure: Scheduling or payment triggers the first bill even though installation failed, or an installation deposit is charged twice.
Preventing check: Reconcile the accepted order, working service and finance record before closure. Apply the agreed billing and proration rules, account for money already received and send the customer the resulting bill or receipt through the established process. Keep unresolved billing and access exceptions assigned.
8. Follow-up call
Owner: Support contacts the customer within the promised follow-up window.
Record: Whether service is usable in the customer’s normal setting, any Wi-Fi or access concern, understanding of the first bill, support contact details and any linked fault ticket.
Common failure: The wired installation test passes, but the customer’s usual room has poor Wi-Fi or the first bill is confusing.
Preventing check: Ask about actual use and the first bill rather than asking only whether the router has power. Route performance issues with the installation evidence; give every unresolved item an owner and next update time.
Printable technician checklist
Print this page: A4 portrait, 100% scale, browser headers and footers off. Only this checklist prints. Tick a box only after checking; mark N/A with a reason.
Order/job: __________________ Date: __________ Technician: __________________
Customer/site: __________________________________________________________________
Plan / serving point: ______________________________________________________________
Before work
- ☐ Confirm address, contact, access permission and approved installation scope.
- ☐ Check coverage approval, payment clearance or credit approval, and collection instruction.
- ☐ Match reserved equipment and tools; review the site safety procedure and escalation contact.
Install and verify
- ☐ Check mounting, cable routing, weather protection and power against the approved design.
- ☐ Match serial / relevant MAC to inventory and service; resolve duplicate device claims.
- ☐ Record wireless alignment readings or ONT optical reading; compare with approved limits.
- ☐ Check PPPoE / hotspot identity and profile with NOC; record a reference, never the password.
- ☐ Confirm usable internet and record the agreed speed test, method, endpoint and time.
Model / serial / MAC: ______________________________________________________________
Signal / optical reading and approved range: __________________________________________
Access identity reference: __________________ NOC verifier: __________________
Down / up / latency: __________________ Test time: __________________
Test method / endpoint / pass criteria: __________________________________________________
Handover and close
- ☐ Attach necessary photos and test evidence to the job; exclude passwords and unrelated details.
- ☐ Explain service result and support contact; record acceptance or an explicit exception.
- ☐ Confirm activation and billing start with operations; reconcile deposit / collection evidence.
- ☐ Set follow-up owner and date; hold completion if a required check fails.
Evidence reference: __________________ Activation / billing date: __________________
Customer acceptance / signature: __________________ Date: __________________
Exception / N/A reason / next action: __________________________________________________
Next owner / follow-up date: _________________________________________________________
Installation checklist · ispagents.com/guides/isp-installation-workflow · 16 October 2026
Where ISPAgents fits: readiness before rollout
ISPAgents supports basic subscriber records, search and device assignment/removal. ISPAgents service-order and Customer 360 foundations are a guided pilot, with scope agreed during onboarding. ISPAgents field-job references and inventory reservation foundations are a guided pilot; scheduled jobs, a full technician job view, an on-site device-claim workflow by serial/MAC, photo capture and customer signatures remain planned in this installation workflow. ISPAgents customer billing and service-policy foundations are a guided pilot; live access changes remain gated.
Treat the checklist above as an operator procedure, not proof of an end-to-end shipped installation product. Review the field-service scope and technician app roadmap, then discuss a guided installation pilot using one example order and its completion evidence.
Continue the installation handoff
- Canonical subscriber and device identity: keep the physical device and service association clear.
- TR-069 device compatibility: qualify the intended model and firmware before relying on remote management.
- FreeRADIUS versus managed RADIUS: compare responsibility and guided pilot gates for access management.