Support ticketing software for network installers: handling "the internet is down" calls properly
CamVerion team · 19 November 2026 · 6 min read
Quick answer
Support ticketing software for network installers logs every support request as a ticket with the customer, problem and priority, assigns a technician, tracks it to resolution and keeps the history for each site.
For a network installer, the most urgent phone call is always the same: "the internet is down". Behind it could be a failed switch, a loose patch lead, a router problem, the internet provider or a user who unplugged something. Whatever the cause, the client wants someone on it now, and wants to know when it will be fixed.
Support ticketing software gives every one of these calls a record, an owner and a clear outcome. This guide explains what installers need from it.
Why support goes wrong for network installers
- Calls arrive on technicians' personal phones, so the office never knows.
- No owner, so the client has to chase.
- No history, so each technician starts from zero.
- Chargeable work forgotten, especially quick fixes and replaced parts.
- No visibility of open calls across clients.
What support ticketing software should do
Log every call
Whoever takes the call should log it immediately: client, site, contact, and a clear description, for example "first floor has no network since 10am, Wi-Fi works, ground floor fine". Specific descriptions save diagnosis time.
Assign one owner
Every ticket needs one technician responsible for it. Assign from the office, or let technicians claim tickets from an open list.
Track clear stages
Stages such as Open, Investigating, Issue traced, Being fixed and Resolved tell everyone where a ticket stands. When the client calls for an update, anyone can answer.
Show the site's history
The technician should see what was installed at the site, when, and every earlier ticket. A switch that has failed twice, or a link that keeps dropping, points to a deeper problem.
Record parts, travel and charges
Replacement switches, patch leads, travel and time should be recorded on the ticket. That makes chargeable work easy to bill, and shows what support costs per client.
Close with a receipt
When the issue is resolved, the client should receive a short record of what was done and charged. It builds trust and avoids disputes.
Remote fixes count too
Many network issues are solved by a phone call or a remote session. Log those tickets as well. They are real work, they show the client you responded, and they build the history the next technician needs.
Turning support into income
Support is a steady income for network installers who organise it:
- Offer support agreements with a set response time and a number of visits.
- Charge per visit, with a minimum call-out, for clients without an agreement.
- Use ticket history to show clients the value you provide at renewal.
- Spot upgrade opportunities, such as ageing switches or weak Wi-Fi coverage.
Our guide on maintenance contracts explains how to structure and price service agreements for installation businesses.
What to measure
- Open tickets and their age.
- Average time to resolve.
- Repeat tickets per site.
- Support revenue against cost.
Ticketing and monitoring
Network monitoring tools tell you when something fails. Ticketing tells you who is fixing it. Use both: when monitoring raises an alert that needs a visit, log a ticket so it has an owner and a record.
Set priorities before the phone rings
Not every ticket is urgent, but every client thinks theirs is. Agree a few priority levels, and the response you promise for each:
| Priority | Examples | Target response |
|---|---|---|
| Critical | Whole office or shop offline, billing counters down | Within 2 to 4 hours |
| High | One floor or department offline, Wi-Fi down in meeting rooms | Same working day |
| Normal | One desk not working, slow Wi-Fi in one area | Next working day |
| Request | New user, new point, a change to the setup | By appointment |
Write the priority on each ticket when it is logged. It tells the technician which call to take first, and gives you an honest answer when a client asks why another site was visited before theirs.
A first-call checklist
The person taking the call can solve or narrow down many problems in five minutes. Ask:
- What exactly is not working? Internet, one application, printing, Wi-Fi or everything.
- Since when? A start time often lines up with a power cut, a change or a provider outage.
- Who is affected? One person, one floor or everyone.
- What changed? New equipment, an office move, a new internet plan or work by another contractor.
- Are the lights on the router and switches normal? Ask for a photo of the rack if possible.
- Has the client restarted anything? If so, what, and did it help?
Write the answers on the ticket. Even when a visit is needed, the technician arrives with half the diagnosis done.
What to keep for each site
The site record is what makes support fast. For each client site, keep:
- a simple network diagram, even a photo of a hand drawing
- the rack layout, with switch and patch panel labels
- the internet provider, account number and support number
- where the router, firewall and access points are
- which devices have fixed addresses, such as printers, cameras and servers
- photos of the rack after installation and after each change
Store passwords in a proper password manager, not in ticket notes, and record only where they are kept.
When a fix becomes a project
Some tickets reveal a bigger problem: a switch with no spare ports, cabling that fails testing, or Wi-Fi that was never designed for the number of users. Fix the immediate fault, then raise a quote for the proper solution. Note on the ticket that a quote was sent, so the next technician knows the history if the same fault returns.
Billing support fairly
Clients accept support charges when they are predictable. Common approaches:
- Per visit, with a minimum charge that covers travel and the first hour.
- Prepaid hours, used up as tickets are resolved, with a statement each month.
- Support agreement, a fixed yearly fee covering a set response time, a number of visits and a yearly health check.
Whichever you use, record the time and parts on every ticket, including free ones. At renewal, a list of tickets resolved during the year is the best argument for the agreement.
Monthly review
Once a month, look at tickets by client and by cause. A client with many tickets may need an upgrade. A cause that keeps appearing, such as unlabelled patch leads or overloaded switches, may point to a change in how you install. Support history is one of the best sources of new work for a network installer.
Network contractor support software: how CamVerion fits
CamVerion's service calls work as support tickets: clear stages from Open to Issue Resolved, a technician who is assigned or claims the call, notes, parts and charges as expenses, and a receipt for the client. Each call sits on the client record alongside the original installation. It is part of CamVerion's networking business software. Support agreements can be set up as maintenance contracts, so each scheduled health check becomes a service call and the agreement is flagged for renewal. It does not monitor networks, so keep your monitoring tool alongside it.
Frequently asked questions
What is support ticketing software?
Software that turns each support request into a ticket with an owner, status and history until it is resolved.
Do small network installers need ticketing?
Once more than one person handles support, yes. It stops requests being forgotten and shows response times.
Can customers raise their own tickets?
With a request link or form, yes; requests arrive for the office to approve.