Customer records for home builders

Maintain one structured customer record for contact details, address, status, portal access, notes, custom fields and the shared communication history.

Real Home Builder Software interface for Customer records for home builders

Customer records for home builders: how it works in Home Builder Software

One customer record serves sales, site and accounting instead of three versions of the same address. The list carries the customer number, contact details, town, portal status and a fully colored status, and the file behind it holds name, email, phone, address, country, status, portal release and notes. Company-specific custom fields sit directly underneath, together with the same activity log used across the product.

The customer is a fixed master-data relation, never free text and never a custom field, so a project stores the customer ID and reads name and number from the record itself. The searchable picker offers only active customers of the tenant and allows creating or updating one without leaving the form. A CSV or XLSX import maps name, email, phone and address, updates existing contacts by email address and gives every other row a new customer number.

The customer channel button opens the shared conversation, and the signed link shown there gives the customer secure access without an Home Builder Software account. Where a full portal login is wanted, an invitation or a twelve-character access code can be issued instead, and the customer then sees progress, dates, released files, invoices and messages while internal budget figures stay hidden. Because a prospect record becomes the active customer when a contract is won, the history reaches back to the first inquiry.

Address, status, portal release and notes in the customer file

The file is a single form: name, email, phone, street, postal code, town, country, status, portal release and notes. Name and country are required, everything else may stay empty, and notes take up to five thousand characters. The save button sits in the page head and submits the form from there, so a long file does not have to be scrolled to its end before it can be stored.

The portal release is a checkbox on this form and decides whether the customer can be given access to shared files and messages at all. Below the form sit the company's own fields for customers and the activity log, which looks the same on projects, leads, subcontractors and equipment: notes, meetings, minutes, photos, email and portal messages in one timeline.

A customer file keeps address, communication details and account information on one record.Open full-size screenshot
A customer file keeps address, communication details and account information on one record.

Finding a customer by search, status filter and sorted columns

The list searches name, customer number, town and email address in one field, filters by status and pages at twenty-five rows, the page size every list in the application uses. Sorting is limited to number, name, town and status, with name ascending as the default. The number is a link just as the name is, so the identifier is a way in wherever it appears.

The empty state distinguishes a list that holds no customer yet from a list a filter has emptied, and offers the way back in the second case. The contact import in the settings reads CSV, TXT and XLSX up to ten megabytes, shows a preview first, and then maps name, email, phone, street, postal code and town onto the fields of the record.

Where the customer record surfaces in projects, invoices and the portal

A project names its customer as the owner and carries a portal button in its head that opens the customer view directly. Estimates and proposals point at the same record, and the searchable picker on those forms shows the company’s customers while allowing a new one to be created without leaving the document. Invoices and payments inherit the address instead of keeping a second copy of it.

The customer channel opens the shared conversation between office and customer, and the signed link shown there gives access without an Home Builder Software account. For a full login an invitation is sent or an access code is issued instead. The customer then sees progress, dates, released files and invoices, while budget, cost groups and supplier figures stay internal, and the company releases the portal areas one by one.

The project portfolio shows current jobs with customer, management, phase and completion information.Open full-size screenshot
The project portfolio shows current jobs with customer, management, phase and completion information.

Customer records for home builders in the daily routine

The record usually starts in sales as a prospect attached to an inquiry, or arrives with an imported contact list. Office staff complete address, country and notes, add whatever custom fields the company defined, and decide whether the portal is released. Site and accounting then reuse the same record through the project link, so an address correction lands everywhere at once. When the customer writes into the channel, the message reaches the internal chat and the project history.

Read the documentation

Customer records for home builders: what it covers

  • Keep customer number, contacts, address and status in one record

  • Add company-specific fields without replacing core customer relationships

  • Open a customer channel and provide signed access without an Home Builder Software account

Customer records for home builders: questions and answers

Are customers stored as free text in projects?

No. Projects link to a tenant-filtered customer record with a stable customer ID.

Can a customer reply without an Home Builder Software user account?

Yes. A signed customer-channel link can provide limited access without an internal account.

Use Customer records for home builders on your own projects

Request a trial period for the workflow around this module. We agree the roles, permissions and useful scope with you before preparing access.