Ops & Supply

How to triage property maintenance requests as Real Estate Founders

Ops & SupplyFor Real Estate Founders2 apps10 steps~20 min to set up

You manage 200+ units across a handful of properties and maintenance requests come in through every channel at once — texts to your property manager, emails to your personal inbox, calls to the office line, notes left on doors. Half the time a tenant reports a broken HVAC unit, it sits in someone's text messages for three days before a work order gets created. You're using a combination of Gmail, a spreadsheet someone built in 2021, and maybe AppFolio or Buildium that nobody fully adopted. Duplicate requests go unnoticed. Vendors get dispatched twice. High-priority safety issues (water intrusion, electrical, mold) get triaged at the same speed as a burned-out light bulb. You don't have a dedicated maintenance coordinator — it's you or your one ops person.

Build this on Starch → See the apps used

Ops & SupplyFor Real Estate Founders2 apps10 steps~20 min to set up

Outcome

What you'll set up

A central triage queue that captures maintenance requests from email and routes them by property, priority, and trade type — so nothing sits in a personal inbox waiting to be noticed

An automated workflow that drafts tenant acknowledgment replies and creates work orders with the right vendor, property address, and urgency level attached

A live dashboard showing open requests by property, average days to close, and which vendors are being dispatched most often — so you can spot recurring issues before they become capex surprises

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

Project Management Email Agent

Data sources & config

Connect Gmail as a scheduled-sync provider so Starch syncs incoming maintenance request emails on a schedule and the Email Agent can parse, triage, and draft replies automatically. The Project Management app tracks every work order as a task card. For vendor contact lookups or property management platforms that are web-accessible (AppFolio, Buildium), Starch automates those through your browser — no API needed.

Prompts to copy

Build me a maintenance triage board with columns for New, Triaged, Vendor Dispatched, and Closed. Each card should capture property address, unit number, request category (HVAC, plumbing, electrical, appliance, general), priority level (P1 emergency through P4 cosmetic), tenant name, date reported, and assigned vendor.

Set up an email rule: any inbound email to maintenance@[mydomain].com gets parsed for property address and issue type, creates a card on the maintenance triage board, and drafts a reply acknowledging the request with an estimated response window based on priority.

Every Monday morning, send me a summary of all open maintenance requests older than 5 days, grouped by property, with the assigned vendor and last update date.

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

Walkthrough

Step-by-step

1 Connect Gmail through Starch's scheduled-sync integration so the Email Agent starts pulling inbound maintenance request emails automatically.

2 Tell Starch: 'Build a maintenance triage board with columns for New, Triaged, Vendor Dispatched, and Closed — each card captures property address, unit, issue type, priority (P1–P4), tenant name, and assigned vendor.' Starch builds the board inside Project Management.

3 Set up the email parsing rule: 'When an email arrives tagged as a maintenance request, extract property address, unit number, and issue description, create a board card in the New column, and draft a tenant acknowledgment reply with an estimated response window.' Starch wires this automatically.

4 Define your priority logic by telling Starch: 'P1 = water, sewage, electrical hazard, no heat below 55°F; P2 = HVAC not cooling, appliance failure; P3 = plumbing slow drain, door/lock issue; P4 = cosmetic.' The agent applies these classifications when creating cards.

5 Add your vendor roster by telling Starch: 'When a new card is triaged as plumbing, suggest Martinez Plumbing. For HVAC, suggest CoolAir Services. For electrical, suggest Redline Electric.' Vendor names and trade types live as a reference table Starch can read when drafting dispatch messages.

6 Tell the Email Agent: 'Draft a vendor dispatch email when I move a card from Triaged to Vendor Dispatched — include property address, unit, issue description, tenant contact, and access instructions from the card.' One click sends it.

7 Set a weekly automation: 'Every Monday at 8am, send me a Slack message listing all open cards older than 5 days, sorted by priority, with property name and last status update.' Starch connects to Slack to deliver this.

8 Build a dashboard view: 'Show me a table of all open maintenance requests by property, average days from New to Closed this month, and a count of P1 and P2 requests closed within 24 hours vs. outside 24 hours.'

9 Add a recurring audit: 'Every Friday afternoon, check for any cards still in the New column that are more than 24 hours old and send me an alert with tenant name and issue type.' This catches anything that slipped through initial triage.

10 For any vendor portals or property management platforms you access through the browser, tell Starch: 'After I approve a work order card, log into AppFolio and create a matching work order with the same details.' Starch automates this through your browser — no AppFolio API required.

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

February 2026 — 48-unit portfolio, 11 active requests in one week

Sample numbers from a real run

