Ops & Supply

How to triage property maintenance requests as Property Management Founders

Ops & SupplyFor Property Management Founders3 apps12 steps~24 min to set up

Maintenance requests arrive through three channels simultaneously: tenants text your personal cell, others email the office, and a third group submits through your AppFolio or Buildium tenant portal. Your property manager screenshots the texts, copy-pastes the emails, and manually logs everything into the PMS — if they remember. Urgent repairs (no heat in January, water leak) sit in the same queue as 'lightbulb is out.' You have a preferred vendor list but it lives in someone's head or a shared Google Sheet. When the owner calls to ask why the HVAC repair cost $800 and took five days, you're digging through emails to reconstruct the timeline. You're managing maybe 200-400 doors and this is already consuming 2-3 hours a day.

Build this on Starch → See the apps used

Ops & SupplyFor Property Management Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A single triage inbox that ingests maintenance requests from email and your tenant portal, categorizes them by urgency and trade type (HVAC, plumbing, electrical, general), and routes each ticket to the right vendor contact — without your team manually reading and sorting every one

An automated status-update workflow that messages tenants with confirmation and estimated response time when a ticket is received, so your phone stops ringing with 'did you get my request?'

A weekly digest surfaced to you and property owners showing open tickets, average days-to-close by trade, and which vendors are completing work fastest — pulled from your email history, no separate spreadsheet required

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Email Agent Task Manager Project Management

Data sources & config

