A support visit can appear successful while the original problem remains.
The device powers on. The network responds. The camera shows live view. The amplifier makes sound. The TV displays a picture.
But did the client’s actual problem get tested?
That is the question that matters.
Device testing is not the same as workflow testing
A technician may confirm that a TV works.
But the client may have reported that the bedroom TV could not watch a specific source.
A technician may confirm that the camera is online.
But the client may have needed playback from yesterday evening.
A technician may confirm that music plays.
But the client may have reported that the patio zone fails when grouped with the kitchen.
The device can be healthy while the workflow is still broken.
The original complaint should be repeated
Good support should ask:
What exactly was the client trying to do when the fault appeared?
Then that exact action should be tested again.
If the problem was “Netflix drops in the cinema after ten minutes,” a two-second picture test is not enough.
If the problem was “remote camera playback fails away from home,” testing live view on the local Wi-Fi is not enough.
If the problem was “the guest room cannot use DSTV,” testing the main lounge TV is not enough.
Client-side testing catches assumptions
Whenever possible, the person who reported the fault should test the system before support closes the call.
That may be the homeowner, house manager, office manager, guard or staff member who actually uses it.
They may use a different button, app, remote, room name or sequence from the technician.
That difference matters.
The goal is not only technical success.
The goal is restored use.
Some fixes need time
Intermittent faults should not be closed too quickly.
If a device failed after warming up, test it long enough to confirm the condition has changed.
If a network fault appeared under load, test real use, not only connection status.
If a power recovery issue appeared after load shedding, simulate or observe recovery where appropriate.
A fast green light is not always proof.
Notes should say what was tested
A useful support note should not only say “fixed.”
It should say what was tested afterwards.
For example:
“Main bedroom TV tested on DSTV and Apple TV. Client confirmed remote operation.”
Or:
“Gate camera live view and playback tested from mobile data. House manager confirmed access.”
That record helps if the issue returns.
The client buys the outcome
DG Technologies believes support should end where the client felt the fault.
The problem was not that a box had a technical state.
The problem was that the client could not watch, listen, view, control, open, secure or use something.
Testing the device is necessary.
Testing the original problem is what proves the repair.