FieldCamp

Customers — The Core Customer Record | FieldCamp

The FieldCamp Customers record holds every person and company you serve. See its fields, how it connects to Jobs, Estimates, and Invoices, and its lifecycle.

A Customer is the person or company you do work for, and it sits at the top of the FieldCamp data model.

Everything else in the system traces back to it: the requests they send in, the jobs you run for them, the visits your crews make, and the estimates and invoices you bill them on.

Every new FieldCamp account ships with the Customers record already enabled, connected to the other core records, and running a default lifecycle, so you can start adding customers and booking work on day one.

From there the record bends to your business — add your own fields, redefine the stages, and rearrange the customer page to match how you actually track accounts.

The same record serves any size of operation, from a single-truck operator to a multi-location franchise, residential or commercial.

What a Customer record captures

The Customer page renders a focused set of fields that cover who the customer is, how to reach them, where their work and billing addresses are, and a running tally of their account activity.

The table below lists the fields that appear on a Customer out of the box.

FieldWhat it is
First nameThe customer's first name. Required.
Last nameThe customer's last name.
EmailThe primary email for the customer.
PhoneThe primary phone number.
WebsiteThe customer's website, for business accounts.
CompanyThe company name, for business accounts.
TAX numberThe customer's tax registration number.
Customer typeIndividual or business.
StageWhere the customer sits in their lifecycle (New Lead, Active Client, and so on).
AddressThe customer's main company address.
Property addressWhere the work is typically done.
Billing addressWhere invoices are sent.
Preferred techniciansTeam members this customer prefers to send.
NotesFree-text notes about the account.
Job formsForms or checklists attached to this customer's work.
Lead sourceWhere the customer came from — website, referral, advertisement, and so on.
Customer sinceWhen the customer became active.

A Customer page also shows an At a glance strip of running totals, drawn automatically from the customer's work and billing. These are read-only — FieldCamp keeps them current as jobs and invoices move.

At a glanceWhat it shows
Total jobsHow many jobs this customer has, lifetime.
Open requestsHow many of their requests are still open.
Total invoicedThe lifetime value billed to the customer.
OutstandingWhat the customer still owes.
Last paymentThe date of their most recent payment.

FieldCamp keeps additional account details on a Customer behind the scenes — such as default payment terms, an account classification, and credit-hold controls — that flow down to new requests, estimates, and invoices without appearing as editable fields on the page.

How Customers connect

A Customer is the parent record for almost everything a field service business does. It owns the requests it submits, the jobs it asks for, the tasks tied to it, and the estimates and invoices it is billed on.

The diagram below shows the records a Customer connects to directly.

Read the connections outward from the Customer:

  • One Customer can have many Requests, but each Request belongs to exactly one customer.
  • One Customer can have many Jobs, and a Job is carried out as one or more Visits in the field.
  • A Customer is billed on Estimates and Invoices — a quote can become a bill, and an approved estimate or a request can turn into a job.
  • A Customer can have many Tasks, can have Job Forms attached, and can list preferred technicians to send.
  • Every change to a Customer is written to its history, so you always have a record of what changed and when.

Because the Customer owns the records below it, deleting a customer is treated with care: the work and billing tied to that customer come along with it rather than being orphaned.

In practice you will rarely delete a customer outright — moving them to the Inactive or Archived stage keeps their history intact.

The Customer lifecycle

Every Customer moves through a default lifecycle of four stages, from a brand-new lead to an archived account. You can move a customer freely between any of these stages as the relationship changes.

New Lead

A new customer starts as a New Lead — someone who has come in but does not yet have active work. This is where website inquiries, referrals, and imported contacts land.

Active Client

Once you start doing work for them, move the customer to Active Client. This is the working state for any customer with live jobs, open requests, or recent billing.

Inactive Client

A customer you are no longer actively serving — but want to keep on file — moves to Inactive Client. Their full history stays intact, and you can reactivate them at any time.

Archived

Archived is the final stage, for accounts you want out of your day-to-day lists while keeping their records. An archived customer can be reactivated if they come back.

A new customer must have a first name, and any email you enter is checked for a valid format. Beyond that, the Customer record is deliberately light at creation so you can capture a lead fast and fill in the rest later.

On the Customer page

This page comes with an out-of-the-box layout, built from building blocks. If you want to customize the blocks — reorder, add, hide, or group the sections below — you can. See Record layouts & building blocks.

The Customer page opens on the Details tab, with a wide main column for the customer's summary and a sidebar for the facts you reference most.

The other tabs gather everything the customer touches — their jobs, billing, files, and conversations — so the page doubles as the full account view.

The Details tab reads top to bottom:

  • Header — the customer's name (falling back to the company name), their company as a subtitle, a stage pill, and the customer's actions: Add Job, Add Task, Add Estimate, Add Invoice, Call, SMS, and Delete.
  • At a glance — the running totals: total jobs, open requests, total invoiced, and outstanding.
  • AI summary — a written summary of the account.

The sidebar carries the reference details:

  • Contact — first name, last name, email, phone, company, and customer type.
  • Financial — outstanding balance, total invoiced, and last payment.
  • Addresses — the property, billing, and company addresses.
  • Additional — website, tax number, preferred technicians, job forms, lead source, and customer since.
  • Custom properties — any fields you have added to the Customer.

The remaining tabs gather the customer's related records:

  • Jobs, Invoices, Estimates, Requests, Products, and Tasks — each a table of the customer's records of that type, with a button to add a new one.
  • Files — a full file manager for the customer's documents, with folders and uploads.
  • Emails, Calls, Messages, and Billing info — the synced email thread, call history, text conversation, and payment history for the customer. These tabs appear once the matching integration is connected; until then, each shows a prompt to connect it.
  • Events and Job Forms — calendar events linked to the customer and the forms attached to their work.

The Customer page is the single place to see a whole account — who they are, every job and invoice, and every call or email — without leaving the record. That is what makes it the natural home base for dispatchers and office staff.

Make it your own

The Customer record is the starting point, not the limit. Every part of the record can be tailored without disturbing the connections underneath.

Built for any size

The same Customer record serves a single-truck operator and a multi-location franchise. A one-person plumbing business uses the customer record as-is: a name, a phone, a property address, and a stage.

A growing electrical contractor adds a few custom fields and an extra stage. A multi-location or franchise operation runs the same customer lifecycle across every location, with each site's customers kept under its own structure.

Residential or commercial, the record is the same set of building blocks — ready on day one, and yours to tailor.

See also

More in the FieldCamp data model.

Hands-on, step-by-step guides from the rest of the FieldCamp documentation.

On this page