Ghosted Account Re-Engagement Playbook 2026

Silence alone isn't a trigger — plenty of healthy accounts don't need to talk to you, and interrupting them costs goodwill. The trigger is the intersection: no meaningful human contact in 30 days (email replies and meetings count; your outbound doesn't) AND a declining engagement score. Accoil computes the score from the events you already send via Segment, PostHog, Amplitude or Mixpanel, and the trigger fires carrying the payload every later touch is built from: the score trend, the last meaningful action the account took, which features went quiet, and the date of the last real contact. That payload is the whole point — nobody downstream should have to go find something to say.

One question splits the play: is usage still alive? A quiet relationship with healthy usage is a communication problem — automate it. A quiet relationship with dying usage is a churn risk wearing headphones — that gets a human. Set the line mechanically: score trend flat-or-up with active seats holding means alive; a double-digit score slide over 30 days means dying. No judgment calls at triage time.

For alive-but-silent accounts, send one email keyed to their actual usage: "your team shipped 40% more X last month — here's what teams like yours do next." The numbers come from the payload; Customer.io just delivers them.

• One insight, one next step, one sentence of each. If the email works without the merge fields, it's not this email — delete it and start over.
• Point the next step at a quiet feature adjacent to what they already use; adoption grows along edges, not leaps.
• Cap it at one per month per account, and suppress the sequence the moment a human conversation starts. Automation that keeps talking over your AM is worse than silence.

Dying usage doesn't get an email — it gets flagged to the account owner in #cs-alerts with the full payload: score trend, last meaningful action, the features that went dark, days since last contact. The AM should be able to dial from the alert without opening a dashboard. Shared channel over DM, always: unclaimed at-risk accounts need to be visible to someone whose job is noticing.

The call opens with what you observed, not how they're doing: "your team's usage of the reporting module dropped by half since March — did the workflow move somewhere else, or did something break?" Then stop talking. The insight does two jobs the check-in can't: it proves you're paying attention, and it gives the customer something concrete to correct, confirm or explain — any of which restarts the relationship. Log the reason in the CRM with a code; a quarter of these calls tells you why accounts actually go quiet, which is a churn-driver report most teams would pay for.

When a top-tier account stays silent after the call attempt, go physical — but keep the rule: the send references their usage, not your logo. A note that says "your team hit 10,000 projects in our product last quarter — congratulations from ours" lands because it's unfakeable attention. Gate it hard: reserve Sendoso sends for your top ARR tier or accounts above your save-motion threshold, and skip this step entirely when the insight call landed. A gift that arrives mid-conversation reads as a bribe; one that arrives during silence reads as effort.

The play closes one of two ways: a meeting booked, or the engagement score back above its trailing baseline with the silence broken. If neither happens within 45 days of the first touch, stop touching — route the account to your churn-risk save motion instead, because at that point you're not re-engaging, you're triaging. Every exit gets logged against the touch that produced it, so you learn which format — email, call, send — actually moves your book.