Customer

A customer is who you serve. Almost every operational record hangs off it: contacts, sites, assets, work orders, estimates, invoices, agreements, and portal invitations.

Where

Customers → Customers (nav.customers). Path /app/w/{workspace}/customers. Permission customers.view / create / update.

There is no customer number, slug, or external ID in the office UI — the record is identified by name (and email if you fill it).

Relationships

Customer
   ├── Contacts
   ├── Sites → Assets
   └── Work orders, estimates, invoices, agreements

The customer owns billing (tax number + billing address). It does not own the street the van drives to — that is a site. Dispatch uses the site, not this billing block.

Typical workflow

1. New customer — Person needs Full name; Company needs Company name. Status Active / Inactive.
2. Add at least one site before dispatching geography-sensitive visits.
3. Invite portal users from the customer’s Customer portal section only if portal is enabled. Email on the customer does not send an invite by itself.

Restrictions

Customers are not technicians. Public booking may match or create a customer by email; that is not a CMS user and not a portal identity.

If you created one customer per building: merge the relationship onto one customer and add sites. Invoices and agreements stay on the legal entity.

Office manual: Customers.