For those managing maintenance in-house: how do you track vendor communications?

Question

Hey everyone, I hope this type of post is allowed. If not, I apologize and will remove it if requested.

I'm a developer working on a maintenance coordination tool aimed at small-to-mid property management companies, and I'm trying to make sure I'm solving an actual problem before I spend too much time building.

The specific area I'm focused on is vendor communications and what happens after a maintenance ticket is assigned out. From what I've heard talking to PMs, the follow-up side has quite a few things to track: knowing what you're waiting on, following up on threads that have gone stale with no response, having tenants calling for updates because their maintenance request is stalled, etc. is where there seems to be some friction and lost communication.

A few things I'm trying to understand from a PM or coordinator's point of view:

• How are you tracking vendor follow-ups right now? Spreadsheet, your PM platform, texts, something else?
• When a vendor doesn't respond, what does your process look like? Is there a point where you escalate to a different vendor, or does it stay reactive?
• For those using existing systems (AppFolio, etc.) — does vendor communication get tracked within that platform for you, or does it still end up outside the system in texts and email?
• What does a bad week look like when it comes to maintenance fulfillment? Trying to understand what the biggest pain points are.
• What is your average fulfillment time/goal for maintenance tasks? I understand this is likely different depending on the ticket, but any general insight is appreciated.

This is purely for research purposes. I genuinely just want to talk to people who do this every day. If anyone's open to a quick conversation I'd really appreciate it. I'm happy to share what I'm building in return if that's useful context.

Ryan Stomel · Answer

Good research questions. I'll give you the commercial side since most PM tools are built around residential workflows and the friction looks different there.

For vendor follow-up tracking: on a commercial portfolio (NNN/modified gross leases, retail and industrial) I run it through a combination of my PM software and a shared notes system. The honest answer is that the follow-up chain almost always lives in texts and email even when you have a platform — because vendors respond to their phones, not your ticket system. The gap you're describing is real and it's not being solved by AppFolio or anyone else I've seen.

On escalation: I set a hard 24-hour no-response threshold for anything urgent (HVAC down, access issue, code compliance). After that I'm calling the backup vendor and letting the primary know they lost the work. For non-urgent, it's 48 hours before I start leaning on them. The problem is without a system tracking "when did I last hear from this vendor on this ticket" you're doing that tracking mentally, which breaks down fast if you have more than a handful of open items.

A bad week looks like: tenant calls me for an update because the vendor gave them a window and didn't show, I call the vendor, they say they texted me two days ago (they didn't or it got buried), now I'm scrambling to reset expectations with the tenant and find someone else. The communications gap is the actual problem — not the ticket software.

Fulfillment targets: for commercial, routine repairs within 5 business days, urgent/habitability within 24-48 hours. The difference from residential is that commercial tenants (especially NNN) are often responsible for their own interior maintenance, so most of what I'm coordinating is common area, structural, or mechanical for the building itself.

John Ledesma · Answer

Ryan's description of a bad week is exactly right — and it's the same pattern whether you're managing 5 units or 500. The vendor says they texted, you never got it, the tenant already called, and now you're managing three conversations at once to fix one repair.

The piece that's hardest to systematize isn't the ticket software — it's the confirmation loop. Did the vendor actually acknowledge the job? Did the tenant get told someone is coming? Those two things failing silently is what turns a routine repair into a three-day escalation.

What changed things operationally for me was getting the vendor confirmation out of email and into SMS — vendors respond to texts, not platform notifications — and automating the tenant acknowledgment so they know the request was received and someone is being dispatched without me sending a separate message.

Priya's point about maintenance history is underrated too. When the same issue comes back 14 months later and you can't pull up what was done, who did it, and what it cost, you're starting from scratch every time.

Adrian — to answer your owner approval question specifically: that bottleneck is usually a dollar threshold problem. Most PMs have an informal number in their head but it's not documented anywhere. Writing it into the management agreement with a clear approval matrix is the fix, but most operators don't do it until an owner dispute forces them to.

William S Brenza · Answer

This is the piece most PM software drops the ball on. They're great at intake (tenant submits request) but then vendor coordination falls back to texts and phone tag. I've been using a combo approach — PM software for the ticket, but Realty Watchers on the front end to handle the initial tenant call and triage urgency before it even hits my queue. For vendor tracking specifically, shared notes in the PM tool + a 24/48hr escalation reminder has been my best system. Not perfect but way better than memory alone.

Adrian Maresca · Answer

Hey everyone, I appreciate the detailed responses.

The maintenance coordination tool I'm working on is aimed at the gap in communication that a few of you described. The specific problem I'm trying to solve is what happens after dispatch, did the vendor actually follow up, is this ticket moving, and if it's not, who needs to know before the tenant asks for an update first, and so on.

The core idea is that the tool surfaces inaction before it becomes a problem, rather than just logging what happened. It's also meant to keep communication in the same place instead of having everything spread out over text, email, spreadsheets, etc, while still allowing vendors and tenants to use their preferred method of communicationIt's still early in development, and something else came to mind that I'd love to look into if it's applicable and anyone's willing:The owner approval bottleneck came up a few times in different threads I saw. When you're waiting on an owner to approve a repair, how are you tracking that wait right now? Does it live anywhere, or do those also tend to get lost in the same manner as your maintenance tickets? What is currently weighing down this process and would help you keep track of these more efficiently? Additionally, how do you know when exactly you need to contact an owner for approval? Are these guidelines tracked anywhere?

Thanks again for the replies!

Jim Johnson · Answer

Most teams I’ve seen end up running a hybrid whether they intend to or not.

The PM platform (AppFolio, Buildium, etc.) holds the ticket, but vendor communication almost always spills into text and email — which is where tracking starts to break down.

The real issue isn’t just where communication lives, it’s the lack of a defined follow-up system. Without that, everything becomes manual:
• No clear “waiting on vendor” status with a timestamp
• No trigger for when a thread is considered stale
• No consistent escalation point to move to another vendor

So coordinators end up relying on memory or scattered notes, and that’s where delays and missed follow-ups happen.

In a tighter setup, you’d typically see:
• Every work order tied to a single communication thread (no splitting across channels)
• Defined SLAs for vendor response times
• Automatic follow-up intervals (24–48 hrs depending on urgency)
• Clear escalation rules when a vendor goes dark

A “bad week” usually isn’t volume — it’s when a few tickets stall with no visibility, and then everything turns reactive with tenants calling for updates.

If you’re building something here, the gap isn’t just messaging — it’s creating accountability and visibility around each step of the workflow.

Priya Menon · Answer

Honestly my vendor follow-up tracking is just texts and then I log the expense in my spreadsheet after the fact. The real gap for me is I have no easy way to search back through old maintenance history on a property when something comes up again a year later. If you build something that bolts onto an existing workflow instead of replacing it, that's the kind of thing I'd actually try.

Drew Sygit · Answer

Go research PropertyMeld

For those managing maintenance in-house: how do you track vendor communications?

Most Popular Reply