Overview

AgileField supports unlimited levels of customer hierarchies within the system.  Many of our clients have customers with multi-level hierarchies like a headquarters, division, and individual locations under those.  This way it is easy to track all work done for a particular location, all work done for the division, an all work done for the HQ.  


There are multiple ways to configure the system from a reporting and billing perspective, so you should focus on setting up your hierarchy in a way that the field technicians arrive at the correct location with all the information they need (job history, real-time updates, etc...)



Quick Terminology

  • Customer Type: This is a user defined field that is used for groupings and reporting in the system.  (Ex: "Division" or "Location")
  • Parent Customer: This is how AgileField set up the hierarchy within the system.  There is no limit on how many levels deep the hierarchy can go.  (This example uses a 3-tier hierarchy)



Real-Life Example: Home Builders

Many AgileField clients perform work for Home Builders and typically use the terms (Customer Types) "Builder", "Community", and "Lot" in their hierarchy. 




Grandparent Customer Record (Builder)

In this example, the highest level in the hierarchy is a "Builder".  Under the builders are communities and lots, respectively.  Below is the Custom Record for a builder, "Ashton Woods Atlanta".  

  • This is indicated in the Customer Type field.


Parent Customer Record (Community)

In this example, the next level in the hierarchy is the "Community".  Under the communities are lots.  Below is the Customer Record for a community, "Aria West".  

  • This is indicated in the Customer Type field.  
  • The builder is stored in the Parent Customer field.


Child Customer Record (Lot)

The system supports unlimited levels, but in this example, the lowest level in the hierarchy is the "Lot".  Below is the Customer Record for a lot, "Aria West Lot 15". 

  • This is indicated in the Customer Type field.
  • The community is stored in the Parent Customer field.


So, now our structure looks like this:



Customer Hierarchy Benefits in AgileField

Reporting

  • Report on information across multiple hierarchies: Builders, Communities, and Lots
  • Filter information by Grandparent Customer(s), Parent Customer(s), Child Customer(s), etc...

Billing & Accounting Integration

  • Sync job information to your Accounting or ERP system to keep hierarchies in tact
  • Make sure information for billing is passed to the correct Customer in the hierarchy
    • It is common that a builder will be the customer to bill on a job for a community and/or lot in the hierarchy

In the Field

  • Ensure field techs arrive at the correct locations to perform the job
  • Give field tech all relevant information including customer details, job history, equipment on site, etc...