Why Your Subs Don't Read Your Emails (And What to Do About It)
By Colby Mueller, Founder, VestaBuilder
Email open rates in construction hover around 20%. Text messages get read at 95%. Here's why subs ignore your emails — and the simple fix that doesn't require them to change a thing.
You sent the schedule update on Monday. You followed up Tuesday. By Wednesday morning, the framing crew showed up a day early and the HVAC sub was nowhere near the job site.
So you pulled up your sent folder. The email was there. Opened by one person. Three days ago.
This isn't a you problem. It's not even a them problem, really. It's a channel problem — and once you understand why email fails in the trades, the fix becomes obvious.
The Honest Truth About Email and the Trades
Email was built for office workers. It assumes the recipient is sitting at a desk, checks their inbox multiple times a day, and has the bandwidth to read a message, process it, and act on it.
Your subs are not sitting at a desk. They are on a ladder, in a crawl space, driving a truck full of copper pipe, or coordinating three other jobs at the same time. Their relationship with their inbox is occasional at best.
And even when they do check email? Construction GCs are not the only people emailing them. Material suppliers, inspectors, their own crew leads, homeowners who got their number somehow — it's a pile. Your schedule update is competing with all of it for attention, and it has no particular advantage.
Here's what the data actually looks like across industries: email open rates hover around 20%. Text message open rates are above 95%, typically within a few minutes of delivery. That gap doesn't shrink when the recipient is a trim carpenter who checks his phone between cuts. It widens.
Why the Subcontractor Portal Isn't the Answer Either
If you've looked at Buildertrend or similar platforms, you've seen the subcontractor portal pitch. Give subs a login, they see their schedule, everyone stays aligned. Clean in theory.
In practice, the portal has the same adoption problem email does — except worse, because now you're asking subs to do something they've never done before: log into a platform they didn't ask for, remember a password, and check it regularly.
Most don't. The ones who do, do it inconsistently. And once your subs learn that the portal is where information goes to be ignored, the GC ends up back on the phone anyway — which was the whole workflow the portal was supposed to replace.
The fundamental issue isn't the software. It's that you're asking subs to change their behavior. Subs who have run their business a certain way for 15 years are not going to restructure their communication habits because your project management tool has a portal.
What Actually Gets Read
Think about the last time a sub missed something you told them. Now think about how you eventually got the message through. Almost certainly: a phone call, or a text.
That's not an accident. Phone and text work in the trades because they meet people where they already are. Every sub has a phone on them all day. Most of them text constantly — with their own crew, their suppliers, their family. It's the native communication layer of the job site.
So the question isn't "how do I get my subs to check their email more?" It's "how do I get schedule-critical information into the same channel they're already living in, without me having to send every message manually?"
The Manual Texting Trap
Some GCs solve this by just texting everything. And it does work — until it doesn't.
Manual texting has a few failure modes that compound as your job count grows:
- You forget someone. When you're updating four subs on a schedule shift, it's easy to send three texts and miss the fourth. The fourth sub shows up on the wrong day. You've solved the delivery problem but created a new consistency problem.
- Replies pile up with no structure. You text eight subs. Seven reply. Now you have seven text threads to track, and you're building a mental model of the schedule in your head instead of a system. One "sounds good" that you didn't read until the next morning turns into a missed handoff.
- It doesn't scale. One house with five subs is manageable. Two houses with ten subs starts to feel like a second job. Three houses and you're dropping balls.
- There's no record. When a sub says "you never told me the concrete was pushed," your only recourse is scrolling back through a text thread. That's a bad position to be in, especially when weather delays or lien disputes enter the picture.
What Automated SMS Actually Looks Like
The right answer isn't email. It isn't portals. And it isn't you texting everyone by hand at 6am.
It's a system where the schedule lives in one place, and reminders go out automatically to the right sub at the right time — on the channel they already use.
Here's what that looks like in practice:
- You assign a task to your plumber with a start date. The system sends a reminder automatically — no action required from you.
- The plumber texts back "confirmed" or "need to push two days." The system reads the reply, updates the task status or flags the reschedule for your review.
- You see one dashboard that shows every trade, every task, every status and last reply — without digging through text threads.
- When dates shift, you update once, and the downstream reminders adjust automatically.
The sub doesn't download anything. Doesn't create a login. Doesn't change a single thing about how they operate. They just respond to a text, the same way they respond to texts all day.
That's the whole model. You stop chasing, they stop getting surprised, and the schedule holds together without you being the glue.
The Record-Keeping Side Effect Nobody Talks About
There's a benefit to automated SMS scheduling that most GCs don't think about until they need it: the paper trail.
When every reminder is logged, every reply is captured, and every schedule change is timestamped, you have a record of what was communicated and when. That matters in a few scenarios:
- Weather delays. When a client asks why framing took three extra weeks, you have a log of which days were flagged as weather days, not a vague memory.
- Sub disputes. When a sub claims they were never told about a reschedule, you have a timestamp showing the reminder was sent and — if they replied — confirmed.
- Client communication. When a homeowner asks "where are we on the schedule?", you can pull up the dashboard instead of reconstructing the answer from memory and three different text threads.
Most GCs don't start thinking about documentation until they're in a dispute. By then, it's too late to recreate the record. A system that logs everything as a side effect of doing its main job is worth a lot.
Start Simple
If you're still running your sub communication through email, the fix doesn't require rethinking your entire business. It requires picking one job and running it differently.
Put the schedule somewhere that can send automated SMS reminders. Watch what happens to your "did you get my message?" calls. Watch what happens to the number of no-shows. Give it four weeks.
The builders who've made the switch don't go back. Not because it's fancy software. Because it works, and it requires almost nothing from the people it's supposed to work with.
That's the whole pitch. Meet your subs where they already are.
VestaBuilder sends automated SMS reminders directly from your schedule — no app for the field, no portal, no behavior change required from your subs. We're onboarding custom builders manually right now. Visit vestabuilder.com to see if it's a fit.