The GuardDog field guide

Set up your fleet.
Plan the response.

Watch the real controls, then follow the setup guide. You'll know who gets the first text, what triggers a call, and where to check the response.

Jump to the setup guide

Inside GuardDogReal product UI · Sample data

Find the incidents that need you

Read the dashboard, open Events, and filter for unresolved incidents.

Learn by watching 03 lessons

Screen recordings of the GuardDog application with sample fleet data. No audio required.

Read this lesson

Start on Dashboard. The top row separates acknowledged events, work in progress, and unresolved incidents.
Open Events to see each incident with its status, severity, branch, and unit.
Use the status filter to show Unresolved. These incidents still need your team to follow up.

Download video

Branches

Create your organization and branches

Create your GuardDog account and organization. Open Branches and add a branch for each team that needs its own contacts or alert rules.

Give branches names your team recognizes, such as Denver or North yard.
A unit is the vehicle or equipment you monitor. Add units to the branch responsible for responding.

Create your account

Integrations

Connect your camera provider

Open Integrations and choose your provider. The credentials and webhook setup differ by provider, so follow the matching guide before assigning devices.

Discover or enroll devices using the provider setup flow.
Assign the devices to the correct branch and unit. Discovered devices become billable when assigned as monitored units.
Check delivery diagnostics for incoming events. Video access can require separate provider permissions.

Choose your provider guide

Branches / Select a branch / Contacts and Call Chain

Choose who should respond

Save your responders in the branch contact directory. In Call Chain, add those saved contacts in the order GuardDog should try them.

Put the person responsible for the first response at the top. Add backup contacts after them.
Configure corporate contacts for escalation after branch contacts.
An assigned driver is separate from the escalation contacts. Optional driver coaching calls do not replace the manager response chain.

Watch the contact walkthrough

Alerting

Decide when to text and when to call

Set the organization defaults, then adjust branches or units that need different alert categories. New organizations start with distraction alerts; choose the other categories you want to act on.

Select which camera event categories create alerts. Unselected categories remain recorded in Events.
Choose which alert categories may escalate to $1 phone calls. This does not enable alerts for categories you left off.
Set the text acknowledgment wait, between 5 and 900 seconds. The built-in default is 120 seconds; your deployment or branch may override it.
Set the monthly phone-call budget. When it is reached, texts continue and paid calls are skipped until the next UTC month.

Watch the alert settings walkthrough

Dashboard and Events

Check the response, then follow up

The dashboard separates acknowledged incidents, work in progress, and unresolved incidents. Open Events to filter by status, branch, or unit.

Open an incident to review its details, available footage, and communication history.
Acknowledged means a person responded. It does not mean the safety issue itself has been resolved.
If you send a test event, use a test branch and contacts expecting the alert. Test events can send real texts and place paid calls.

Watch the incident walkthrough

Put your response plan to work

Connect your cameras.
Set your response plan.

Connect your cameras. Choose your contacts. Let GuardDog start the follow-up.

Get started $10 per unit / month. Optional calls at $1 each.Talk through your fleet setup

Set up your fleet.Plan the response.

Product walkthroughs