Overview
Compare providers by what happens after the resident describes a problem. Ask each one to demonstrate the record it creates, the person authorized to act, and how the resident learns the next step. A captured message, a vendor request, and a completed repair are different outcomes.
Choose the work you are buying
Write down whether you need message taking, contact escalation, work-order entry, or approved vendor coordination. Ask each provider to mark those responsibilities as included, separately configured, or unsupported in its proposal. Keep leasing inquiries separate from existing residents’ maintenance requests so an available-unit question does not enter the repair queue.
Buildium’s maintenance course distinguishes request tasks, work orders sent to vendors, and communication tools. Use that distinction when reviewing a proposal: access to a property platform does not establish which of those actions an answering provider can perform for you.
Require a demonstration in the correct property record
Prepare a fictional resident request with a property identifier, unit, callback contact, and approved issue description. Ask the provider to show where it would record the request and how your team would find it the next morning. Then introduce a second property with a different contact rule. Compare the resulting records rather than accepting a generic claim of integration.
AppFolio’s resident help describes maintenance submission with photos, entry permission, and preferred times, and notes that the feature may not be enabled. These are platform-specific examples, not AnSer capabilities. Confirm which relevant details your proposed telephone workflow can preserve and which must be collected through another approved channel.
Put authorization in the proposal
Supply the property-specific vendor list and identify who may approve a callout or expense. Ask what happens if the vendor cannot attend, the request falls outside the approved rules, or the provider cannot reach the manager. Do not let a demonstration quietly replace your authorization process with the vendor’s preferred default.
Compare a repeat request and a status question
In the proposed demonstration, have a resident call about a request already entered through the portal. Ask how the answering team finds the existing record, adds the update, and avoids sending a second vendor for the same work. If access is unavailable, the proposal should identify who reconciles the message.
AppFolio documents resident-facing stages from receipt through technician contact, scheduling, and completion. Ask which status the answering team can actually verify before speaking to a resident. Contacting a technician should not become a promised appointment or a claim that the repair is finished.
Compare the written scope and commercial terms
- Use the same fictional requests for every provider and record demonstrated, not demonstrated, or outside scope.
- Ask how account setup, property-rule changes, repeat calls, transfers and work-order entry affect the quote.
- Confirm who maintains property instructions and how urgent changes reach the team.
- Identify who reviews unresolved messages at shift change and who sends resident updates.
- Retain the approved scope, exceptions and test findings alongside the proposal before making a selection.
