# Business TV Support Call Checklist: What to Note Before You Call

> Before you call about a TV problem, note which screens are affected, the exact message or symptom, when it started and what staff already tried. Add the site name and the label on the receiver. Those details let support narrow the cause on the first call, without rebuilding the story through a long round of questions.

Source: https://www.sportsdirectllc.com/guides/business-tv-support-call-checklist · Guide · Last reviewed 2026-10-22 · Sports Direct | DLM Media

## Who this is for and what it helps you decide

This is for the person holding the phone when a screen goes dark: a shift manager at a restaurant during the dinner rush, a front-desk lead at a hotel, or an operations coordinator fielding a call from one of many locations. A business TV support call checklist turns a stressful moment into a short, useful conversation. You note a handful of facts in about a minute, and the person on the other end can start narrowing the cause right away instead of asking a long string of questions.

Working through the list also helps you decide three things before you dial:

- **Is this something staff can fix themselves?** A remote on the wrong input or a TV that lost power is a quick fix on site, not a support call.
- **How urgent is it?** A blank screen in a storage room can wait until morning. Every bar screen going dark before a big game cannot.
- **What exactly will you say?** A clear description on the first call usually means fewer callbacks and a faster route to a fix or a technician visit.

If your locations already follow a shared routine for problems, this list slots into it. For the escalation side (who calls whom and when), see our guide to [multi-location TV issue reporting](/guides/multi-location-tv-issue-reporting).

## The five things to note before you call

Support teams work by elimination. Each fact you bring rules out a group of possible causes. These five cover most of what a technician will ask.

1. **Which screens are affected.** Name them by location and label: the patio screens, the screen by the host stand, the TV in the private dining room. Say whether the rest are fine. "Some TVs are out" and "every TV in the building is out" point in very different directions.
2. **What the screen actually shows.** Write down any on-screen message word for word, including any code. If you can, take a photo with your phone. Note the symptom too: black screen, a "no signal" box from the TV itself, a frozen frame, blocky or pixelated picture, picture with no sound.
3. **When it started and what changed.** Was there a storm, a power flicker, a remodel, a new TV, a cleaning crew moving furniture, or a programming change on the account? A problem that began right after something changed is often connected to that change.
4. **What staff already tried, and what happened.** "We restarted the receiver for screen four, it came back for a few minutes and froze again" is far more useful than "we tried everything."
5. **Who and where.** The business name on the account, the site name or address, the label on the affected receiver, and a callback number for someone who will be standing near the equipment.

> **Tip:** If your receivers and remotes carry the same number as the screen they serve, items 1 and 5 take seconds. Our post on how to [label TV receivers and remotes](/blog/label-tv-receivers-and-remotes) shows a simple way to set that up.

## The business TV support call checklist

Print this table and keep it near the equipment rack or the manager's desk. It works as a call script.

| What to note | What it sounds like | Why it helps |
| --- | --- | --- |
| Screens affected | "The patio screens are out; the bar screens are fine." | Separates a local problem from something shared by every screen |
| On-screen message or code | "It says the channel is not authorized, with a code." | Points support to a specific cause and the steps that go with it |
| Symptom type | "Picture freezes and breaks into blocks every few minutes." | Signal, equipment and setup problems each look different |
| Start time | "Started around lunch, right after the storm passed." | Ties the problem to an event, a weather pattern or a recent change |
| What changed recently | "We moved the TV in the back room yesterday." | Disturbed cables and connections are a common culprit |
| What was tried | "Restarted that receiver once; checked the TV input." | Avoids repeating steps and shows what has been ruled out |
| Site and account details | "Business name, this location's address." | Lets support pull up the right account and equipment quickly |
| Receiver label or ID | "Receiver 4, the one labeled for the patio." | Identifies the exact unit, especially in a crowded rack |
| Callback contact | "Name and number of the person on site." | Someone near the TVs can follow steps in real time |

The receiver's identifying details are usually printed on a label on the unit or shown in its settings menu. If you are not sure where to look, say so; support can walk you through it. It is easier, though, to have those details written down ahead of time in a [one-page site record](/guides/multi-location-tv-documentation) for each location.

## What the pattern tells you, and what to do next

The single most useful fact is the pattern: which screens are affected and which are not. It shapes both what you try first and how urgent the call is. No pattern is a diagnosis on its own, but it narrows things down quickly.

| What you see | What it often points to | Sensible first step |
| --- | --- | --- |
| One screen out, the rest fine | Something local: that TV's input, its receiver, its cable or its power | Check the TV input and power, then restart that one receiver. See [one TV frozen or pixelated while the others work](/help/troubleshooting/one-tv-frozen-pixelated-bar). |
| A group of screens out | Something they share, such as a cable run, a splitter, a power strip or a section of the rack | Check whether the affected receivers sit together or share power, then call |
| Every screen out | Something upstream: the dish, weather, building power or the account | Note the time and any message, check for a storm, then call |
| One channel out, others fine | Often programming or authorization rather than equipment | Write down the exact message and code, then check the [error code help pages](/help) |
| Picture but no sound, or the reverse | Audio settings, the TV's speakers, or an external sound system | Check mute, volume and audio inputs before calling |

Here are the honest trade-offs in deciding when to call:

