Portal vs text for tenant maintenance requests
2026-10-12 · 7 min read
Rather not build it yourself? We build the automation on your tools and keep it running. Get it built for me→
It's 8:10 on a Tuesday and the maintenance coordinator is going through what came in overnight. The portal has three new requests. One says "bathroom issue" and nothing else. One is a garbage disposal, with a photo. One is a duplicate of last week's dishwasher request, because the tenant never heard anything back. Her phone has two more. One is a photo of a brown ring on a ceiling with the words "is this ok??" from a number she doesn't have saved. The other is from a tenant who always texts and never logs in, asking when someone is coming for the back door lock he reported Friday.
Nobody made a work order for the Friday text. It sat on the coordinator's phone over the weekend, under a family group chat.
Most small property managers know this morning well. The portal was supposed to be the one place repairs come in, but tenants text, call, email the owner, and stop the leasing agent in the parking lot. So you have to pick a channel to build around and decide how the others get into it.
Portal vs text: the short answer
A portal makes a better record and texting reaches more tenants. A portal request carries the unit, the tenant, a timestamp and a status, and it turns into a work order without anyone retyping it. A text gets sent the moment the tenant notices the problem, from the screen they already have open, which is why so many tenants use it no matter what the lease says.
My recommendation for most small portfolios: keep the portal as the place every request ends up, and let a text be a way in that drops the request into the same queue, asking the same questions the portal would. Tenants keep texting, and you still work from one list.
Where each one loses time
The portal loses time before the request arrives and right after. Tenants forget their login, never set one up, or decide the problem isn't worth the trouble until the slow drip becomes a stain on the unit below. The requests that do come in are often thin ("bathroom issue") because a form box is easy to fill with three words. Then the tenant hears nothing until the vendor calls, assumes the request vanished, and submits it again or texts you anyway.
Texting loses time after the request arrives. A text to a personal cell has no unit attached, no status, and no owner on your side. It gets answered between other things, and the details come in over four messages across a day. When the coordinator is out sick or leaves the job, the history leaves with her phone. And because a text feels personal, tenants expect a personal reply, often in the evening.
Side by side
| Portal requests | Text requests | |
|---|---|---|
| How many tenants use it | The ones who set up a login and remember it | Nearly everyone, without being asked |
| What arrives | Unit, timestamp, sometimes a photo, often a vague description | Whatever the tenant typed, usually with a photo, spread over several messages |
| Becomes a work order | Usually automatic | Only if someone retypes it |
| Tenant sees progress | If your software posts status updates | Only if someone texts back |
| Who can see it | The whole office | Whoever owns the phone |
| Where it breaks | Tenants who never log in, thin descriptions | Requests that live only on one phone |
| What fixes it | Asking the right questions on the form, sending updates | Routing texts into the same queue |
Running a portal so tenants actually use it
Most property management software already includes a request form. Buildium's Resident Center, for example, lets residents submit requests with photos and lets the manager share status as work orders get assigned to staff or vendors (Buildium, checked October 12, 2026). The form itself is usually fine. The trouble tends to be in how it's set up and introduced.
- Ask for what the vendor needs, in plain questions: which room, what's happening, since when, is water or power involved, a photo, any pets, and whether the vendor can enter without the tenant home.
- Put a line at the top telling tenants what counts as an emergency and the number to call for one, so a burst pipe never waits in a form.
- Turn on the status updates and check that they go out. A tenant who sees "assigned to vendor, Thursday morning" doesn't submit the request a second time.
- Send the portal link at move-in, in the welcome email and again by text, so the first time a tenant looks for it isn't the night something breaks.
Running texts without losing them
A business number does most of the work here, and it should be one the office shares, not the coordinator's cell.
- Tenants text a single maintenance number. Each new message gets an automatic reply within a minute confirming you got it and asking the same short questions the portal asks.
- The reply looks up the tenant by phone number, so the unit gets attached without anyone asking for it.
- Once the answers and a photo are in, the request gets created in your software as a work order, the same as a portal request would. The coordinator works from one list.
- Status updates go back out by text: received, vendor assigned, appointment time, done. The tenant who texts on Friday knows by Friday that it's on the list.
- Anything that sounds urgent (water, no heat, a door that won't lock, gas smell) skips the queue and goes straight to a person by phone. The Naperville after-hours post covers how that triage works at night.
The middle path most small managers end up on
Put the two pieces above together and you have it: the portal stays the record, and the text line feeds it. A request from either one lands in the same queue with the same questions answered.
After that, the scheduling back and forth between tenant and vendor is the next place time disappears, and I wrote about that in the Wheaton repair scheduling post. More on how this fits a whole portfolio is on the property management automation page.
What stays with a person
- Deciding what's urgent. The system can flag words like "water" and "smell," but someone with experience has to decide whether a brown ring on the ceiling means a plumber today or a look next week.
- Approving spend. Anything over the owner's limit still goes to the owner, and a person decides when to nudge them.
- Picking the vendor. Who's reliable on short notice, who's good with older plumbing, and who the tenant in 3B refuses to let in is knowledge that lives with your coordinator.
- Entry. When and how you give notice to enter a unit depends on your lease and the rules where the property sits, and a person should own that.
- The tenant who is upset. The third message about the same leak needs a phone call from someone who can say what happens next.
Where to start
If you have a portal that few tenants use and a coordinator whose phone fills up every night, the text line feeding your existing software is usually the first piece worth building. I can set it up for your portfolio, wired into the software you already run, or start with the free 20 minute process audit to map where your requests come in now. Tell me how maintenance reaches you today.