Skip to content

Help, answers, and contact

How can we help?

Search practical guidance, create a trackable ticket, or continue a conversation with Sales, Technical Support, or Billing.

Role-based training

Step-by-step walkthroughs

Choose a role to see the work normally performed by that user. The exact controls shown in your account depend on the capabilities your administrator granted.

Dispatch Company Administrator Complete initial dispatch organization setup Prepare the organization in the correct order before live dispatch begins.

WhereMaster context

Access neededDispatch Organization Administrator

  1. 1Open Organization Settings and confirm organization identity, timezone, labels, map defaults, refresh timing, and operational preferences.
  2. 2Create each Serviced Company with a recognizable name, code, color, logo, and timezone.
  3. 3Invite dispatch users and assign only the roles and capabilities required for their work.
  4. 4Configure governance defaults and any deliberate company overrides.
  5. 5Add dispatcher responsibilities and patrol-property access rules.
  6. 6Configure aid agreements, notification recipients, and SOP access.
  7. 7Enter a Company Workspace to add its officers, properties, vehicles, clients, and call types.
  8. 8Test Master CAD, each Company CAD, an officer login, GPS, emergency alerts, and notification delivery before going live.
Dispatch Company Administrator Create, edit, archive, or restore a serviced company Maintain a company while preserving tenant separation and historical records.

WhereMaster context → Administration → Serviced Companies

Access neededManage serviced companies

  1. 1Open Serviced Companies and select Add serviced company.
  2. 2Enter the company name, code, timezone, brand color, logo, and any available workspace labels.
  3. 3Save, then open the new Company Workspace and verify its identity banner.
  4. 4To change details, return to the company list, choose Edit, update the approved fields, and save.
  5. 5To stop new operational use while retaining history, choose Archive and confirm the correct company name.
  6. 6Use Restore when the same company should become available again.
Important

Archiving is safer than database deletion because calls, reports, audit history, and relationships may require retention.

Dispatch Company Administrator Invite, suspend, reactivate, or resend access for a dispatch user Manage dispatch-center personnel without sharing credentials.

WhereMaster context → Administration → Dispatch Users

Access neededManage dispatch users

  1. 1Open Dispatch Users and choose the invitation action.
  2. 2Enter the user’s real email address and select the appropriate organization role.
  3. 3Send the invitation and verify that it appears in the pending invitation list.
  4. 4Use resend or replace invitation when delivery needs to be attempted again; never send the raw token manually.
  5. 5Open an existing user to adjust authorized roles when responsibility changes.
  6. 6Use Suspend to immediately stop protected access while retaining audit history.
  7. 7Use Reactivate only after confirming the user should regain access.
Dispatch Company Administrator Create a custom role and authorize specific work Delegate administrative or operational actions using capabilities rather than passwords or broad role names.

WhereAdministration → Roles & Permissions

Access neededManage roles and permissions

  1. 1Open Roles & Permissions and review the built-in roles before creating another role.
  2. 2Choose Create role, enter a clear job-based name and description, and select Organization scope or Company scope as appropriate.
  3. 3Select only the capabilities required for that job, such as patrol assignment management or incident-report management.
  4. 4Save the role and return to the relevant user-management screen.
  5. 5Assign the role to the intended organization or company user.
  6. 6Have the user sign out and back in, then verify permitted and denied actions in the correct context.
  7. 7Remove obsolete role assignments promptly when duties change.
Important

Capability checks—not the displayed role name—control sensitive actions.

Dispatch Company Administrator Dispatch Supervisor Assign dispatchers to companies, officers, or properties Identify primary and secondary responsibility without hiding Master CAD information.

WhereMaster context → Administration → Dispatcher Assignments

Access neededManage dispatcher assignments

  1. 1Open Dispatcher Assignments and load the serviced company whose work is being assigned.
  2. 2Choose the dispatcher and then select a company, officer, or property target.
  3. 3Choose Primary or Secondary responsibility and save.
  4. 4Repeat for additional targets or backup dispatchers.
  5. 5Review the current responsibilities list and use filters to verify coverage.
  6. 6Change responsibility or remove an assignment when staffing changes.
  7. 7Ask the dispatcher to open My Assignments and confirm the expected workload.
Dispatch Company Administrator Set open patrol access or assign properties to individual officers Control whether every officer can patrol every property or receives a specific roster.

WhereMaster context → Administration → Patrol Property Assignments

Access neededManage patrol property assignments

  1. 1Open Patrol Property Assignments and load one serviced company.
  2. 2Choose Open to all company officers when every on-duty officer may receive every active mapped property.
  3. 3Choose Assigned officers only when each officer must receive a specific property roster.
  4. 4For each officer, check every property the officer should patrol and select Save roster.
  5. 5Repeat for the remaining officers and verify the assigned count shown on each card.
  6. 6Have an officer go on duty and start a new patrol route to verify only eligible properties appear.
