Trouble getting subs to respond? What actually works

You text your electrician on Monday: still on for Wednesday? Nothing. You text again Tuesday morning. Nothing. You call Tuesday afternoon and it goes to voicemail, and now you are standing on a job that needs power Thursday, guessing whether a guy who has done good work for you three years running is going to show up. By the time he texts back “yeah I got you” at 9pm, you have already burned a day of worry and half a plan.

The easy read is that subs are flaky. Some are. But most of the subs you actually want to keep are not dodging you because they are lazy. They are dodging you because, from where they sit, answering your text is a bad trade. It costs them something and it does not save them anything. Getting a reply is one of the core subcontractor headaches every small shop hits, and if you want to know what actually gets a sub to answer, you have to look at the message from his chair, not yours.

Why answering you costs him

A good sub is running your job and four other people’s jobs at the same time. His phone is a wall of the same question from five generals, and every one of those questions is expensive to answer, because of how they are usually asked.

Read a trades forum for ten minutes and you get both sides of this in plain words. The sub’s version: “if I answer him now he asks me to commit to a date, and his dates move twice before the job’s real, so I wait.” The general’s version, a few threads over: “I can’t get a straight answer out of my subs to save my life.” Both men are telling the truth. They are just describing the same broken exchange from two ends.

Here is what makes your text expensive to answer:

The scope is vague. “You good for the Miller job next week” is not a question he can answer, because he does not know if next week means the rough-in he quoted or the whole thing, or whether the drywall is even up yet. A full answer means a five-minute back-and-forth he does not have time for, so he answers with silence and sorts it out later.

The date has moved before. He has been burned confirming a Wednesday that became a Friday that became “we’ll call you.” So he has learned that confirming early costs him: he holds the day, turns down other work, and then your job slides and he ate the day for nothing. Now he waits until your date feels real, which reads to you as him going quiet.

The pay is slow. This one nobody says out loud on the phone, but it is in every forum thread. A sub who is still waiting on an invoice from your last job is slow to jump on your next one. Responsiveness follows the money. If he is chasing you for a check, he is not going to be quick to chase your schedule.

None of that makes it fine. A sub you cannot reach is a sub who no-shows, and a no-show blows up your day and everyone’s downstream. But it does explain why texting harder does not work. You are not fighting laziness. You are fighting a math problem, and right now the math tells him to wait.

Make the ask answerable in one word

The single biggest change is the cheapest: stop sending questions that cost him five minutes, and start sending questions he can answer in one word without thinking.

Bad: “Hey you good for next week?” That forces him to reconstruct which job, which scope, and which day before he can even start typing.

Good: “Rough-in at 214 Miller, Wed the 12th, 7am start, drywall’s not up yet so you’ve got clear walls. You in? Yes/no.” Now he can answer from a job site with his thumb, in the ten seconds between pulling wire, because you did all the lookup work for him. The address is there, the date is there, the condition he cares about is there, and the reply you need is one word.

This is the same discipline that gets a crew to confirm they’re coming tomorrow instead of leaving you guessing: the confirm has to be one tap, or it competes with everything else on his phone and loses. Every extra thing your message makes him figure out is one more reason to deal with it later, and later is where replies go to die.

Give him a date that has earned his trust

If your dates move twice before a job is real, no wording fixes it. He is right not to hold the day. So change what you send him, not how loud you send it.

Do not ask a sub to confirm a date until the date is actually firm. When you do send it, send the thing that makes it firm: the inspection passed, the drywall is scheduled, the GC signed off. “Miller rough-in is a go, drywall’s booked for the 14th so I need you the 12th and 13th” tells him this one is real, not a placeholder he will get whipsawed on. A sub confirms fast for the general whose dates hold. He drags for the one whose dates are wishes. You teach him which one you are with every date you send.

Close the loop on pay so responses stay fast

You will never fully separate how fast a sub answers from how fast he gets paid. If you want quick replies on the next job, the quiet lever is to have been quick with the check on the last one. Pay on the terms you agreed, and when a sub sends an invoice, send back one line that the payment is in: “got your invoice, check cut Friday.” That one text does more for your next confirmation than any amount of Monday chasing, because it changes the underlying math. Answering you stops being a bad trade.

Slow pay usually is not spite. It is that the invoice landed in a text thread, or an email, or a photo of a handwritten ticket, and it fell behind the day. If the work and the ticket lived together, in the same place, you would not lose it. That is the same failure that turns one buried message into a two thousand dollar callback, just pointed at your accounts payable instead of your schedule.

The quiet version of the fix

Notice what all three changes have in common: they lower the cost of answering you until a reply is easier than a dodge. A vague ask, a soft date, and a slow check all raise that cost. An answerable question, a firm date, and a closed loop lower it.

The place this gets hard is that a sub is a guest on your job, not a member of your crew. You do not want to make him buy an app or learn your system just to tell you yes. What you want is a single job thread he can open, see the address and the date and the scope already there, tap yes, and get back to work, without you paying for his seat or him fussing with a login. In Crewmigo a sub is a free guest on the one job you invited him to. The thread carries the ask, so the question shows up already answerable, and marking himself in is one tap by name, not a paragraph typed from a roof. We are new, so put one sub and one job on it and watch how fast the yes comes back. A job thread a sub can answer in ten seconds beats a phone call he has learned to dodge, every time.