To get a business circuit fixed quickly, open the ticket with the carrier's business support line as soon as you confirm the problem, and give them the circuit ID, the service address, an on-site contact with building access, when the problem started, exactly what you see, and what you have already tested, ideally including a test with a laptop plugged straight into the carrier's handoff. Write down the ticket number and the time you opened it, ask what priority it was given, and ask when the next update is due.
Carriers' support teams triage hundreds of tickets. The ones that move fastest are clear about the fault, show that the customer's own equipment has been ruled out, and make it easy to get a technician into the building. The ones that stall usually say "the internet is down" and nothing else, and then spend an hour proving the router was not the problem.
Before you call: confirm it is the circuit
Take five minutes to check the basics. It saves an hour on the phone and avoids a dispatch for a problem on your side.
- Check power and lights on the carrier's equipment, usually an ONT, NID or carrier router, and on your firewall. Note any red, amber or unlit lights.
- Check whether it is everyone or one area. If one floor or one group of users is affected, the problem is probably a switch or access point, not the circuit.
- Check whether it is everything or some things. If websites fail but you can reach an IP address, the issue may be DNS rather than the circuit.
- Restart your own equipment once, in order: firewall or router first, then switches. Do not restart the carrier's equipment repeatedly; it can erase information their engineers would use.
- Test at the demarc. If you can, plug a laptop directly into the carrier's handoff, configure it with your static IP details if needed, and test. If the laptop works, the fault is on your side of the demarc. If it does not, the carrier's side is the likely culprit.
The demarc is the line where the carrier's responsibility ends; our guide to the demarc and inside wiring shows where it usually sits.
What to have in front of you
| Item | Why the carrier needs it |
|---|---|
| Circuit ID | Identifies the exact circuit; account numbers alone can cover many services |
| Account name and number | Confirms you are authorized to open the ticket |
| Service address, floor and suite | Where a technician must go |
| On-site contact and access instructions | Who lets the technician in, building hours, escort rules, the telecom room location |
| Start time | When the problem began, and whether it is constant or intermittent |
| Symptoms | Hard down, slow, packet loss, specific sites failing, lights on the equipment |
| Tests already done | Restarts, laptop at the demarc, ping and traceroute results |
| Your static IP details | Lets the engineer check the right interface and routing |
Keep this on one page, printed and stored in the network closet, and as a shared file. If the internet is down, the file on the server may be unreachable.
Describing the fault so it gets the right priority
Carriers sort tickets by severity. Use specific, factual language:
- Hard down: "Circuit is down. No link light on the handoff, laptop plugged directly into it gets no connection, since 9:12am. Whole office affected."
- Degraded: "Circuit is up but losing about 5% of packets to multiple destinations since yesterday afternoon. Calls are breaking up. Traceroute attached."
- Intermittent: "Circuit drops for two to three minutes, several times a day. Times attached from our firewall logs."
A complete outage of a business's only connection is normally the highest priority. Degraded and intermittent problems are real faults too, but carriers need evidence to work them, which is why logs and test results matter. Our article on latency, jitter and packet loss explains which numbers to capture, and our speed test guide shows how to test fairly.
Ask the agent to confirm the priority, and if it seems wrong, say why: "This is our only connection and our phones run on it."
Intermittent faults need evidence
A circuit that drops for two minutes and comes back is the hardest kind of ticket, because by the time the engineer looks, everything tests clean. Build the case before you call, or keep the ticket open while you do:
- Export firewall or router logs showing each time the WAN link went down and came back.
- Run a continuous ping to the carrier's gateway and to an outside address, and save the results with timestamps.
- Note anything that lines up with the drops: time of day, weather, building work, a power event.
- Ask the carrier to check its own interface counters and error logs for your circuit over the same period.
A ticket with a week of timestamps attached is far harder to close as "no trouble found" than one that says "it keeps dropping."
The SLA clock
If your circuit has a service level agreement, the ticket matters beyond getting it fixed. Many SLAs measure downtime from the moment a trouble ticket is opened, not from when the outage started. A problem you noticed at 9am and reported at noon may count as three hours shorter than it was.
- Open the ticket promptly, even if you are still investigating.
- Record the ticket number, the time it was opened and the name of the person you spoke to.
- Ask what repair time the SLA promises, and when the clock stops. Some contracts stop the clock while the carrier waits for building access or for you to respond.
- Note when service is restored, and confirm the ticket is closed with the correct time.
Credits usually have to be requested, within a set period after the outage. We cover the details in what a 99.99% SLA actually buys.
While the carrier works the ticket
- Approve intrusive testing if asked. The carrier may want to take the circuit down briefly or run a loopback test, which checks the line up to its equipment at your site.
- Get the building ready. Tell the property manager a technician is coming, and make sure someone can open the telecom room.
- Ask for the dispatch window and the technician's arrival time.
- Keep everything in one thread: times, names, what was said and promised.
- Watch for "no trouble found." If the carrier tests clean but you still see the problem, ask what was tested, from where, and request testing toward the destinations that fail for you.
Some contracts include a charge if a technician is dispatched and the fault is on the customer's side. Testing at the demarc before you call is the best protection.
When and how to escalate
Escalate when an update is missed, the agreed time passes, the ticket is closed without a fix, or it is bounced between teams. Ask for the next level by role: a supervisor, the network operations center duty manager, or your account team. Business contracts often include an escalation list; ask for it when you sign, not during an outage.
- State the ticket number, how long it has been open and the business impact in one sentence.
- Ask what is blocking the repair and who owns the next step.
- Ask for the next update time and hold them to it.
Polite and specific works better than loud. The person on the phone rarely caused the fault and usually wants to close the ticket as much as you do.
A worked example
Hypothetical: the office, times and details are invented to show the sequence.
A dental office loses internet at 7:40am. The office manager sees that the carrier's box shows a red alarm light, restarts the firewall once, and plugs a laptop into the carrier's handoff: no connection. At 7:55 she calls the business support line with the circuit ID from the printed sheet in the closet, describes the alarm light and the laptop test, and gives the building's after-hours access number. The ticket is opened as high priority at 7:58, with an update promised by 9:00. Meanwhile, the phones forward to staff mobiles and the office switches to its backup cellular line.
At 9:00 there is no update, so she calls back, quotes the ticket number and asks for the duty manager. The carrier confirms a fiber cut nearby affecting several customers, with crews on site. Service returns at 1:20pm. She notes the times, and the next week requests the SLA credit the contract allows, with the ticket number and timeline attached.
Prepare before the next outage
- Print one page per circuit: carrier, circuit ID, account number, support number, escalation contacts and static IP details.
- Label the carrier's equipment and your firewall's WAN port.
- Set up monitoring so you know about drops, and have logs to send; see network monitoring for small business.
- Agree who opens tickets, and who covers when that person is away.
- Keep a backup connection so the ticket is an inconvenience, not a closure. Our outage checklist covers the first hour.
Help when the ticket stalls
When you buy through FiberX, Phil Morales stays your one point of contact after the sale, and that includes helping when a carrier ticket is not moving. We price circuits and backups across several Tier 1 carriers, the carrier pays FiberX so nothing is marked up, and quotes are free with a same-day response in most cases. Get in touch, call 478-758-8091 or text (347) 870-0965.
