The Non-Responder Chase Sequence That Doesn't Burn Client Relationships

A client who goes quiet mid-tax-season isn't usually being difficult. They're busy, they've forgotten, or the request got buried. But without a defined chase sequence, “probably fine, just busy” can quietly become “ten days from deadline and unreachable” — and by the time that's obvious, the relationship damage is already done.

Three touchpoints, escalating on purpose

Day 7 of silence — friendly check-in. Low pressure. “Just checking you received our document request — happy to help if anything's unclear. No rush if you're still gathering things together.” The goal here is a nudge, not pressure.

Day 14 — specific and dated. Name exactly what's still missing, and give a real date. “We still need [specific items] to get your return moving. To keep you clear of the 31 January deadline we'd need these by [date].” Vagueness at this stage just invites another two weeks of silence.

Day 21 — escalate to a partner, by phone. Not another email. By three weeks of silence, this has stopped being an admin gap and become a relationship signal worth a human conversation, not another message in a queue they're already ignoring.

Why the structure matters more than the wording

The exact wording should match your firm's voice — the version above is a starting point, not a script to copy verbatim. What matters is the shape: friendly, then specific, then a real conversation. The most common failure mode isn't bad wording, it's skipping straight from “friendly nudge” to “nothing until the deadline is uncomfortably close,” with no defined middle step.

Resetting the clock

If a client goes quiet again after previously reaching “complete” status — sends everything, then stops responding to a follow-up query — treat it as a new non-responder chase from the point of silence, not from original contact. The clock resets; don't let an old, resolved chase history mask a new gap.

Making this visible beyond one person

The chase sequence only works if someone's actually tracking where each non-responder sits in it — day 7 vs day 14 vs escalated. In a lot of firms that tracking lives in one manager's head or inbox, which is exactly what breaks when that person's out for a week in December.

The Tax Season Operations Playbook includes this chase sequence as part of a validated PathPilot import, so every client's chase status is visible to the whole team, not just whoever's been keeping track.