A plumbing customer calls about a leak at one rental, but the office opens the record for another property. The phone number matches. The service address does not. Now the dispatcher has to untangle the booking while the owner searches old messages for the tenant’s details.
For US plumbing businesses serving landlords and property managers, plumbing multi-property CRM setup needs a clear rule: identify the customer, the service location, and the specific job separately. A trained VA can maintain those records and prepare bookings, while dispatch keeps control of the schedule and technicians handle technical decisions.
Separate the customer, property, and job
Start with three linked pieces of information. Your CRM may use contacts, opportunities, custom fields, or another approved structure. Confirm what your setup supports before changing records. The goal is a reliable relationship between the pieces, not a complicated database project.
- Customer or billing account: who requests work, who can approve it, and where approved invoices should go.
- Service location: the complete street address, unit or suite, city, state, and ZIP code where work happens.
- Job: the current request, its scope, assigned owner, appointment status, and next action.
A landlord can have several properties. A property can have several jobs over time. A tenant may be the access contact without being the payer. Keeping those roles explicit prevents a new tenant’s phone number from replacing the landlord’s billing details.
Use a minimum record standard
Build a short intake checklist the VA follows for every multi-property request. Require enough information to identify the correct job before it reaches dispatch:
- Customer or management company name and existing account reference.
- Verified service address, including the unit when applicable.
- Onsite contact name, role, and preferred approved contact method.
- Person authorized to approve work and the source of that authority.
- Billing recipient and any required purchase-order reference.
- Reported issue, date received, and link to the current job record.
- Assigned coordinator, next action, and due time.
Use a consistent job label such as “125 Example Street, Unit B | Kitchen drain | October request.” This is an illustrative format, not customer data. Put the full address in structured fields as well. A label helps people scan; it should not be the only place that stores dispatch information.
Keep door codes and other sensitive access details in a restricted location with appropriate permissions. Do not put them in broad task titles, marketing fields, or routine email subject lines.
Confirm the address on every new request
Searching by phone number is a starting point. It does not prove which property needs service. Have the VA ask: “Which service address and unit is this request for?” Read the address back before creating or updating the booking.
Search existing locations before adding a new one. Check spelling differences, abbreviations, and missing unit numbers. Never combine two properties just because the same landlord owns them. Never merge separate units because their street address matches.
If a customer says “the same place as last time,” confirm the actual address. If the caller cannot identify the property, assign a clarification task and leave booking unconfirmed. Urgent reports still follow the company’s emergency escalation procedure; record cleanup must not delay that escalation.
What this looks like in real life
Consider an illustrative plumbing office handling requests for a landlord with three rentals. The landlord emails about a kitchen drain at one address. A tenant later calls about a water heater at another. Both requests mention the landlord’s name.
The VA links both jobs to the same customer account, but records a separate service location and onsite contact for each. The drain job waits for an access confirmation. The water-heater request goes to the qualified team for assessment and scheduling decisions.
The landlord receives the appropriate approval request for each job. Tenants receive only the visit information relevant to their own property. Dispatch sees the address, issue, and contact together. No one has to infer the destination from whichever address happens to appear first on a contact record.
Check message fields before using automation
A reminder can pull the wrong address even when the correct address exists somewhere in the CRM. Review which record each message field reads. A contact-level address may describe a billing office rather than the current job site.
Before enabling a reminder workflow, test it with non-customer test records through an internal test destination. Include one account with multiple properties and simultaneous jobs. Confirm the message uses the intended service location, appointment, and recipient. Do not send test messages to customers.
Check replies too. The coordinator needs to know which job a response concerns. If the setup cannot reliably distinguish concurrent jobs, use a reviewed manual message until the configuration is fixed. Avoid sending tenants billing information or sharing one property’s appointment details with another occupant.
Give the VA a daily exception queue
A useful queue contains jobs missing an address, unit, onsite contact, authorization reference, or next action. The VA checks it at the start and end of the scheduled shift, resolves straightforward gaps, and routes disputed details to the designated manager.
Set a release rule: dispatch receives a booking-ready record only after the required fields are confirmed. The VA can flag readiness but must not decide technical urgency, expand approved work, or promise a technician slot without dispatch approval.
Measure missing-address exceptions, address corrections after booking, and jobs delayed by contact confusion. Establish your own baseline before claiming improvement. Track the reason for each correction so coaching fixes the intake step that caused it.
Start simple
Pilot this process with one active multi-property account. Map its current locations and open jobs, then check the details against authorized customer information. Preserve the original records and an audit trail before making corrections. Avoid a bulk merge or field rewrite until the proposed structure has passed a small test.
Use the BoostOps CRM discussion to define the record structure, task ownership, and message checks your operation needs. BoostOps CRM is $199/month. BoostOps also pairs a trained full-time Filipino VA with a fully set up CRM for $11.86/hour, billed monthly for a full-time VA. See pricing for the offers.
The VA + CRM approach gives the process an assigned operator and a shared system. BoostOps works as a revenue operations partner, helping connect intake, follow-up, and administrative ownership.
For the next steps in the workflow, use the plumbing property-manager authorization checklist to confirm who can approve work, and the plumbing job closeout process to keep field records connected to billing.
FAQ
How should a plumbing CRM handle one customer with multiple properties?
Keep the customer account linked to distinct service locations and individual jobs. Confirm the service address for every request instead of assuming the customer’s main address is the job site.
Should plumbing tenants and property managers share one contact record?
Keep their identities and roles separate. A tenant may coordinate access while a property manager approves work or receives invoices. Link the relevant contacts to the job without overwriting each other’s details.
Can a plumbing VA maintain multi-property CRM records?
A trained VA can confirm addresses, update approved contact details, assign clarification tasks, and check record completeness. Dispatch and qualified staff retain scheduling, technical, and work-approval decisions.
What should a plumbing office test before automating reminders?
Test an account with multiple properties and simultaneous jobs using internal test destinations. Verify the service address, appointment, recipient, and reply handling before sending automated customer messages.
Ready to stop sorting service addresses from scattered messages? Book a discovery call to map a practical plumbing intake and record-management process with BoostOps.