Important

An already-active patrol route remains its original audited snapshot. Roster changes apply to nearby suggestions and the next route.

Dispatch Company Administrator Configure company change governance Choose which company changes are prohibited, require approval, or apply with notification.

WhereMaster context → Administration → Governance Rules

Access neededManage governance rules

  1. 1Open Governance Rules and review the organization defaults by resource and action.
  2. 2For each item, choose Not allowed, Approval required, or Direct with notification.
  3. 3Set company-specific overrides only when a company truly needs different rules.
  4. 4Save the rules and verify the effective behavior displayed for that company.
  5. 5Test one low-risk change from a company administrator account before enabling broader direct changes.
  6. 6Review notifications and change history to confirm direct changes remain visible to dispatch.
Dispatch Company Administrator Dispatch Supervisor Review, approve, or reject a company change request Evaluate proposed values before they become live.

WhereMaster context → Approvals & Changes → Pending Review

Access neededReview proposed changes

  1. 1Open Pending Review and select the request.
  2. 2Confirm the serviced company, requester, resource, action, reason, previous values, and proposed values.
  3. 3Check for warnings that the live record changed after the request was submitted.
  4. 4Approve only when the proposal remains correct and authorized; the application applies it transactionally.
  5. 5Reject with a clear reason when corrections are required.
  6. 6Open Change History to confirm the decision and application result were recorded.
Dispatch Company Administrator Dispatch Supervisor Create or edit an aid agreement Define eligible same-organization company assistance without exposing resources prematurely.

WhereMaster context → Administration → Aid Agreements

Access neededManage aid agreements

  1. 1Open Aid Agreements and choose Create.
  2. 2Select the requesting and assisting serviced companies within the same Dispatch Organization.
  3. 3Configure the agreement terms, permitted resources, activation limits, and expiration information.
  4. 4Save and review the agreement from both company identities.
  5. 5Edit the agreement when authorization changes.
  6. 6Remember that the agreement alone does not expose officers or vehicles; visibility begins only during an activation or qualifying emergency.
Dispatch Company Administrator Maintain organization settings, audit history, and API access Customize safe tenant settings and issue integrations without weakening isolation.

WhereMaster context → Administration

Access neededOrganization settings, audit logs, or API access as applicable

  1. 1Open Organization Settings, change only the intended labels, navigation, map, refresh, or feature preferences, and save.
  2. 2Open Audit Logs to filter by user, company, action, or date and export only when authorized.
  3. 3Open API Access to create a token with the smallest necessary ability set and an appropriate expiration.
  4. 4Copy a newly issued raw token once into the approved secret store; it cannot be recovered later.
  5. 5Revoke tokens immediately when an integration is retired or a secret might be exposed.
  6. 6Confirm tenant labels and identifiers remain present in audit exports and integration behavior.
Dispatch Supervisor Dispatcher Dispatch Company Administrator Operate the Master CAD across serviced companies Monitor calls, units, properties, officers, and emergencies without losing company identity.

WhereMaster context → Master CAD

Access neededView Master CAD; operational actions require additional capabilities

  1. 1Open Master CAD and verify the Dispatch Organization label.
  2. 2Review the company color legend, but always read the company text label because color is not the sole identifier.
  3. 3Use the map and call tables to review active calls, mapped properties, and on-duty officers.
  4. 4Filter or search when focusing on one company, priority, status, officer, or property.
  5. 5Open a call or unit in its displayed company context before changing operational state.
  6. 6Keep the CAD tab open, emergency audio enabled, and device volume audible.

Knowledge base

Help articles

Support ticketsHow Patrol Forge support tickets workCreate, track, and reply to a Sales, Technical Support, or Billing request.

Choose Sales for plans, demonstrations, and new-account questions; Technical Support for sign-in, setup, CAD, GPS, apps, and operational problems; or Billing for subscriptions, invoices, charges, and capacity changes. After you submit the form, Patrol Forge assigns a ticket number beginning with TKT so the request and every reply stay together.

Sign in before creating the ticket if you want it saved under My Support Tickets. Signed-in customers can open the ticket, read the conversation, see its current status, and send additional replies. Guest tickets are still delivered to the selected team by email, but they cannot be viewed inside an account or authorize support access.

Open means the ticket is awaiting review or has a new customer reply. In progress means a support representative is working on it. Waiting on customer means Patrol Forge has replied and needs more information. Closed means work is complete; closed tickets cannot receive replies or provide account access. You may close your own active ticket from its detail page when you no longer need assistance.

Email notifications may contain a link back to the ticket. Sign in using the same Patrol Forge account that created it. Never place passwords, payment-card numbers, or other secrets in a ticket.

For a Technical Support ticket, a signed-in customer may authorize one-time, read-only account access. You can verify your current Support Access Code or issue access limited to that ticket. Ticket access expires after seven days, after one use, or when the ticket is closed, whichever happens first.

