How to Manage One Customer With Multiple Service Addresses

Keep one Customer record and separate service Locations, with a worked property example and a checklist for choosing the right address on each Job.

Daylane week schedule with field Jobs, Customers and service Locations
A real Daylane schedule with sanitised fictional example data.

Create a Location for each service address under the Customer who arranges the work. Give each Job the Location where that work will happen. This keeps a customer's contact details together while allowing different properties to have their own address and access notes. Check the Location again when booking a new Job, even if the customer is familiar.

Model the customer relationship before entering properties

In this fictional example, Example Property Services arranges maintenance at two buildings. It is one Customer with two Locations, because the same business is commissioning the work. The people opening each building can still be different. Do not treat a shared site contact as proof that two unrelated customers should share a record.

One fictional Customer with two distinct LocationsScroll for more columns →
CustomerLocation labelService addressJob
Example Property ServicesNorth office10 Example Street, Exampleville NSW 2000Inspect meeting-room door
Example Property ServicesSouth office20 Sample Road, Exampleville NSW 2000Replace courtyard tap washer

Add and check each Location in Daylane

Open the Customer record and add a Location with its street address, suburb, state or territory and four-digit postcode. A short label helps distinguish properties. Address line 2 can hold a unit or suite detail; access notes can describe a relevant site arrangement.

Before saving a Job, match its Location to the customer's request. Compare the full address, including unit details, rather than relying only on a label such as 'office'. A label is useful shorthand, but it does not replace the destination.

Do not repeat import rows to add extra addresses

Daylane's Customer CSV import can create one initial Location for each newly imported Customer. A matching existing email causes a row to be skipped, including its Location. Add additional Locations through the Customer record after import. Repeating the customer's email in several rows will not attach all those addresses.

Use the verified Customer CSV example

Keep a property change separate from a new property

If the customer takes on another building, add another Location. If an existing address contains a typo, verify and correct that record. Review upcoming Jobs after a change so the attending person has the intended destination. Avoid overwriting one property's address merely to reuse its label for a different site.

Sources and scope

An original operational guide from the Daylane team at Blu Mint Digital. Scenarios, durations and message wording are illustrative planning examples, not customer results or industry benchmarks. Product references were checked against the Daylane implementation on 5 September 2026. Adapt the workflow to your service, customer agreements and working conditions.

How we write and maintain our guides. Free templates and planning tools.

    Back to the guide library

    Put the next Job in a clearer place.

    Start with one user and unlimited manually scheduled Jobs.

    Start 14-day trial