Field service and property
Keep AppFolio resident and prospect conversations moving
Prospects and residents ask for help outside a property manager’s day. Bob answers from the property information you approve, uses the AppFolio context for that person and property, and prepares the leasing or maintenance follow-through.
Bob handles resident and prospect conversations with AppFolio property context, maintenance requests, leasing coordination, and team follow-through.
Carry the request from the first message to the team that owns it
A prospect asks about a listing, or a resident reports a problem. Bob explains the published property details, collects the unit, the request, and the urgency, and attaches that to the AppFolio record your team uses. Leasing gets a showing or application follow-up with the questions already documented. Maintenance gets a request the work-order process can accept. Staff approve the step that changes a lease, a unit, or a vendor assignment. The resident or prospect gets an answer and a next step instead of a voicemail.
Workflows
Guide the leasing conversation
Explain the approved property details and application steps, then capture the questions a leasing manager needs to finish the follow-up.
Use the property context
Answer from the property, unit, and resident information that belongs to the conversation, and point people to the portal path you publish.
Prepare maintenance and follow-through
Collect the property, unit, problem, and urgency, and hand the team a request they can turn into the work order.
Example workflow
Example workflow
A prospective resident asks about the published pet policy and a viewing. Bob gives the approved answer, collects the preferred time, and prepares the leasing follow-up with the original questions attached. Staff continue in AppFolio without asking the prospect to start over.
Illustrative example, not a live execution log.
Connection and setup
Connect AppFolio, approve the property information and intake fields Bob uses, and set which leasing or maintenance changes require a teammate’s approval.
How Bob turns a conversation into a useful next step
Bob starts with the customer's request and the business information you approve. When the workflow needs a current record, Bob retrieves it from the connected service. When the next step changes a record or sends a message, Bob follows the permissions and approval steps you configure. The customer gets a useful next response, and your team gets a clear handoff when a person needs to take over.
Questions
Does Bob work inside the AppFolio records our team already uses?
Yes. Bob uses the property, resident, and prospect context for the conversation, then prepares the leasing or maintenance follow-through your team approves.
Can residents keep the portal they already use?
Yes. Bob guides residents to the portal path you publish and still collects the context your team needs for follow-up.
Who decides what Bob can change or send?
You choose the records Bob reads and the actions he takes. A reply, a record update, or an outbound message follows the approval step you set for that workflow. See the pricing page for plans. This page does not list prices.
Continue this workflow with
These are related workflows, not prerequisites.
Get started with AppFolio
Tell us how your front office handles this job today. You send the message when you are ready.