what it catches
Courtesy can hide weak momentum.
Many cancellations sound polite enough to keep you investing. This tool separates apology from actual repair effort, so one sorry does not automatically become your logistical homework.
vøiddo micro-tool
cancellation triage
raincheck-or-run is a deterministic first pass for one expensive moment:
someone canceled, and now you need to tell a real reschedule from a vague delay,
repeat flake, or soft exit.
live checker
offer one specific time
10 hours since cancel · 1 cancellation
posture
real-reschedule
what to send or do next
use the $19 Deep Diveproof by example
what it catches
Many cancellations sound polite enough to keep you investing. This tool separates apology from actual repair effort, so one sorry does not automatically become your logistical homework.
what it does not do
It reads one cancellation plus the recent timing around it. If the real problem is a
recurring person, recruiter, client, or support pattern, move into
tells instead of squeezing more certainty from one message.
why it matters
raincheck-or-run keeps the decision operational. It asks whether their
message carries enough specificity and initiative to justify your next move.
best next free exits
the thread went quiet after this
ghost-or-go is better when the moved plan already turned into silence.Use it when the cancellation is done and the next question is whether the quiet thread still deserves one final ping.
you already wrote the follow-up
double-text-risk is better when the real question is whether your next ping looks needy.
Keep this checker for the cancellation call. Use double-text-risk
once the draft already exists and timing/pressure is the real risk.
the wording is the problem now
replytone is better when the reschedule text itself needs a warmth / pressure check.
Decide the posture here, then move into replytone to score the line
before you send it.
paid next step
raincheck-or-run handles the narrow free call. tells is
the paid move when the same person, recruiter, prospect, or support thread keeps
reopening the same ambiguity.