P1 — Unit 4B, 812 Meridian Ave — no heat (tenant with infant)	0
P2 — Unit 12A, 1140 Crescent St — HVAC not cooling	0
P2 — Unit 7C, 812 Meridian Ave — refrigerator not cooling	0
P3 — Unit 2A, 1140 Crescent St — slow bathroom drain	0
P4 requests (7 units, cosmetic/minor)	7

On a Tuesday morning in February, 11 maintenance requests came in across three properties over 36 hours. Before Starch, those would have been split across two property manager inboxes, one text thread, and a voicemail — and the P1 (no heat, 812 Meridian, unit 4B, tenant with infant) would have been sitting in a Gmail inbox next to a lease renewal question. With the triage setup live, all 11 emails hit the maintenance address, Starch parsed each one, created 11 board cards with correct priority classifications, and drafted tenant acknowledgment replies within minutes. The P1 card surfaced immediately at the top of the board flagged red. You approved the vendor dispatch email to CoolAir Services with one click — they were on site within 4 hours. The 7 P4 cosmetic requests sat in the queue correctly deprioritized. By Friday, the Monday automation fired and showed 2 cards still open past 5 days — both P3 plumbing at 1140 Crescent — which you escalated. Average response time on P1 and P2 requests for the week: 6.2 hours. The week before: unknown, because nobody was tracking it.

Measurement

How you'll know it's working

Average hours from request received to vendor dispatched, broken out by P1/P2/P3/P4

Percentage of P1 requests resolved within 24 hours (relevant for habitability compliance in most jurisdictions)

Open work orders by property and by trade type (HVAC, plumbing, electrical) — helps spot buildings with recurring system failures that signal deferred capex

Vendor dispatch frequency by contractor — tells you who's getting over-used and whether a recurring issue keeps generating tickets

Requests per unit per month — high rates on specific units often precede lease non-renewals

Comparison

What this replaces

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

AppFolio or Buildium (full property management platforms)

Deep property management features including rent collection and tenant portals, but maintenance triage is rigid — you can't build custom workflows or connect your Gmail inbox and Slack into a unified triage system without manual data entry on both sides.

Spreadsheet + Gmail labels

Zero cost and total flexibility in structure, but completely manual — someone has to move every request from inbox to spreadsheet to work order, and nothing alerts you when a P1 sits untouched for 12 hours.

Zendesk or Freshdesk (helpdesk software)

Solid ticket routing and SLA tracking designed for customer support teams, but not built for property operations — no concept of property address, unit number, or vendor dispatch, and you'll pay per seat for a tool that does far more than you need.

Notion database + Zapier automations

Flexible enough to build the triage structure and trigger some automations, but every workflow step requires a separate Zap configuration, and there's no AI parsing inbound emails into structured fields — you're still manually classifying requests.

On Starch RECOMMENDED

One platform — project management, email agent 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 maintenance emails come to three different addresses. Can Starch handle all of them?

Yes. You can connect multiple Gmail accounts through Starch's scheduled-sync integration. Set up email rules for each address and all requests flow into the same triage board, tagged by which inbox they came from. If you're using Outlook instead of Gmail, Starch connects directly to Outlook the same way.

Can Starch create work orders directly inside AppFolio or Buildium?

If AppFolio or Buildium doesn't have an API connector in Starch's integration catalog, Starch automates the work order creation through your browser — the same way you'd do it manually, but without you having to do it. Tell Starch what fields map to what, and it logs in and fills them out. No API required.

What about requests that come in by phone or text, not email?

Starch's triage workflow is built around email as the intake channel. For phone or text requests, your best move is to forward or manually log them to the maintenance inbox so they enter the same pipeline. You can also tell Starch to build a simple intake form that tenants can submit directly — Starch builds it, requests come in as structured form submissions, and the triage automation handles them the same as email.

Is this the same as a Customer Support Agent?

Starch is building a Customer Support Agent — coming soon — that will handle inbound requests 24/7 across chat, email, and other channels with AI-generated responses from a knowledge base. The maintenance triage setup described here is buildable today using the Email Agent and Project Management apps. The future Customer Support Agent will add always-on automated response and multi-channel intake on top of that.

Does Starch store my tenant data? I need to think about data handling.

Starch is not SOC 2 Type II certified today, and there is no on-premise or self-hosted option. Tenant names, email addresses, and request descriptions that flow through Gmail will be processed and stored in Starch's database as part of the triage workflow. If your portfolio has specific data handling requirements — for example, you're managing subsidized housing with tenant privacy rules — factor that in before connecting personal tenant data.

Can I track which vendors are getting called most often and cross-reference that with costs?

Yes on vendor frequency — the triage dashboard tracks dispatch counts per vendor directly from your work order cards. For cost data, connect QuickBooks through Starch's scheduled-sync integration so your vendor payment history syncs automatically. Then ask Starch to build a view that joins vendor dispatch frequency from the maintenance board with payment totals from QuickBooks by vendor name.