Skip to content
GuidesEnterprise salesUpdated 2026-08-24

What to Do When Your Sales Champion Goes Quiet

Silence is not a diagnosis. When a champion goes quiet, your job is to learn what changed before you try to create more pressure.

7 min read

When Your Sales Champion Goes QuietA field guide showing no response as the only observable fact, then branching into five possible explanations: priority, power, consensus, confidence, and timing. The guide warns against solving uncertainty with more follow-up volume.FIELD GUIDE / ENTERPRISE SALESG 02WHEN YOUR SALESCHAMPION GOES QUIETSilence is not a diagnosis.“THEY REJECTED US.”SOMETHING CHANGED. YOUR JOB IS TO LEARN WHAT.NO RESPONSETHE ONLYOBSERVABLE FACT?01 PRIORITYStill urgent enough to acton??02 POWERCan your champion stillmove it??03 CONSENSUSDid someone new createdisagreement??04 CONFIDENCEIs a concern stillunresolved??05 TIMINGIs “not now” rational?※ YOU MAY NOT KNOW WHICH ONE IS TRUE YET.That is the point.DO NOT SOLVE UNCERTAINTY WITH VOLUME.“JUST BUMPING THIS.”“CIRCLING BACK.”MORE ACTIVITY / NO NEW INFORMATIONLearn what changed before you try to create more pressure.ANDERSON DUNCANandersonduncan.com
No response is the observable fact. Priority, power, consensus, confidence, and timing are hypotheses to diagnose before adding pressure.

Do not confuse silence with rejection

A champion can go quiet for dozens of reasons: the priority changed, a leader intervened, budget moved, legal found a problem, your contact lost political capital, an internal project exploded, or nothing meaningful happened at all.

The mistake is treating silence as a single signal and responding with more volume. “Just bumping this,” “circling back,” and “wanted to make sure this did not get buried” are usually attempts to solve your uncertainty, not the buyer's problem.

Run a five-part diagnosis

Before contacting the buyer again, answer five questions:

  1. Priority: Is the business problem still important enough to act on?
  2. Power: Does your champion still have the authority or internal standing to move it?
  3. Consensus: Did another stakeholder enter and create disagreement?
  4. Confidence: Is there an unresolved concern about you, the solution, implementation, or risk?
  5. Timing: Did something change that makes “not now” rational?

You may not know the answers. That is fine. The point is to replace one emotional story with a set of testable possibilities.

Use the buying group before you use urgency

If the deal depends entirely on one person replying, the account was probably under-mapped before the silence started.

Look back at the buying group. Which stakeholders have their own reason to care about the decision? Which conversations already exist independently of your champion? Who can help you understand whether the business priority changed without turning the situation into an escalation?

The goal is not to go around your champion. It is to avoid making one relationship carry the entire weight of a committee decision.

Send a message that gives the buyer room to tell the truth

A useful re-engagement note should make three things easy: saying the priority changed, naming the real blocker, or recommitting to a next step.

For example: “I may be reading the silence wrong, so I would rather ask directly. Has the priority changed, has something new entered the decision, or is this simply a timing issue on your side? Any of those is completely workable. I just want to make sure I am responding to what is actually true.”

That message protects the relationship because it does not punish honesty.

Know when to stop chasing

Persistence is useful when there is evidence of an active problem and incomplete coordination. It becomes noise when the only remaining evidence is your own desire for the deal to exist.

I would rather close the loop cleanly than manufacture urgency. A final message can say that you are stepping back, restate the problem you believed mattered, and leave a precise path back in if it becomes important again.

That often preserves more future value than another month of low-information follow-up.

Have a version of this problem in a real account or team? Bring the question, not a polished brief.

Bring a real question