Give the support team a useful starting point.
The fastest first step is to name the affected site, system, user impact and the time the issue began. A short description beats a guess about what component failed.
For a video issue, share the camera or recorder ID and whether the issue is live view, recording, playback or export. For access control, identify the door and the observed behavior without emailing personal credentials. For a network or Wi-Fi issue, include the affected area, device type and whether the problem is isolated or widespread.
Diagnose the system without delaying the right field work.
Video and access systems
Review health alerts, connectivity, recordings, user permissions, event history or approved configuration where the installed platform allows remote support.
Network and Wi-Fi
Review managed devices, switch ports, AP status and logs where authorized tools and customer access are available.
Cloud and IT
Investigate account, endpoint, service or configuration issues within the supported systems and the agreed service scope.
Coordination
Work with the onsite contact, ISP or manufacturer as needed and document the finding, next action and ownership.
Remote troubleshooting depends on a supported platform, functioning connection, appropriate permissions and the customer’s service arrangement. Some issues can be identified remotely but still require a physical repair.
Agree on the access method and change approval.
Record who authorizes a session, which systems are in scope and whether the support engineer may make a change or only observe. Use a customer-approved remote-access method with individual accounts and multifactor authentication where supported. CISA recommends MFA for remote access; exact access controls should match the customer’s policies. See source note.
If an outage affects a critical door or video server, define who can approve a reboot or configuration change and who is present to confirm the result. A support session should leave an understandable record of actions taken.
Remote diagnosis can point to onsite work.
Damaged cabling, failed power supplies, a door out of alignment, broken hardware, physical camera obstruction or a switch that has lost connectivity may need a technician at the facility. An onsite contact can often help distinguish a platform issue from a local power or equipment problem.
When a visit is recommended, the support record should state the evidence, likely parts, access needs, safety constraints and who will approve the scope. Avoid promising a remote resolution before the cause is known.
Make the next request easier.
Remote support questions.
Can every problem be fixed remotely?
No. Physical power, cabling, hardware, alignment and site-access issues can require a visit even when diagnosis begins remotely.
Do I need to share a password?
Use an approved secure access workflow. Do not put passwords in a regular email or web form.
Are response times the same for every customer?
Response and coverage depend on the applicable service agreement and the issue. Confirm the current arrangement with Terapixels before relying on a particular timeframe.
Reference note
- CISA, Require Multifactor Authentication: MFA for remote access.
- Specific remote capabilities, hours and charges depend on the installed systems and customer agreement. Confirm response commitments in the customer agreement.
Request help with your system.
Describe the issue, location and affected equipment so the team can route your request.
Request service ↗