Full-site design previewPreview forms do not send messages
1Degree Surveillance

Account management and onboarding

Turn a client account into a usable monitoring plan.

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.

Illustration of Asian technical staff reviewing site cameras and a site plan

Choose how we watch
your cameras.

Get a quote
Illustration of a fictional monitoring specialist watching several live camera feeds
Day24/7Night

Watch all day

A real person watches your live cameras, 24/7. If we see a problem, we follow your response plan.

Shared team$25per camera / month

Your cameras and other sites.

Dedicated team$35per camera / month

Only your agreed cameras.

Continuous monitoring
Illustration of an alarm at a warehouse entrance after dark
AlarmVideo check

Check alarms

When your system sends an alarm, we check the video and follow your response plan.

$10per camera / month

60 minutes of staff time per camera each month, shared across your site. Extra time: $0.30/minute.

Alarm verification
Illustration of camera checkpoints at a site gate, yard and loading bays
Scheduled camera round1 Gate 2 Yard 3 Loading bays

Check at set times

We check your cameras at the times you choose and send you a report of what we find.

$0.75per scheduled check

Up to 16 camera views and 5 minutes per check. Minimum: $22.50 per site each month.

Virtual guard tours

Start with the information an operator needs

A 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.

The account handover

Make the next action and its owner visible.

  1. Connect

    Test the required functions

  2. Prepare

    Agree the instructions

  3. Hand over

    Name the responsible people

A handover structure to complete for the account.

View the working details
Account handoverPlanning inputs
Equipment and access
Models, required functions and connection test.
Site instructions
Named areas, coverage hours and routine activity.
Response permissions
Authorized actions and current contact ladder.
Activation decision
Test results, open issues and the decision owner.

For each input, record

  • Evidence
  • Owner
  • Open action

Use five records to check readiness

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.

Suggested account readiness records
RecordWhat to includeEvidence for review
Site briefLocations, views, blind spots, hours and expected activity.An approved camera map and current site instructions.
Function testsRequired video, event, audio and access functions.A result for each function on the actual installation, including relevant night conditions.
Event instructionsAction criteria, permissions and unclear/unavailable-video handling.A walkthrough showing the next action for representative events.
Contact testsPrimary and fallback routes, availability and handoff information.Completed authorized contact tests with any unresolved issues recorded.
Activation recordIncluded cameras/tasks, start time, open issues and responsible parties.A clear decision that identifies who is responsible before and after the handover.

Separate installation, testing and activation

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.

Keep access and account changes manageable

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.

Start with the account information you have

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.

Illustration of colleagues reviewing monitoring account instructions

Common questions

Before you bring an account on board.

Can we move accounts already monitored elsewhere?

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.

How long does onboarding take?

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.

What should stop an account from launching?

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.

Can we add sites after the pilot?

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.

What would you like
to hand over?

Share your company, client-site mix and coverage needs. Let’s work through the next step.

Illustration of a fictional monitoring specialist reviewing camera views
Your camera setupYour coverage hoursYour response plan