November 9, 2026
How to Handle a Carrier or Dispatcher Who Ghosts You
Going quiet mid-conversation is one of the more common ways a working relationship actually ends — not with a disagreement, just silence where a reply used to be. It's frustrating because there's rarely a clean moment to call it: someone can always still be "about to respond."
First, Rule Out the Boring Explanation
Before assuming the worst, consider the ordinary ones: they're driving, they're mid-load and genuinely slammed, the message didn't land the way you think it did. One unanswered message over a day or two isn't ghosting yet — it's just a delay. Set a reasonable window (a day, maybe two, depending on urgency) before treating silence as an answer in itself.
Send One Clear Follow-Up, Not Five Vague Ones
A single direct message — "just checking whether this is still moving forward, let me know either way" — gives someone a clean opening to respond, even with bad news. Repeated vague check-ins ("hey," "still there?") are easy to keep ignoring. One message that's easy to answer gets answered more often than five that aren't.
Know When to Stop Waiting
If a reasonable window passes with no response to a direct ask, treat it as your answer and move on — chasing someone who's gone quiet rarely changes the outcome, it just delays you making other plans. This is the same instinct behind handling a load that falls through last-minute: work from where things actually stand, not where you wish they stood.
Leave an Honest Review
This is exactly what ratings and reviews on a Directory profile are for — not just rating good experiences, but giving the next person accurate information before they commit time to someone who may do the same to them. A specific, factual note (what happened, not just a low score) is more useful to the next reader than a vague complaint.
If It Crosses Into Actual Misconduct
Going quiet on a conversation is one thing. Disappearing after accepting a load, after money has changed hands, or after agreeing to terms is a different problem — that's not just poor communication, it's a broken agreement. Dispatch Xchange has a reporting flow for exactly that: select the member, describe what happened, and attach anything that backs it up, and it goes to DX's team for review. Reviews handle reputation; reporting is for situations that go further than that.
The Pattern Worth Remembering
One instance of someone going quiet might just be a bad week. A pattern — across multiple people describing the same behavior — is a track record. That's the whole reason checking reviews before committing time to someone matters more than taking a good first call at face value.