Property management teams receive very different conversations on the same phone line. A resident may report maintenance, a prospective tenant may ask a general leasing question, and a vendor may return an office call. Start by identifying the purpose and property so that the next person can act without exposing another resident's information.
An AI receptionist should follow the management company's approved intake and routing rules. It should not decide eligibility, interpret a lease, disclose account information based on caller ID or replace the company's urgent response process.
Route by purpose and property
Establish which managed property the caller means and whether the request concerns maintenance, a general enquiry or an existing conversation. Properties may use different owners, vendors and on-call arrangements. A shared office number does not make those boundaries disappear. Keep the property supplied by the caller separate from a verified business phone-route label so an uncertain address does not silently change which organization receives the record.
Take a maintenance report without promising entry
Collect the property address, unit, callback details and a short description of the issue. Note a requested contact time and that access coordination is needed. Do not treat a caller's general statement as a completed entry authorization or save sensitive door codes in a routine summary. The authorized management team should confirm the required access and notice procedure using its own policy and approved communication channels.
- Property and unit, with corrections preserved.
- Caller-supplied relationship to the property.
- Reported issue and requested response.
- Assigned follow-up and unresolved access questions.
Separate recognition from authorization
A familiar phone number can help the team locate possible context, but a shared household phone or changed number is not reliable proof of identity. General office information can be answered from approved knowledge. Private resident records, payment details, lease changes and sensitive access requests should follow the company's verification and human review process. The assistant should not recite a resident's history merely because a number matches.
A fictional resident callback
Taylor contacts the fictional Westbank Property office about an unresolved maintenance request. Taylor gives an apartment number and asks whether a vendor will arrive tomorrow. A useful intake records the reference Taylor provides, the requested update and the contact preference. Unless a verified authorized source supports the answer, the assistant leaves arrival unconfirmed and creates a review task. It does not disclose another resident's work order or claim that the vendor accepted the visit.
Test permissions and escalation together
Rehearse a person calling on behalf of a resident, a wrong-property request and an urgent report. Define a clear fallback when the intended team is unavailable. Review who can see recordings and notes, and keep customer data scoped to the correct company. If a property platform will receive tasks, its adapter, field mapping and delivery result need separate verification. A website signup does not establish a property-management system connection.