Open My Support Tickets
Getting startedStart setting up your dispatch organizationThe recommended order for preparing a new multi-company dispatch center.

Create each serviced company first so its officers, properties, vehicles, clients, SOPs, and calls remain inside the correct company workspace.

Then invite dispatch users, assign capabilities, configure governance rules, and assign officers or properties. Test Master CAD and each Company CAD before live operations begin.

Getting startedUse the customer onboarding guideOpen the detailed customer handbook for setup, training, and daily operations.

The onboarding guide explains organization setup, users and roles, company resources, CAD, emergencies, aid, GPS, incident reports, client access, and troubleshooting.

Open onboarding guide
Account and accessTrouble signing inCheck the account email, password reset, verification, and workspace access.

Sign in with the email address connected to your account. Use Forgot password when needed, then check your inbox and spam folder for the reset email.

A verified account still needs active membership in a dispatch organization or serviced company. Ask your organization administrator to confirm your invitation, account status, and assigned access.

Account and accessUse your one-time Support Access CodeGet help inside your account without sharing your email password or Patrol Forge password.

Your Support Access Code is a private, one-time code that lets an authorized Patrol Forge Super Administrator or Support User open your account temporarily for troubleshooting. Support will never need your password. Do not send your password by email, contact form, text message, or chat.

To find the code, sign in to Patrol Forge and select My Support Code near the bottom of the application navigation. It is also available from the workspace-selection screen. Read the code to the authorized support representative only when you have requested assistance.

The code works one time. As soon as support uses it, Patrol Forge disables that code and automatically creates a new replacement code for you. Reusing, guessing, or entering the previous code will not open the account.

Support access is read-only. A noticeable banner remains on screen, account changes are blocked, access is audited, and the session ends automatically after 30 minutes. Support cannot use this process to open a Super Administrator or Support User account.

You can disable an unused code at any time by opening My Support Code and selecting Disable this code and generate a new one. If you did not request support or believe someone obtained your code, regenerate it immediately and contact Technical Support.

When creating a signed-in Technical Support ticket, you may instead issue an authorization that works only for that ticket. It expires after seven days, after one use, or when the ticket is closed—whichever happens first.

Open My Support Code
Account and accessMaster CAD versus Company WorkspaceKnow which workspace to use and why company switching is explicit.

Master CAD shows authorized activity across the serviced companies belonging to your dispatch organization. A Company Workspace limits the view to that company and clearly displays its name and identity.

Use Switch workspace in the left navigation whenever you need to change context. Opening a record never silently moves you into another company.

CAD and operationsEmergency alerts in CADEmergency activations stay visible across the dispatch workflow.

Keep CAD open, enable emergency sound, and keep the device volume audible. An officer emergency is designed to remain visually prominent across navigation until it is acknowledged and resolved.

Silencing sound does not acknowledge or close an emergency. Follow your dispatch center SOP for acknowledgment, response ownership, escalation, resolution, and closure.

CAD and operationsHow aid agreements affect visibilityA standing agreement does not automatically expose another company’s resources.

Cross-company operational visibility begins only during an authorized aid activation or emergency and ends when it closes or expires. Shared resources continue to display their home company.

Officer mobile and GPSOfficer duty status and GPS sharingLocation sharing is tied to an authorized officer login and active duty session.

The officer must use a login linked to exactly one officer profile for the company, accept the current legal acknowledgments, and select Go on duty.

Location permission must be enabled on the device. GPS sharing stops when the officer goes off duty or ends the location session. Device and browser power settings can affect background updates.

Officer mobile and GPSInstall an official Patrol Forge appFind currently available desktop and mobile application information.

Use the Apps page for official store links and platform availability. The hosted application stays current as website features are deployed, while native capability changes may still require a store update.

View official apps
Plans and billingPlans, limits, and add-on capacityReview how extra companies, dispatch users, and officers affect price.

Plan cards show included capacity and available monthly add-ons. Before checkout, the pricing estimate shows the projected recurring total and warns when moving to the next plan may be more appropriate.

For changes to an active subscription, contact Billing and include the dispatch company name and the capacity you want to add or remove.

Contact Patrol Forge

Create a support ticket

Choose the team that best matches your question. We will create a trackable ticket and securely notify the appropriate Patrol Forge team.

SalesPlans, demonstrations, and new accounts.

Technical supportSign-in, setup, CAD, GPS, apps, and operational questions.

BillingSubscriptions, invoices, charges, and capacity changes.

What happens next?You will receive a ticket number. If you are signed in, the request appears under My Support Tickets, where you can follow its status and reply. Guest requests are handled by email.

Prefer email? support@patrolforge.com

What can we help with?

Sign in before creating a Technical Support ticket if you want to authorize secure, one-time, read-only account access.