A tenant can report a plumbing issue without being the account's billing or authorization contact. Property-manager calls add another layer: the caller may manage several buildings but have different approval limits at each.
Capture the caller's role, actual service property, reported issue, and contact route. Then apply the plumbing company's approved authorization and escalation process. The receptionist should not decide who is legally responsible for repairs.
Define roles before changing records
Keep reporter, account holder, approval contact, payer, and access contact separate. A new tenant number should not overwrite the property manager's account number. An owner approving work does not necessarily become the person who can meet a technician onsite.
For managed accounts, maintain explicit property relationships and approved contact roles. Do not infer authority from the caller sounding familiar or knowing the address. Route uncertainty to staff while preserving the useful report.
Work through a fictional apartment request
A tenant reports a blocked fixture in Unit 7. The building is under a property manager's account, and the company requires manager approval before routine billable attendance. The tenant can coordinate access but cannot approve work under that account policy.
The agent records the issue and sends the request through the approved manager route. It explains whether attendance is pending. If the caller reports a concern covered by urgent instructions, the workflow follows that separate approved process.
| Caller situation | Required boundary |
|---|---|
| Tenant reports issue | Capture facts and access route |
| Manager requests attendance | Confirm site and approval scope |
| Owner changes billing details | Separate authorized update process |
| Unknown site under manager account | Review property relationship |
| Responsibility disputed | Staff route without legal conclusion |
Make approval delays visible
Track requests awaiting authorization separately from requests awaiting technician capacity. Staff can then contact the right person instead of repeatedly calling the tenant for a decision they cannot make.
Role-aware intake adds questions and may delay routine booking. It prevents billing confusion and avoids attaching a visit to the wrong managed property. The business can reduce friction through preapproved account rules, provided they are explicit and maintained.
Test two properties with similar names and a caller who changes the unit midway through the conversation. Review multiple-property handling for independent request identities.
Questions about managed-property intake
Can tenants receive arrival messages?
Follow the approved contact policy and role. Keep billing or unrelated account details out of access-only communications.
Should the agent create a new customer for every tenant?
Not automatically. Use the company's account model and a review path for uncertain matches.
What if the manager cannot be reached?
Record attempts and follow the approved pending or escalation process. Do not convert lack of response into assumed authorization.