Lesson 2 of 7 · 7 min

Custom fields for trades: equipment, system age, access notes

Add custom fields for trades: equipment, system age and access notes.

Read the lesson

Goal: Design a small set of custom fields that the office fills every time and that drive real campaigns.

You need: Settings → Contacts & Pipeline → Custom fields. The workshop sheet (Setup Sprint lesson 2).

Why this matters

Custom fields hold the facts that make a service business money later. The age of a furnace tells you when to offer a replacement. A gate code saves a tech 15 minutes at the curb. A water heater type tells you which customers need a flush offer.

But custom fields fail in two ways. Too many fields, and nobody fills them. Free-text fields, and the answers come in 10 spellings that no list can sort. Either way, the data is there but useless.

The rule is simple. Few fields, each with a fixed format, each tied to a use.

Pick the right field type

ServiceAgent offers 13 field types. They are Text, Long Text, Number, Date, Date & Time and Yes/No. Then Dropdown, Multi-Select, Email, Phone, URL, File Upload and Rating.

FactBest typeWhy
Equipment typeDropdownOne spelling for each answer
Install yearNumberYou can do math on it
Last service dateDateSorts by time
Access notes, gate codeLong TextFree words for the tech
Has petsYes/NoTwo answers only
Brands on siteMulti-SelectMore than one answer
Photo of the data plateFile UploadProof of model and serial

Use Text and Long Text only where a person will read it, not where a list will sort it. If you will ever filter, count or target by a field, it must not be free text.

Fig 1

Which field type?

  1. A fact the office will store
  2. Will you sort, count or target by it?YesPick a fixed formatNoText or Long Text, for a person to read; add Help TextEnds here
  3. Is it a year or an amount?YesNumberNoCheck the next question
  4. Is it a date?YesDateNoDropdown, Yes/No or Multi-Select
  5. Add Help Text, and Unknown for a Dropdown
If you will sort, count or target by it, it is not free text.

What goes where

Each field applies to an entity type. The choices are Contact, Company, Deal, Project, Service, Appointment, Ticket and Intake Form.

  • Facts about the home and its equipment go on the Contact, since the contact holds the address.
  • Facts about one sale go on the Deal, such as a lost reason or a financing need.
  • Facts about one visit go on the Appointment, such as "bring a ladder".
  • Facts customers give on the intake form page ("Sign & Complete") go on the Intake Form.

Each field also has a Key in snake_case and Help Text. It has three switches: Required field, Show in list views and Show in forms. Write Help Text for every field. It tells the office what a good answer looks like, right where they type.

A starter set by trade

Keep each trade to 5 to 8 fields at the start. Add more only when someone asks for a use. A field nobody reads is a tax on every call the office takes.

TradeStarter fields
HVACEquipment type (Dropdown), system install year (Number), filter size (Text), last tune-up date (Date), access notes (Long Text)
PlumbingWater heater type (Dropdown: tank gas, tank electric, tankless), water heater install year (Number), main shutoff location (Long Text), access notes (Long Text)
ElectricalPanel brand (Dropdown), panel amps (Dropdown), EV delivery date (Date), access notes (Long Text)
Cleaning and lawnPets (Yes/No), gate or door code (Long Text), visit frequency (Dropdown), special instructions (Long Text)

Filter size is Text on purpose. Techs read it; nobody sorts by it. The EV delivery date is a Date, because the follow-up task is due two weeks before it.

A limit to plan around

The Contacts filter reads Company, Status, Filter by Tags, Created From and Created To. It does not filter by custom fields.

So when a field should drive a campaign, add a matching tag. For example, say the install year shows a system 15 years or older. Then the office also adds the tag old-system. The tag drives the saved view and the campaign. The field keeps the detail.

Fig 2

A field that drives a campaign

  1. 1Install year field2011 or earlier
  2. 2Tag old-systemAdded by the office
  3. 3Saved view on the tagFilter by Tags
  4. 4Replacement campaignWorks from the view
The contact filter reads tags, not custom fields. The tag carries the field into a view.

You can also export contacts and sort by a field in a spreadsheet. That works for a one-time count, not for daily work.

