Customer CRM
Manage client profiles, billing names, contact details, tags, notices, reminders, jobs, invoices, batches, transactions and portal access.
See Customer CRMCustomer, property and service context
Build every job on clean customer and property data
DOP connects customer profiles, properties, service setup, pricing context, access notes, job history, invoices and portal visibility so the operation does not start from scattered notes.
Customer CRMProperty recordsService setupPortal visibilityJob history
Bring one customer with multiple properties, services and open invoices. We will show how DOP turns that into operational context.
1 customer
with properties, jobs, invoices and payments connected
1 property
with address, access notes, services and history
Less rework
before scheduling, dispatching or billing starts
Operational foundation
If customer and property data is messy, every workflow after it becomes risky
A job is only as reliable as the customer, property, service, notes and pricing context behind it. DOP makes that foundation visible before the team schedules work, dispatches employees, invoices the client or reviews payroll.
Avoid duplicate customer and property records that split history
Keep access notes, service instructions and billing context where the team actually works
Give office, field and finance teams the same operational source of truth
What DOP connects
A customer and property system built for cleaning operations
This is not a generic address book. It is the operating layer that feeds schedule, jobs, turnover work, invoices, payments and reports.
Property Records
Keep each service location tied to the right owner, address, access notes, property services, job history and map context.
See Properties
Customer Portal
Give customers and property managers controlled visibility into properties, work status, proof, invoices and payments.
See Customer PortalData to work
From client setup to reliable job context
DOP keeps the relationship, location and service setup connected so every operational action starts with the right context.
1
Create or verify the customer
Search by name, email or billing name before creating a new record so history is not split.
2
Attach the right properties
Connect addresses, property names, owners, access details and location notes to the customer.
3
Define services and context
Keep services, descriptions, price expectations and recurring instructions available before work is scheduled.
4
Use the record across DOP
Jobs, schedule, invoices, batches, payments and reports can all point back to the same customer and property context.
What the office can control before the job happens
The value of Customers & Properties is that it reduces guesswork before the work reaches the calendar, the cleaner or the invoice.
Search before duplicates
Find existing customers or properties before creating records that divide history and billing.
Address and access accuracy
Keep physical address, map context and entry instructions available for scheduling and field work.
Services by location
Connect services and location-specific details before jobs and recurring routines are created.
Operational notes
Store notes that protect execution: entry details, client preferences, billing context and warnings.
Invoice and payment history
Review invoices, batches, transactions and balances from the relationship context.
Controlled access
Decide when customers or property managers should receive portal visibility.
What stays under your control
Your office decides which customer owns each property
Duplicate records should be reviewed before merging or deleting history
Portal access remains controlled by your company
Service setup and pricing context should be reviewed before jobs or invoices are created
Customers & Properties FAQ
Why are customers and properties so important in DOP?
They are the operating base for jobs, schedules, invoices, payments, reports and client visibility.
Can one customer have multiple properties?
Yes. DOP supports customer records connected to multiple service locations and their own operational history.
Can properties store access notes?
Yes. Properties can hold address, access and operating context so dispatch and field teams do not guess.
Does every customer need portal access?
No. Your company controls who gets access and what visibility makes sense for the relationship.
Ready to clean up the base of your operation?
Bring one real customer with properties, jobs and invoices. We will show how DOP connects the records your operation depends on.
