A property receptionist should identify whether the caller is reporting a repair, asking about a rental, or following up on an existing request before collecting a long set of details. These routes need different records and different staff owners.
Define administrative intents with the property manager. Keep maintenance, leasing, account questions, and concerns covered by approved escalation policy distinct. The agent should not decide tenancy rights, liability, or eligibility from a conversation.
Use the minimum intake for each purpose
Maintenance needs the actual property and unit, caller role, report, contact route, and routing context. Leasing needs the property of interest, viewing or information request, preferences, and approved contact route. Do not expose occupied-unit details while answering a prospective renter.
A caller can have more than one intent. Preserve separate tracked requests rather than overwriting the first route when the conversation changes.
Work through a fictional mixed call
A tenant reports a maintenance issue and then asks whether a larger apartment is available. The agent records the repair under the correct occupied unit and creates a separate leasing enquiry with the requested preference.
The repair does not become a leasing note, and the leasing team does not receive unnecessary maintenance detail. Each request has its own owner and status, even though both came from one call.
| Caller purpose | Required destination |
|---|---|
| New repair report | Maintenance request |
| Existing ticket follow-up | Linked maintenance update |
| Rental information | Approved leasing answer or enquiry |
| Viewing request | Leasing scheduling or preferences |
| Mixed purposes | Separate linked intents |
Keep commitments route-specific
A maintenance ticket is not a confirmed contractor visit. A viewing preference is not a reserved appointment. The agent should read back the actual next step for each route and avoid a generic “all sorted” ending.
A single shared intake form is easy to build but can collect irrelevant information and obscure ownership. Separate routes add configuration while reducing privacy exposure and staff sorting work. Start with the categories that materially change the next action.
Review unresolved requests by queue and owner. Test callers who mention a maintenance issue while asking about leasing, and callers who change the property midway through the call. See appointment states for the general commitment boundary.
Questions about property routing
Can the agent answer legal tenancy questions?
Route them through the manager's approved staff process. Do not improvise jurisdiction-specific advice.
Should every caller create a contact record?
Follow the business's data policy and actual purpose. General public questions may not require a persistent personal record.
What should staff see after a mixed call?
Separate requests with purpose, relevant property, approved contact route, current status, owner, and only the information each team needs.