- **Calling right away** gets the problem logged and keeps it from being forgotten after the rush. The downside: if you call before checking the obvious, you may spend the call finding out the remote was on the wrong input.
- **Trying a few basic steps first** often solves the small stuff and makes the call shorter when it is needed. The downside: a manager who keeps tinkering during a busy shift loses time and may change settings that support would rather see as they were.
- **A sensible middle ground:** give staff a short list of allowed checks (input, power, one restart of the affected receiver) and then call. Anything beyond that list is support's job.

> **Note:** During heavy rain or snow, a satellite picture can break up or drop out across every screen and come back when the weather passes. Note the timing anyway. If the picture does not return after the storm clears, that is worth a call. Our post on [business TV during severe weather](/blog/business-tv-during-severe-weather) covers what staff should do while it is happening.

## Common mistakes that slow down the fix

Most delays on support calls come from a few avoidable habits.

- **Reporting "the TVs are down."** Without knowing which ones, support has to start from zero. Name the screens.
- **Clearing the message before writing it down.** On-screen messages and codes often disappear once someone presses a button or restarts the receiver. Photograph the screen first.
- **Restarting everything at once.** Pulling power on every receiver in the rack makes it harder to tell which unit was the problem, and they may all take a while to come back. Restart only the affected receiver, and note that you did.
- **Rearranging cables to see what happens.** Swapping connections between receivers and TVs can create a second problem on top of the first. Unless support asks, leave cabling alone.
- **Calling from the parking lot.** The person on the call should be able to see the screen and reach the receiver. Otherwise every step turns into a relay.
- **Not knowing which receiver feeds which TV.** In a rack of identical boxes, this alone can add a lot of time. Labels fix it permanently.
- **Dialing whatever number turns up in a search.** Business accounts and consumer accounts are handled differently. Keep the right support number on the checklist card so nobody has to guess.

Many of these come down to staff habits rather than equipment. Our post on how to [train staff on bar TVs](/blog/train-staff-on-bar-tvs) covers the small routines that prevent most of them.

## Questions to ask while you are on the call

A support call is also a chance to learn something that prevents the next one. Before you hang up, ask:

1. **What was the likely cause?** Was it on our side (input, cable, power), the equipment, the signal or the account?
2. **Is a technician visit needed, and how will it be scheduled?** Ask what time window to expect and who on site should meet them.
3. **Is there a reference or ticket number?** Write it on the checklist card or in your site log so a follow-up call does not start over.
4. **What should staff do in the meantime?** For example, move the game to working screens, or leave a receiver off until a technician arrives.
5. **Could this affect our other locations?** If the cause was an account or programming change, other sites may see the same thing.
6. **Is there anything we should change to keep this from happening again?** Ventilation around receivers, cable management, labeling or a pre-opening check are common answers.

If you find you are not getting clear answers to these questions, that is useful information too. Our guide to [commercial TV support evaluation](/guides/commercial-tv-support-evaluation) covers what good support looks like and how to judge it.

## Make it routine at every location

A checklist only helps if it is in reach when something goes wrong. A few habits make that happen:

- **Post the card where the equipment lives.** A laminated copy of the checklist table by the receiver rack, plus the support number, means anyone on shift can make a useful call.
- **Keep a one-page record per site.** List each screen, its receiver label and where the receiver sits. When someone new is running the shift, they can still answer "which receiver feeds that TV?"
- **Fold a quick screen check into opening.** Problems found before doors open are much easier to deal with than problems found mid-rush. Our [TV opening and closing checklist](/guides/tv-opening-closing-checklist) covers that routine.
- **Log every call.** Date, screens affected, cause and ticket number. Over time, the log shows whether one location, one receiver or one time of day keeps coming up.

For businesses that work with Sports Direct | DLM Media, support is coordinated from Phoenix, AZ, with technicians and engineers in all 50 states. General Support is reachable at 480-941-3703. You can see what we offer as an authorized commercial dealer on our [services](/services) page. If you want help setting up a support routine for your sites, a [conversation with a programming specialist](/contact) is a good place to start.

## Frequently asked questions

### Should staff restart the receiver before calling support?

One restart of the affected receiver is a reasonable first step, as long as someone photographs or writes down any on-screen message first. Restarts often clear the message, and that message is one of the most useful clues. Avoid restarting every receiver at once or restarting the same one repeatedly. If a single restart does not fix it, stop there, note what happened, and call.

### Where do I find the receiver information support asks for?

The receiver's identifying details are usually on a label on the unit itself, and many receivers also show them in a settings or system information menu. The simplest approach is to record those details once for every receiver at each site, alongside which screen it feeds, so nobody has to dig behind a rack during a busy shift.

### Who should make the support call, a manager or a staff member?

Whoever is standing nearest the equipment and can follow simple steps. Rank matters less than access: the caller needs to see the affected screen and reach its receiver. A bartender with the checklist card in hand often makes a better call than a regional manager phoning in from another site. The manager can still be the callback contact for follow-up.

### Is it worth reporting a problem that fixed itself?

Usually, yes, especially if it happened more than once or during a busy period. A screen that freezes and recovers can be an early sign of a failing cable, an overheating receiver or a signal issue that will get worse. Log the time, the screens involved and what it looked like. A short report now can prevent a longer outage at a worse moment.

### What if only one channel shows a message and the others work?

That pattern often points to programming or authorization rather than equipment, so write down the exact message and any code before doing anything else. You can look the code up on our error code help pages for general guidance. If the message stays, call support with the code, the channel and the receiver label, and ask whether other locations might see the same thing.

Talk to a specialist: 888-688-1699 (New Sales) or https://www.sportsdirectllc.com/contact