Category: Company Settings
Audience: Admins, Dispatchers
Screen: Settings → Company → Defaults for New Customers
Most operators serve one state. Typing it into every customer and every
site address is pure repetition. Default State is the setting that
removes it.
This article covers what the setting does, every screen it reaches, how
site addresses decide between the customer's state and yours, and the
places it deliberately stays out of.
---
DS-1: Setting Your Default State
The card then shows the state as a badge, with the note "Pre-filled on
new customer and site addresses".
If you haven't set one, the card reads "No default state set" and
no pre-filling happens on any screen. Every State field starts blank,
exactly as it did before.
Only admins can change this. It is one value for the whole
organization, there is no per-user or per-territory variant.
---
DS-2: Where the Default Appears
| Where | What gets pre-filled |
|---|---|
| Add Customer (Customer Hub) | The State on the customer's Billing address and, when the service address is A different address, on that site's address |
| Add Site on a customer profile | The State on the new site's address, using the cascade in DS-3 |
| Booking form or one-off quote → Where is it? → Add a site | Same as above |
The Add Site path is shared, so it behaves identically wherever you
reach it from: the customer's Sites tab, the booking form or a quote.
---
DS-3: How Site Addresses Choose a State
A site belongs to a customer, and a customer's sites are nearly always
in that customer's own state. So sites use a cascade rather than always
using the company default:
If that customer is set up with a separate default service address,
the state on *that* address is used instead of their main one.
recorded.
Example. Your company default is OH. You open a Texas-based
customer and add a site, the State pre-fills TX, because their own
address is the better guess. Add a site for a customer whose profile has
no address at all and you get OH.
With no customer selected
Quotes and prospects can reach a site form before a customer is chosen. There is no customer to read from, so the form goes
straight to your organization's Default State. It does not error and does
not sit blank waiting.
---
DS-4: The Field Always Stays Yours
Pre-filling is a suggestion, never a constraint.
address, type over it. Nothing is locked and nothing warns you.
chosen a state, nothing replaces it, not a slow-loading customer
record, and not collapsing and reopening the "Add a new Site" form
mid-entry. What you picked stays picked.
job before you've touched the State field, the suggestion updates to
match the new customer.
is how you turn off the organization-level fallback everywhere.
---
DS-5: Where It Deliberately Does Nothing
Customer import
Import ignores Default State completely. Whether you upload a CSV,
paste a spreadsheet, or use AI paste, addresses are taken from your file
exactly as written. A blank State cell imports blank.
This is intentional. An import is a bulk operation you are trusting to
reproduce your file; quietly stamping hundreds of records with a state
nobody typed would put wrong data on records you believe came straight
from your source. Correct blanks in the spreadsheet before importing, or
fix the affected customers afterward from the Customer Hub.
Editing an existing address
Pre-filling applies to new addresses. Opening an existing customer or
site to edit it never rewrites the State already saved there, even when
that field is empty.
Leads
Lead capture forms, the internal New Lead form, the lead edit panel,
and public/embedded web lead forms, are not covered by this setting. A
lead saved without a state converts to a customer without one. If your
web form leads arrive stateless, set the state on the customer after
conversion.
---
DS-6: Troubleshooting
"The State isn't pre-filling anywhere."
Check Settings → Company → Defaults for New Customers. If it reads
"No default state set", nothing will pre-fill. Set a state and reopen the
form, an already-open form won't fill retroactively.
"It fills the wrong state on a customer's sites."
That is the cascade in DS-3 working as designed: the customer's own state
wins over the company default. Check the State on the customer's profile
address, correcting it there fixes every future site for that customer.
Type over the field for the one-off case.
"It stopped filling after I cleared the field."
Clearing the State makes the field empty, and empty is the condition for
filling, but only when the form is next opened. Close and reopen the
form to get the suggestion back.
"My imported customers have no state."
Expected, see DS-5. Import never applies the default.
---