Build it in ServiceAgent

  1. List the 5 to 8 facts the owner will use in the next year. Write the use next to each one.
  2. Go to Settings → Contacts & Pipeline → Custom fields.
  3. Click Add Field. Pick the type from the table above.
  4. Pick the entity type, such as Contact.
  5. Set a clear Key, such as system_install_year.
  6. Write Help Text, such as "4-digit year from the data plate".
  7. For a Dropdown, enter every allowed answer. Add "Unknown" as an answer.
  8. Turn on Show in forms so the office sees the field when editing.
  9. Leave Required field off for facts the office may not know yet.
  10. Check it works. Edit a test contact. Fill each field. Then search for it from another screen.
Fig 3

Adding the install year field

Add Field: install year (Number)

Apply to Entity TypesContact
Keysystem_install_year
Help Text4-digit year from the data plate
Show in formsOn
Required fieldOff
Add Field
Write Help Text for every field. It tells the office what a good answer looks like.

Fixing a free-text field

Many clients already have a free-text field full of mixed answers. You fix it in three steps:

  1. Create a new Dropdown field with the clean answers.
  2. Export the contacts. In the spreadsheet, map each old answer to a clean one. "tankles", "on demand" and "tankless" all become "Tankless".
  3. Import the clean column into the new field. Then retire the old field.
Fig 4

Water heater type, before and after

Free text
  • tankless
  • tankles
  • on demand
  • gas tank
  • Tank gas
Dropdown
  • Tank gas
  • Tank electric
  • Tankless
  • Unknown
Fix the spelling in a sheet, then import the clean column.

Making the old field required does not fix it. It was already filled. The problem was the spelling, not the blanks.

Worked example: Polar Air Services

Polar Air has 3,000 active customers in ServiceAgent. It adds a system_install_year Number field. The office fills it from old records and at every visit.

After 3 months, 2,400 of 3,000 contacts have a year. That is 2,400 / 3,000 = 80% filled.

In 2026, a system from 2011 or earlier is at least 15 years old. 2026 minus 15 = 2011.

The office exports contacts and counts years of 2011 or earlier: 432 contacts. That is 432 / 2,400 = 18% of the known systems.

Fig 5Example numbers

Polar Air's replacement list

3,000Active customers
2,400Install year known
432Year 2011 or earlier
13About 13 expected to replace this year (3%)
One well-built field turns into a replacement pipeline.

Each of those 432 gets the tag old-system. A saved view on that tag feeds the replacement campaign. Say Polar Air's average replacement is $9,500, and 3% of the list replaces this year. That is 432 x 3% = about 13 jobs. 13 x $9,500 = $123,500 of work, from one field the office filled.

Fig 6Example numbers

What the old-system list is worth

Contacts tagged old-system432
×Share that replaces this year3%
=Jobsabout 13
×Average replacement$9,500
Work this year$123,500
The rate and the job value are example inputs. Agree them with the owner.

Common mistakes

  • Free text for anything you will sort. Fix: use Dropdown, Number or Date.
  • 20 fields on day 1. Nobody fills them. Fix: 5 to 8 fields, each with a use.
  • No "Unknown" answer. The office guesses. Fix: add Unknown to every Dropdown.
  • No help text. Fix: write what a good answer looks like.
  • Expecting to filter by a field. Fix: add a matching tag for campaign use.

Do this now

Write the starter set for one trade, with a use for every field. Build it in your practice account. Fill it on 5 test contacts. Then add one matching tag and save a view on it.

Practice the conversation

  1. Operator Which facts about a home make you money later?
  2. Owner Age of the system, mostly. Old ones get replaced.
  3. Operator Then we store the install year as a number, not a note.
  4. Owner My guys write it in the notes now.
  5. Operator Notes can't be counted. A number field can.
  6. Owner What do I get from counting?
  7. Operator A list of every system 15 years or older. That's your replacement list.
  8. Owner How many fields will my office have to fill?
  9. Operator Five. Each one has a job, or it doesn't go in.

Quick check

  1. A plumbing shop stores water heater type as free text. Answers include "tankless", "tankles" and "on demand". What is the fix?
    • Make the field required
    • Add a second free-text field
    • Change it to a Dropdown, then clean the old answers
    • Store the age instead
  2. You want a saved view of all homes with an old system. The install year is a Number field. What else do you need?
    • A matching tag, because the contact filter cannot read custom fields
    • Nothing; the filter reads every field
    • A Long Text copy of the year
    • A new pipeline
  3. 2,000 contacts have an install year. 15% are 15 years or older. 5% of those replace this year at $8,000 each. What is the revenue?
    • $120,000
    • $160,000
    • $240,000
    • $80,000

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community