Customer records
Add the occupant or beneficiary, link them to a property, and review their requests from the customer profile.
A customer in this guide is the person or company who occupies the property or benefits from the work. Their name appears on the request. This is not the billing organization — that is the account.
List and profile
On the customers list, search by name or mobile. Card view shows the total number of customers that match the current search and filters. A customer appears when they are assigned to the header branch, or when their unit is visible there — including a place shared with that branch. The branch badge is the assignment, not the unit. A resident who scans a QR code is not asked for a branch. Open the profile to see linked properties and maintenance requests. Activate or deactivate a selection from the list when those actions appear and your role allows them.
Add a customer with the name and mobile that should print on the request. Link them to the unit when they are a standing occupant so forms can suggest them. If a visitor only sends through a QR code, what they type on the form is enough — do not create a new record for every scan.
Tip: Mobile number is the key for contact and reminders. Use the correct country when the country list appears. Do not replace the occupant’s number with the office number unless that office is the agreed contact.
Import
For large lists, download the import template, review the batch, then submit. The template has an optional branch column — leave it empty to assign the header branch captured when you submit; a named value assigns that customer even if the header is elsewhere. Older files without the column still import. An unknown branch name fails that row only. Fix a row before you submit. Do not upload real contacts into a trial environment.
When not to add a customer
Do not copy a WhatsApp ping into a new record if the same mobile already exists. Search first. Do not store legal or payment disputes on the customer file; use the maintenance-request notes for field work.
What to read next
- Branches — the list follows the header branch; a visible unit still shows; QR does not ask for a branch.
- QR codes — how the occupant name appears on a scanned request.
- Maintenance requests — where the customer is written on a team-created request.
- Users and roles — a resident is not a dashboard user.