When a client phones and says something has stopped working, the natural instinct is to start at the symptom.
The TV has no picture. The music is not playing. A camera is offline. The Wi-Fi is weak. The touchscreen is slow. The app will not connect.
Those symptoms matter.
But the first useful question is often simpler:
What changed since it last worked?
That question can save hours.
Most faults have a timeline
AV and smart-home systems rarely fail in isolation.
Something usually happened first.
A fibre provider replaced a router. A decoder was moved. A cabinet was cleaned. A UPS was unplugged. A power trip happened. An electrician worked in the ceiling. A TV was replaced. A staff member changed Wi-Fi details. A service provider used a spare network port. A builder moved furniture and pulled a cable tight.
None of those details may feel important to the person reporting the fault.
To a support technician, they are often the clue.
The question is not about blame
“What changed?” is not an accusation.
It is a diagnostic shortcut.
In a premium home or business, several systems often depend on the same foundation. CCTV, Wi-Fi, Crestron Home, audio, streaming, access control and remote support may all pass through the same rack, router, switch or power path.
If one of those foundations changes, the symptom may appear somewhere else.
The client may say, “The lounge TV is not working.”
The real cause may be that the fibre router was replaced and an IP-controlled source device lost its reservation.
Recent changes narrow the search
If the system worked yesterday and failed after a site visit, the support process should start around that visit.
If it failed after load shedding, power recovery becomes important.
If it failed after a router change, IP addresses, Wi-Fi names, port forwarding and remote access should be checked.
If it failed after furniture moved, cables, emitters, ventilation and blocked devices should be inspected.
If it failed after a TV replacement, HDMI control, input labels, audio return, IR repeaters and mounting access may all be relevant.
The timeline helps the technician avoid random guessing.
Complex systems need disciplined questions
The more advanced the system, the more important the questions become.
A basic TV plugged into a decoder is easy to understand. A large home with distributed video, centralised audio, CCTV, managed networking, automation processors, remote access and power backup is different.
The system may be reliable, but it is still connected.
That means the support process must be structured.
For DG Technologies, a good first call tries to establish:
- what room or system is affected,
- when it last worked,
- what happened before the fault appeared,
- who has been onsite recently,
- whether there was a power event,
- whether anything was moved,
- whether any provider changed equipment,
- and whether photos or videos can confirm the current state.
That is not paperwork for the sake of paperwork.
It is how professional support reduces downtime.
A good answer protects the client
The client does not need to diagnose the system.
But if they can say, “It worked before the fibre router was replaced,” that changes the whole support call.
If they can say, “It stopped after the cabinet was cleaned,” that helps.
If they can say, “It failed after the electrician worked in the ceiling,” that helps.
The more accurate the story, the faster the correct person can be sent with the correct tools and parts.
The best support starts before the visit
Good fault finding is not only what happens onsite.
It starts before the technician drives.
That is especially important in larger KZN homes, holiday homes, commercial sites and estates where access, distance and availability all affect support timing.
Asking what changed since the system last worked is one of the simplest ways to respect the client’s time.
It keeps the investigation focused.
It also keeps the system history intact, which matters years after installation.
The fault may look new.
The clue is often in the change that came before it.