Property Management Call Intake: Leasing and Resident Requests

This guide is for the team preparing calls about leasing, resident needs, and property follow-up. Initial call intake should establish what the caller is requesting and what information the next person needs. It is not applicant screening, a tenant background check, or a judgment about housing eligibility.

A leasing inquiry and a resident maintenance request are different uses of the phone agent. Choose a specific leasing intent for qualification entry; keep unrelated resident contacts in reception unless the business has deliberately configured an applicable entry. Additional entry methods converge on the same criteria, not independent leasing and maintenance decision trees.

This is a staff preparation checklist for a useful contact or message. It is not a claim that the agent can add these as extra qualification questions.

Illustrative configuration: a management team uses a specific new-leasing topic to start three ordered criteria. The team supplies its managed-property list and approved timing information. No applicant finances, background details, or protected personal characteristics are part of this screen.

Greeting, contact collection, the three criteria, the result, and the next action remain separate steps. Qualification supports exactly two or three criteria; this example uses three.

Synthetic example: a caller asks about a new lease, identifies a managed community, and reports timing that matches the team’s approved window. If the answers satisfy the configured rules, the initial result is qualified. A prepared tour or consultation booking can be attempted, with message taking as an available backup.

If booking is unavailable and a message succeeds, that is the completed action. A qualified path can also use a prepared live handoff when selected and ready. A not-qualified path can use prepared booking or message taking, but not live handoff. These alternatives stop after one succeeds.

Synthetic review record: New leasing inquiry; managed community identified; timing reported as matching; qualified result; tour booking unavailable; callback request saved for leasing staff. Verify the actual result and action in Inbox. This is not a reserved unit, an application decision, or a promised PMS update.

Contrast a resident saying, “The kitchen sink is leaking; please leave a message for the property team.” That request does not establish new-leasing intent. With Message Taking saved On, a caller can request a message in normal reception without first passing leasing criteria.

Synthetic resident message: Existing resident reports a kitchen-sink leak at their stated property, asks for the property team, and selects a callback number. If they state urgency, retain it as caller-reported. Qualification did not run; the requested message was saved. Review the dedicated Inbox message to distinguish a saved request from a completed response.

The agent does not determine whether a real emergency exists, decide a safety or habitability condition, guarantee dispatch, process a payment, or create a maintenance work order. Use business-approved response wording and established emergency procedures; keep professional and operational decisions with the responsible people.