Why keeping a signal history helps when you complain to your carrier

A signal history turns "my signal is bad" into evidence: dates, times, places, signal strength, network type and cell details. Carriers handle many vague complaints, and a clear signal report helps yours reach someone who can check the right mast. It also shows whether the problem is constant, at certain times, or in one spot.

Why vague complaints go nowhere

When you call a carrier, the first questions are usually the same: where, when, how often, and have you tried restarting? Without details, support may check the coverage map, say your area should be fine, and suggest a restart. That is not always unhelpful, but it rarely leads to an engineer looking at a real fault.

A written record answers those questions before they are asked. It also shows you have done the basic checks.

What a good signal report includes

For each reading, note:

• Date and time. Problems that happen only in the evening point to congestion.
• Place. An address, a room, or a point on a map. Indoors or outdoors matters too.
• Signal strength in dBm. More useful than bars, because it is a real number. See what a good signal strength in dBm is.
• Network type. 5G, 4G or older.
• Band and cell ID. These identify which mast and frequency your phone was using. Our guide to LTE bands and cell IDs explains them simply.
• Speed test results. Download, upload and ping, if data is the problem.
• What happened. A dropped call, no data, a call that would not connect.

How to build a signal history

1. Pick the places that matter. Your home, your workplace, the bits of your commute where calls drop.
2. Take readings at different times. Morning, midday, evening and weekend.
3. Record the same details each time. Consistency makes patterns easy to spot.
4. Note problems as they happen. If a call drops, write down where and when straight away.
5. Keep going for a week or two. A short history may look like bad luck. A longer one shows a pattern.
6. Put readings on a map. Seeing weak spots together makes a strong case. See how to make your own signal map.
7. Export it. A PDF signal report is easy for support staff to read. A spreadsheet file lets you sort and compare.

What patterns tell you

• Always weak in one place. Likely a coverage gap or a blocked signal. The carrier may know of a planned mast, or offer Wi-Fi calling or an indoor option.
• Weak only at busy times. Likely congestion on that cell.
• Fine until a certain date, then weak. Possibly a mast fault, a change in the network or new building work nearby. This is the strongest case, because something changed.
• Weak on one cell ID, fine on another. One mast or sector may be at fault.
• Weak everywhere, on your phone only. Possibly your phone, case or SIM rather than the network.

How to present it to your carrier

1. Start with a one-line summary: "Since early this month, calls drop at home every evening."
2. Share the key numbers: typical dBm at home now, and before, if you have earlier readings.
3. Mention the cell ID and band where the problem happens.
4. List what you have already tried: restart, a new SIM, another phone.
5. Ask what they can check: a mast fault, planned work, or indoor options.
6. Ask for a reference number and note the date of the call.

If the problem is your home broadband rather than mobile signal, the approach is similar. See when to call your internet provider.

What a signal history cannot do

A report does not guarantee a fix. Carriers plan masts years ahead, and a single home may not change their plans. It does improve your chances of a proper investigation, a fault being found, a SIM swap, or an offer like Wi-Fi calling. It can also help if you later need to ask about leaving a contract over poor service, depending on your contract and local rules.

Keep it honest

Record what you measure, including the good readings. A history that shows strong signal in the morning and weak signal in the evening is more convincing than one that only lists the bad moments.

How CellRadar helps

CellRadar shows live mobile signal in dBm with network type, carrier, band and cell ID. Its history and reports feature keeps a signal history and exports PDF and CSV reports, and the signal map puts your own readings on a map. A home-screen widget makes it quick to note a reading the moment something goes wrong.

Frequently asked questions

How long should I keep a signal history before complaining?

A week or two usually shows a clear pattern. If the problem is severe, contact your carrier straight away and keep recording while they investigate.

Will my carrier accept readings from an app?

They may run their own checks, but clear dates, places and dBm readings help them know where and when to look.

What is a cell ID and why does it matter?

A cell ID identifies the specific mast sector your phone was connected to. It helps the carrier find which part of their network is causing trouble.

Should I include good readings too?

Yes. Good readings at other times show the problem is real and specific, not just a phone that always reads low.