
Watch all day
A real person watches your live cameras, 24/7. If we see a problem, we follow your response plan.
Your cameras and other sites.
Only your agreed cameras.
Account management and onboarding
1Degree helps security and service providers prepare client accounts for outsourced video monitoring in the US and Canada. The work connects site information, technical access, operator instructions and response contacts so your team can evaluate readiness before activation.


A real person watches your live cameras, 24/7. If we see a problem, we follow your response plan.
Your cameras and other sites.
Only your agreed cameras.

When your system sends an alarm, we check the video and follow your response plan.
60 minutes of staff time per camera each month, shared across your site. Extra time: $0.30/minute.
Alarm verification
We check your cameras at the times you choose and send you a report of what we find.
Up to 16 camera views and 5 minutes per check. Minimum: $22.50 per site each month.
Virtual guard toursA camera list is only one part of an account. Operators also need to know where the cameras are, what activity is permitted and which observations require action. Missing context can make an otherwise clear image difficult to interpret.
Build a site brief with the address, local time zone, camera labels, relevant entrances, normal operating pattern and authorized contact list. Add temporary deliveries or maintenance as time-limited exceptions. Use a consistent site identifier across technical records, instructions and reports.
Include your current monitoring platform and software version, and tell us whether the account already uses Immix. Our team uses Immix for monitoring; the technical review still needs to establish the connection and functions for your particular installation.
Test the required functions
Agree the instructions
Name the responsible people
A handover structure to complete for the account.
For each input, record
The following is a planning framework for your team. It identifies evidence worth collecting; it is not a claim that every account follows an identical implementation process.
| Record | What to include | Evidence for review |
|---|---|---|
| Site brief | Locations, views, blind spots, hours and expected activity. | An approved camera map and current site instructions. |
| Function tests | Required video, event, audio and access functions. | A result for each function on the actual installation, including relevant night conditions. |
| Event instructions | Action criteria, permissions and unclear/unavailable-video handling. | A walkthrough showing the next action for representative events. |
| Contact tests | Primary and fallback routes, availability and handoff information. | Completed authorized contact tests with any unresolved issues recorded. |
| Activation record | Included cameras/tasks, start time, open issues and responsible parties. | A clear decision that identifies who is responsible before and after the handover. |
Equipment online, workflow tested and monitoring active are different states. A successful camera login does not show that an event will reach the right operator with usable instructions. A date in a project plan does not establish that coverage has transferred.
Choose a representative account for the pilot. Include ordinary permitted activity and an ambiguous event as well as a straightforward test. Check the resulting record and contact handoff, then keep unresolved items with a named owner and a required next action.
When moving accounts from another operation, document the cutover sequence and the party responsible at every stage. Include what happens if a readiness check fails or the launch has to move. Review account-transfer and exit arrangements before depending on either provider to release data or access.
Your team should know who authorizes technical access, who holds administrative responsibility and how access changes when people or providers leave. Ask where account data and footage are handled, who may see them and what retention and deletion terms apply. Record the actual answers rather than assuming a standard arrangement.
For routine changes, use a record that includes the site, requested change, authorizer, effective time and expiry if temporary. A new contact number, shifted camera or late delivery instruction needs an acknowledgement and a clear active version. Sending an update and having it in use are separate steps.
You can begin with the equipment details you have, approximate site and camera counts, current coverage and the work you want to outsource. Identify what is unknown so the technical review can address it.
Use the site-readiness resource to organize those inputs. Your first review should leave your team with a clearer view of the required setup work, open decisions and evidence needed for a pilot.

Common questions
An existing portfolio can be reviewed for transition. Current equipment, data, procedures and transfer arrangements affect the work required. Keep responsibility for coverage explicit until the new arrangement is active.
Timing depends on the accounts, technical connections, procedures and outstanding setup work. The initial review identifies the required steps and target launch date. There is no single duration that fits every installation.
An unresolved issue that prevents an included task from working, such as missing event delivery, unusable video or an invalid response contact. Record the limitation and owner rather than treating a scheduled date as proof of readiness.
Yes, discuss the additional accounts and workload with the team. Use the same readiness evidence for each site; a successful pilot does not establish that every later installation is equivalent.
Related reading & tools
Share your company, client-site mix and coverage needs. Let’s work through the next step.
