Manage property maintenance tickets through automated text chat

Turns tenant chat messages into tracked maintenance tickets, routes them to the right team, and logs everything.

How the work actually flows

It branches. Every path runs; a person is alerted when a step fails.

Pattern: Sequence (1) ยท Parallel Split (2)

flowchart TD trig>"tenant sends maintenance text"]:::trig s0["classify message type urgency"]:::task s1[("log ticket in spreadsheet")]:::store s2["notify tenant and team"]:::task trig --> s0 s0 --> s1 gx{"+ who needs notifying"}:::gate s1 --> gx p00["send ticket number"]:::task gx -->|"tenant"| p00 p10["alert assigned team"]:::task gx -->|"maintenance team"| p10 p00 --> s2 p10 --> s2 out[/"logged ticket with tracking status"/]:::out pay{{"nothing slips through the cracks"}}:::pay s2 --> out out --> pay esc(("Alerts a person")):::human s1 -. "if it fails" .-> esc esc -.-> out classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepA personA record or sheetEvery pathResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
Voice & PhoneMessaging & NotificationsSpreadsheet & Database OpsReal Estate & Property
Connects
WATIGoogle Sheets
Featured in

The problem it solves

Tracking maintenance requests across texts, calls, and sticky notes makes it easy to lose track of what needs fixing. Tenants do not know the status of their request, and urgent issues like leaks can sit unanswered. You have no easy way to see which properties need attention.

Who it fits

Best for property managers and landlords who handle maintenance requests from multiple tenants.

How it works

  1. A tenant sends a maintenance issue as a text message
  2. The system reads the message and figures out the type and urgency
  3. A ticket is created and logged in a spreadsheet
  4. The tenant gets a ticket number and the right maintenance team is notified
  5. A daily check flags overdue tickets so nothing slips through
What you get

Maintenance requests that never fall through the cracks

Tenant messages turn into tracked tickets that reach the right team automatically, so nothing gets lost between the message and the fix.

What you get

A logged maintenance ticket with status tracking, plus text updates for tenants and teams.

What you need

A WATI messaging account and a Google Sheets account.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook