Skip to content
Learning Center Onboarding Service Provider

Service Provider Onboarding

Follow a guided setup path for organizing customer records, choosing a subscription, configuring account settings, adding users, setting up testing workflows, and helping your team find information faster in R2.

Before You Sign Up

Prepare Your Existing Customer Records

Before setting up your account, identify the customer locations, assemblies, assets, and team members you plan to manage. This helps you choose the right subscription and decide whether to enter records manually or use Data Import Services.

Estimate how many customer locations or service sites you will manage.
Review the assets and assemblies you need to track.
Determine how many team members require user accounts.
Identify active testers, gauge records, and certification details.
Decide whether you want R2 to import existing records for you.

Optional Setup Help

Data Import Services

If you already have customer records, locations, assets, or assemblies in spreadsheets or another system, R2 can help import supported record types so you do not have to add everything manually.

Learn About Data Import

Sign Up & Subscription

Choose the Right Subscription for Your Company

Service providers should choose a subscription based on location capacity, asset capacity, and user seats.

Location Capacity

Estimate how many customer locations or service sites you plan to manage. As your customer base grows, capacity can be adjusted at any time.

Asset Capacity

Estimate how many assets or assemblies you plan to track across all customer locations, including backflow assemblies and other equipment records.

User Seats

Review how many team members require their own R2 account and determine the appropriate access level for each person.

While subscription selection is primarily based on Locations, Assets, and User Seats, it is also helpful to consider how your company plans to use scheduling, routes, testing workflows, reporting, notices, customer management, and team collaboration.

Account Setup

Configure Your Company Settings

Before building records and service workflows, review your account settings and company preferences. Configuring these items early helps create a smoother onboarding experience.

Profile Settings

Review company profile details and make sure core account information is accurate.

  • Company name
  • Contact information
  • Business address
  • Service area details

Branding & Visibility

Configure how your company appears across supported areas of the platform.

  • Upload company logo
  • Configure branding
  • Visibility preferences
  • External access settings

Billing & Notifications

Review subscription-related settings and communication preferences.

  • Subscription management
  • Billing information
  • Notification preferences
  • Account communications

Users & Access

Configure User Seats and Access Levels

Each team member should have their own login. Service providers commonly use Admins for oversight, Managers for office operations, and Users for technicians or field personnel.

Administrator

Highest access level for full company oversight, setup, configuration, users, and records.

  • Full system control
  • Can manage users and records
  • Best for owners or administrators

Manager

Operational access for managing records, supporting users, and helping oversee daily service activity.

  • Can create and edit records
  • Can support field operations
  • Best for office managers or supervisors

User

Standard access for team members completing assigned work and interacting with relevant records.

  • Works with assigned records
  • Completes tasks and updates activity
  • Best for field staff or technicians
Primary account note: The email used to sign up becomes the primary account and first user in the system. This account should be used for top-level oversight and kept current.

Customer Records

Build Organized Customer Records

Service providers are often managing many customer locations, assemblies, and service records. Building organized records early makes it easier for office staff and field technicians to quickly find the information they need when work needs to be completed.

Location Contacts Assets / Assemblies Tasks

Create the Location Record

Create a location record for each customer property, facility, or service address. The location becomes a convenient place where your team can quickly find customer information, assemblies, service history, and active work.

  • Customer service address
  • Map and navigation support
  • Linked contacts
  • Easier technician access in the field

Add & Link Related Records

Connect the information your team needs before arriving on-site.

  • Customer contact information
  • Assembly records
  • Asset records
  • Related service history

Build Better Field Records

Supporting information helps technicians and office staff quickly understand a location before work begins.

  • Notes
  • Files
  • Photos
  • Notices
  • Service history
Locations, Contacts, Assets, and Assemblies are all primary records within R2 and can exist independently. However, many service providers choose to organize customer information around a Location record because it provides a convenient place to view customer details, service history, assemblies, assets, and active work in one place.

Cross Connection Module

Configure Cross Connection Workflows

If your company performs backflow testing, configure testing records before field work begins so testers, gauges, reports, and testing workflows are ready when work is assigned.

Add Testers & Link Gauges

Build tester records and associate gauges used for testing activity. Add tester certifications to tester files and calibration certificates to gauge files.

  • Tester certifications
  • Certification expiration dates
  • Gauge records
  • Calibration dates
  • Calibration certificates

Configure Testing Workflows

Configure the testing workflows and records your team needs to complete work accurately in the field.

  • OneTest access
  • Test report workflows
  • Customer reporting
  • Utility reporting
  • Compliance documentation

Tester Access

Testers may create a free account using the email associated with their Tester record. Testers are used for performing backflow tests and do not consume a user seat.

Why This Matters

Proper tester, gauge, and workflow setup supports accurate reporting, cleaner testing records, and ensures technicians have the information they need while performing work in the field.

Service Workflows

Develop Workflows That Help Your Team Find Information Faster

Once records are established, begin building workflows that support daily operations, field work, customer communication, and service history.

Customer Records

Maintain organized customer information across all service locations.

Tasks

Create, assign, schedule, and track work tied to customer locations, assets, and assemblies.

Routes & Rounds

Build technician routes and quickly locate customer sites in the field.

Service History

Review previous visits, notes, reports, and testing activity before arriving on-site.

Final Thoughts

Build Records That Support Your Team

The onboarding flow outlined on this page reflects our recommended setup process and is intended to help service providers establish a strong foundation within R2.

The most successful service providers use R2 to create organized customer records that make information easy to find. When locations, contacts, assemblies, service history, and tasks are connected, office staff can answer questions faster and field technicians can arrive on-site with the information they need already available.

Every company operates differently, and there is no single correct way to use the platform. Locations, contacts, assets, assemblies, tasks, notices, reports, and workflows can all be configured to support your company’s specific operational needs.

As you become more familiar with the platform, we encourage you to adapt R2 to fit your team’s processes, services, and field operations.

Explore our resources to learn more about platform sections, modules, workflows, and best practices.