Starch connects directly to Gmail (scheduled sync — messages refresh on a schedule and live in Starch's database) to read inbound tenant maintenance emails. Your AppFolio or Buildium tenant portal is reached through browser automation — no API needed — so Starch can read submitted portal requests and post status updates back. Your vendor contact list lives in Google Sheets, connected from Starch's integration catalog and queried live when a dispatch task is created. Task Manager and Project Management apps track open tickets and completion status inside Starch.

Prompts to copy

Watch my Gmail inbox for emails with subjects or bodies containing words like 'repair,' 'broken,' 'leak,' 'not working,' 'heat,' 'AC,' 'maintenance request.' When one arrives, extract the property address, unit number, issue description, and tenant name. Categorize urgency as Emergency (no heat, active water leak, no hot water, security issue), Urgent (appliance failure, pest, HVAC not cooling), or Routine (cosmetic, minor fixture). Create a task for each request with those fields and assign it to the correct property manager based on this address-to-PM mapping: [paste your list].

Every Monday at 8am, send me a summary of all open maintenance tasks grouped by property, including how many days each has been open and which ones have passed 5 days without a vendor assignment.

When a new maintenance task is created, draft a reply to the tenant's original email confirming receipt, stating the urgency category, and giving an expected response window (Emergency: 2 hours, Urgent: 24 hours, Routine: 3-5 business days). Show me the draft before sending.

Create a project called 'Vendor Dispatch — Q2 2026' and add a task for each open maintenance ticket. Group tasks by trade type: HVAC, Plumbing, Electrical, General. Tag each task with the assigned vendor name from this list: [paste vendor list with trade and contact].

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect your Gmail account — Starch syncs your messages on a schedule, so the agent reads new tenant emails without you forwarding anything manually.

2 If your tenants submit through AppFolio, Buildium, or Rent Manager's tenant portal, Starch automates that portal through your browser — no API needed — and pulls submitted requests on the same schedule as your email check.

3 Paste your address-to-property-manager mapping and your vendor roster (trade, name, phone/email) directly into the setup prompt. Starch stores this as the routing logic for every new ticket.

4 Tell Starch what urgency tiers mean for your firm (you likely have a lease clause and a state statute on emergency response times). The agent applies your definitions, not a generic template.

5 For each inbound request, Starch creates a task in Task Manager with property address, unit, tenant name, issue description, urgency tier, and the email thread link — so your property manager sees the full context without opening Gmail.

6 Starch drafts a tenant acknowledgment email for your review — showing urgency category and response window — and sends it once you approve, or automatically if you configure it that way.

7 When the task is assigned to a vendor, Starch drafts the vendor dispatch message with property address, unit access instructions (pulled from your notes), and the tenant's description verbatim — reducing phone tag.

8 Starch's Project Management app groups open tickets by trade type so you can see 'I have 4 plumbing jobs open across 3 properties this week' without scrolling through individual tasks.

9 When a vendor marks a job complete (via email reply or your portal), Starch detects the closure language and updates the task status, logging the close date and actual duration.

10 Every Monday morning, Starch emails you and your property owners a maintenance digest: open tickets, days open, vendor assigned, and any tickets that breached your SLA window — formatted per owner so each owner only sees their properties.

11 Monthly, run a prompt like 'Show me average days-to-close by vendor over the last 90 days' to see which trades and vendors are slow — data for your next vendor contract negotiation.

12 If a repair escalates (tenant threatens habitability claim, issue recurs at same unit), Starch flags it in the project view and surfaces the full email history so you have documentation ready.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

March 2026 — 12-unit building, Harrison Street property

Sample numbers from a real run

Emergency — No heat (Unit 4B)	1
Urgent — Dishwasher not draining (Unit 2A)	1
Routine — Bathroom faucet drip (Unit 7C)	1
Routine — Screen door damaged (Unit 1A)	1
Urgent — HVAC not cooling (Unit 9B)	1

On March 4th at 11pm, a tenant in Unit 4B emails 'furnace is making a clicking sound and won't turn on.' Starch picks it up in the next Gmail sync, categorizes it as Emergency (no heat), creates a task assigned to your HVAC vendor Miguel, drafts a tenant reply confirming 2-hour response, and pings your on-call property manager in Slack — all before anyone wakes up. Miguel is dispatched by 7am. The repair costs $340 and closes in 14 hours. Meanwhile, Unit 2A's dishwasher request came in through the Buildium tenant portal — Starch's browser automation read it at the same sync, routed it to your appliance vendor, and sent the tenant a 24-hour acknowledgment. By Monday's digest, your owner sees 5 open tickets, 1 closed (Unit 4B — 14 hours, within SLA), 4 in-progress, and average days-to-close for March sitting at 3.2 days across all trades. No spreadsheet was opened. The owner's email took Starch 90 seconds to draft and you 30 seconds to send.

Measurement

How you'll know it's working

Average days-to-close by trade (HVAC, plumbing, electrical, general) — your benchmark for vendor contract renewals

SLA breach rate: percentage of Emergency tickets not responded to within 2 hours, Urgent within 24 hours — a liability metric, not just an ops metric

Tickets per door per month — rising numbers signal a building that needs capital investment, not just maintenance management

Repeat tickets at same unit within 90 days — indicates a fix that didn't hold, worth tracking before a tenant escalates to habitability

Owner-reported maintenance satisfaction (pulled from any owner survey you run) — the metric owners actually bring up in renewal conversations

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

AppFolio / Buildium native maintenance module

Handles in-portal requests well but doesn't read email or text, so you're still manually entering requests that come in off-portal and there's no cross-channel triage.

Latchel or Rentvine maintenance coordination

Purpose-built for maintenance dispatch but adds a per-door monthly fee on top of your PMS cost, and it won't connect to your existing Gmail threads or generate owner-facing digests from your own data.

Manual email + shared Google Sheet

Zero tool cost, but your property manager is spending 60-90 minutes a day on triage that doesn't require human judgment, and the sheet is always a version behind.

Zendesk or Freshdesk

Robust ticketing but built for software support teams — property-specific fields like unit number, lease status, and vendor routing need significant custom configuration, and the per-seat cost adds up fast for a small PM firm.

On Starch RECOMMENDED

One platform — email agent, task manager, project management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

My tenants submit requests through Buildium's tenant portal, not email. Can Starch read those?

Yes. Starch automates your Buildium portal through browser automation — no API needed. It logs in, reads submitted requests on a schedule, and pulls them into the same triage queue as your email-based requests. Your tenants don't change anything about how they submit.

We use AppFolio for work orders. Will Starch conflict with that, or replace it?

It doesn't replace it. The typical setup is: Starch handles intake triage and routing (reading email + portal, categorizing, notifying vendors), while AppFolio remains your system of record for work orders. Starch can post updates back to AppFolio through browser automation, or you can keep them in sync manually. Most property managers use Starch to eliminate the 60-90 minutes of daily sorting and drafting, not to replace the PMS.

What if a tenant texts my property manager's personal cell? Can Starch triage that?

Not directly from SMS today. The practical fix most PM firms use: set up a Google Voice or similar number that forwards to email, then Starch reads the email. Alternatively, your property manager can forward texts to a dedicated Gmail address that Starch watches. It's a one-time setup change, not an ongoing workaround.

Is Starch SOC 2 certified? We handle tenant PII and owner financials.

Starch is not SOC 2 Type II certified today. If your firm has a compliance requirement that mandates SOC 2 for third-party tools, that's worth weighing. Most small PM firms under 500 doors aren't bound by that requirement, but it's worth knowing before you connect sensitive data.

We have about 15 preferred vendors across 5 trade categories. How does routing work?

You paste your vendor list into the setup prompt — trade type, vendor name, contact info, any coverage notes (e.g., 'Miguel HVAC: call first, don't email after 9pm'). Starch stores that as routing logic and applies it to every new ticket. If a ticket doesn't match a known trade or the assigned vendor is flagged as unavailable, Starch surfaces it to your property manager for manual assignment rather than guessing.

Can the weekly owner digest go directly to owners, or does it go to me first?

Either way — you configure it. You can have Starch draft the digests for your review before they send, or set it to auto-send to each owner's email with their properties only. Most PM founders start with draft-first until they trust the formatting, then flip to auto-send within a few weeks.