Third-party remote monitoring

Last modified: Friday June 06, 2025.

Before using Alta Protect with a third-party monitoring service, consider the following responsibilities and implications of setting up and managing the integration.

Partner responsibility for the integration

The partner is solely responsible for setting up remote monitoring with their chosen monitoring service. This involves configuring the necessary API calls and alarm settings within the Alta Protect platform, and any configuration of the monitoring service.

For more information about best practices and system design, see Alta Protect design guide.

The partner as the alarm company

The partner is considered the alarm company responsible for deployment, installation, obtaining local permits, complying with local certification standards, and covering costs associated with false alarms.

For more information, see Local authority licensing and dispatches.

System flow management

The partner needs to manage the alarm flow from the customer site, through the Alta Protect platform, to their third-party monitoring service, and back to the platform and its users. See Third-party remote monitoring alarm flow.

Support responsibility

The partner is responsible for providing support related to their integration, and the overall system flow to their monitoring service. There is no structured escalation path to Alta Video Support for integration-specific issues if the partner built the integration.

System testing and optimization

The partner must fully test their integration before going live. See Alta Protect readiness review.

The system must be carefully monitored post-installation. See Alta Protect setup walkthrough.

Sensor-only alarms

While Alta Protect provides camera-based detection, if you use sensor-only alarms without associated camera footage for remote-monitoring verification, these alarms have the same false alarm potential as conventional intrusion systems. See Sensors.