Ghosted Account Re-Engagement Playbook 2026
Your renewed customers use the product and talk to you on a steady rhythm. This play finds accounts with healthy usage that have stopped talking, confirms the quiet is real, and puts the move on the account in your CRM: a note built on their own usage, an insight call, a card – or no move, with the reason noted.
Your renewed customers use the product and talk to you on a steady rhythm – a reply, a call, a meeting every few weeks. Some accounts match the usage and skip the talking. That's a contact gap, and it's a good one to start with: the account is doing well, so you have good news to bring.
This play runs inside the weekly check. Each check ends with a move your team decides on, or a note on why there isn't one. One rule holds across every move: each touch opens with something from the customer's own usage. "Just checking in" is banned – it tells them nothing and gives them a reason to skip the next one.
Measure it on the share of healthy accounts with two-way contact in the last 30 days, the reply rate on these touches, and the renewal rate of accounts that went quiet.
How it works10 steps
01SignalFind healthy accounts that stopped talking to you
Build the benchmark once, refresh it quarterly (the benchmark play has the detail):
- Comparison customers: same segment (plan tier, size band), 12+ months as customers, renewed at the same or higher revenue. Aim for 20; with fewer, label it low confidence.
- Healthy usage: their median share of seats active each week, and their median weekly use of your core feature (reports exported, say). Default: an account at 75% of both medians or better counts as healthy.
- Contact rhythm: their median days between two-way contacts over the last 12 months – a reply, a meeting held, a call. Your own outbound doesn't count.
Your CS lead approves it. Default trigger: healthy usage and no two-way contact in 30 days, or in the peers' rhythm if that's longer. Tune both.
If usage is below the benchmark, it isn't a contact gap – that account belongs in the churn-risk save play. If the people you knew have left or stopped logging in, it's the champion play.
Say an account pays $30,000 a year and renews in eight months. 22 of its 25 seats are active and it exported 40 reports last month – right at the benchmark. Renewed customers its size reply or meet every three weeks. This one last replied eleven weeks ago. (The numbers are illustrative.)
Under about a hundred accounts, do it by hand in a spreadsheet.
02ScoreCheck the records before calling it a gap
- Usage falling? Compare with four weeks ago. A slide means the save play.
- Talking elsewhere? A shared Slack channel, support tickets with a named contact, a meeting nobody logged. Ask the owner, and log what they find as the last two-way contact.
- Quiet by choice? Notes where the customer asked for fewer calls, or a self-serve account that has never wanted a meeting.
- Recent wins: a milestone, a new team, a feature adopted in the last 60 days. This is what the touch will say.
03DecisionDecide whether there's a move worth making now
Leave it alone if usage is falling (hand it to the save play), contact is happening somewhere else, the customer is quiet by choice, or a move from this play went out less than four weeks ago (default). Also leave it if there's no recent win to talk about yet – an empty touch costs more than a week's wait. Everything else picks a move.
04ActionLeave it alone, and write down why
Set Recommended move to No move, write the reason in one line ("healthy usage, quiet by choice – asked for quarterly calls only"), and set Review date to when it could change. The leave-it-alone play covers the call in full.
05DecisionPick the move the evidence supports
Defaults to tune:
- Still silent: a key account that got a note or call from this play and hasn't replied in four weeks. A card.
- Key account: top quarter of the segment by ARR, or renewal inside six months. Insight call.
- Most: everyone else. A note.
06ActionDraft a note only their usage could write
One insight, one next step, from the account owner. Point the next step at a feature next to what they already use (a whole new use case is the second-use-case play). If the note still works with the numbers taken out, rewrite it. At first the owner enrolls each account in the note sequence from the task. Once the drafts hold up, a workflow can enroll them automatically (Sales or Service Hub Enterprise). Cap it at one note per account per month. The sequence stops the moment anyone at the account replies.
07ActionDraft an insight call, never a check-in call
Say the opener below, then stop talking: the customer now has something to confirm, correct or explain.
08ActionDraft a card tied to a usage milestone
The card names their milestone, not your logo. Skip it if a conversation has started since the check – then it reads as pressure, not effort.
09Human stepYour team decides and runs the move
The AM or CSM reads the evidence and runs the move as drafted, changes it, or passes. They own every customer conversation. Before acting, record the success measure and the review date: a reply is activity, a meeting held is progress, a renewal at the same ARR or more is the result. When they hear why the account went quiet, they log it in Move reason.
10OutcomeReview what changed, then sharpen the benchmark
On the review date, record three answers in Review result: are they talking to you, is usage holding, and what else played a part? If nothing moved, change the move, stop it, or give it time – the eight-week review covers how. Each quarter, check which moves got replies and why accounts went quiet, then update the benchmark.
Setup and templates
Sources: active users and core-feature use per account from a weekly saved query in PostHog, Amplitude or Mixpanel; replies, meetings and calls from the CRM's activity timeline (logged outbound emails don't count); ARR and renewal date from billing or the CRM; tickets from your help desk. By hand: one spreadsheet row per account each Monday with usage against the benchmark and the date of the last reply or meeting. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set.
Sendoso sends the card as a handwritten notecard (keep it under 60 words); a card you post yourself works too. Keep it a card. If you add a gift, check the recipient's rules first: government buyers and many regulated or large companies cap or ban them.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Last two-way contact | Date picker | Weekly check |
| Peer contact rhythm (days) | Number | Weekly check |
| Usage vs benchmark | Dropdown select: At or above · Near (75–99%) · Below 75% | Weekly check |
| Recent win | Single-line text | Weekly check |
| Recommended move | Dropdown select: Note · Insight call · Card · No move | Weekly check |
| Move reason | Single-line text | Weekly check, then account owner |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Weekly check, then account owner |
| Last note sent | Date picker | Workflow, when an account is enrolled in the note sequence |
| Review result | Dropdown select: Meeting held · Replied · No reply, usage holding · No reply, usage falling | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The weekly list is a saved view: Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Each move creates a task for the owner, "Quiet account: [move]", with the draft in the body. A Slack message with the task link is fine as a nudge; the work happens on the record. HubSpot's Slack app sends task notifications; custom messages need a workflow (Professional or Enterprise).
The note lane is a HubSpot sequence (Sales or Service Hub Professional); enrolling automatically needs Sales or Service Hub Enterprise. Turn on Unenroll contacts from the same company, so a reply from anyone at the account stops it. The cap is the Last note sent date on the company: the workflow skips accounts with a note in the last 30 days.
Note (Most):
Hi [name] – your team [did the win] last month, more than most [segment] customers. Teams at that point usually start on [next feature] next. Want the five-minute version?
Use this peer claim only if your records support the specific comparison, including any timing or plan choice. If they don't, describe this account's own activity instead.
Insight call opener (Key account):
"I was looking at [company]'s account – [n] of your [seats] are active, and [team] has [done the win] since [date]. What's driving that? And is [next feature] on your list?"
Card (Still silent):
[Name] – your team [hit the milestone] in [product] this quarter. Congratulations from all of us at [your company]. – [owner]
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark from your renewed customers with your team, and you approve it. Every week we check every account in the agreed segment, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call, including which moves run on their own. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan. The play stays the same.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
AI Agent Account Context Playbook 2026
Walk into customer calls current, with the account on one page instead of five tabs. When a move lands on an account or a customer meeting is booked, a one-page brief goes on the CRM record: the gap against your successful customers, the recommended move and its evidence, and what's still open. Your team reads it, decides and sends.
Second-Value Seeding Playbook 2026
Your best customers show you which feature comes after the first. This play checks every account against them each week, finds the feature customers like it added next and kept, and puts the move on the account in your CRM: an in-app prompt and a short story, the CSM on the next call – or no move, with the reason noted.
Support-Signal Escalation Playbook 2026
Fix a bad week fast and keep the account informed. When tickets spike, this play compares the account's support load and usage with your successful customers, then splits the response: a reordered queue and a note for contained problems, or the CSM and support lead on one plan, on the account record in your CRM.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.