Your ghosting list needs a next action, not more names

Dongyun Lee·Jul 29

It is Friday afternoon when you remember the client who said they would reply on Tuesday. You search your inbox and find two more: one proposal with no answer and one project waiting on approval. Put them in one ghosting list, then give every row a specific next action. That is how you track clients who stopped responding without relying on memory or turning every silence into a chase.

The list can live in a spreadsheet, task tool, or follow-up CRM. The tool matters less than the rule: a silent client must move into a visible state with an owner, context, and a decision about what happens next.

What counts as a client who stopped responding?

Silence starts when an expected response does not arrive. It does not start after a universal number of days.

If a client says, "I will approve this by Thursday," the account becomes silent on Friday. If they say the team will review your proposal next month, three quiet weeks may be completely normal. A customer who usually replies within hours may deserve attention after two business days. A procurement lead working through a six-week process may not.

Track the broken expectation, not just the last email date.

This distinction prevents two common mistakes. The first is following up too early because a dashboard marked an arbitrary date overdue. The second is waiting too long because nobody recorded when the client said they would return.

Use one of these events to start the clock:

A promised reply date passes.
A decision, approval, payment, or document is due.
A normal communication rhythm changes noticeably.
Your last message contained a clear question and received no answer.
A scheduled meeting is missed without a new date.

Do not label every quiet account as ghosting. Some conversations are complete. Some clients are between projects. Some buyers told you exactly when to return. Your list should capture relationships with an open loop, not everyone who has not emailed recently.

What should a ghosting list contain?

Most ghosting lists fail because they contain names and dates but no decision.

A useful row needs enough context for someone to act without reconstructing the conversation from five email threads. Start with these fields:

Client and primary contact
Owner
Last meaningful exchange
Expected response or commitment
Date the expectation passed
What is blocked
Next action
Next action date
Channel
Status

The field that matters most is Next action. "Follow up" is not specific enough. Write the action as a short instruction connected to the open loop:

"Send the revised scope and ask whether legal or budget is holding approval."

"Call the operations lead because the onboarding date is now at risk."

"Park until 15 September, then return with the contract-renewal trigger."

Now the list can drive work. Without that field, it is only a record of discomfort.

If you want a simple starting structure, the client follow-up tracker template uses the same principle: last contact explains what happened, while next action decides what should happen.

Use statuses that force a decision

A single status called Ghosted hides too much.

One client may be two days late on a low-stakes answer. Another may have ignored three messages while holding up a launch. A third may have lost the internal sponsor who owned the project. They should not sit in the same queue.

Use five working states:

Waiting

The client is still inside the response window they set. No action is due. Keep the account visible, but do not manufacture urgency.

Follow up now

The expected response date passed and one direct follow-up is appropriate. The next message should restate the open item and make the reply easy.

Try another route

Email has failed, but the relationship and stakes justify a different channel or contact. Call, use a known messaging channel, or ask another stakeholder. Do not repeat the same email through three channels in one day.

Park until a trigger

The client is not ready now, but you know when the conversation may become relevant again. Attach a real trigger such as budget planning, contract renewal, hiring, a product launch, or the end of a busy period.

Archive or escalate

There is no useful next commercial action, or the silence has become a contractual issue. Archive dead opportunities. Escalate unpaid invoices, project dependencies, or legal obligations through the process agreed in the contract.

These statuses stop the list from becoming an archive of people you feel guilty about contacting. Every account has a current treatment.

Build the list from open loops, not inbox age

Searching for emails older than seven days will find noise. It will miss important conversations too.

Start with places where an open loop already exists:

Proposals sent without a decision
Projects waiting on client input
Meetings missed without rescheduling
Renewals or expansions waiting on stakeholder review
Customers who promised a document, approval, or internal introduction
Active accounts whose normal reply pattern changed

Then check three sources: your inbox, calendar, and current client or pipeline list. You are looking for a mismatch between what was supposed to happen and what actually happened.

Take a 12-client consulting pipeline as an example. Two proposals are awaiting decisions. Three active projects need client input. One former client asked you to return after a hiring decision. The inbox shows six quiet threads, but only four have open loops today:

Northstar promised proposal feedback on Monday.
Acme missed a content approval that now affects Friday's launch.
Juniper asked you to reconnect after its new operations lead starts next month.
Fieldhouse received a final deliverable and owes an invoice that is five days overdue.

Northstar belongs in Follow up now. Acme may need Try another route because delivery is at risk. Juniper belongs in Park until a trigger. Fieldhouse follows the payment process, not the sales cadence.

One label would flatten four different situations. The list should preserve the difference.

Write the next message from the blocked decision

When a client stops responding, do not ask them to restart the whole conversation.

Bring forward the one decision that is blocked. Then reduce the work required to answer.

Weak:

Just checking in to see whether you had any thoughts on my last email.

Better:

You mentioned the team would review the proposal by Tuesday. Is the open question scope, timing, or budget? If timing is the issue, I can hold the current start date until Friday.

The second version recovers the agreement, names likely blockers, and offers a concrete next step. The client can reply with a few words.

For project work, state the consequence without using it as a threat:

We still need the final product copy to keep the 14 August launch date. If it is not ready, should we move the launch or publish the approved sections first?

For a relationship that may simply be mistimed:

It looks like this is not a priority right now. I can close the loop and return before Q4 planning, unless there is a better time.

The principle is the same as following up without being annoying. Relevance matters more than persistence. A message earns attention by making the recipient's decision smaller.

How many times should you follow up?

There is no useful universal number. The right cadence depends on the agreement, stakes, relationship, and channel.

For a normal proposal or non-urgent decision, two or three thoughtful attempts across roughly two weeks may be enough. For an active project blocked by client input, the contract and delivery plan should determine the escalation. For an overdue payment, follow the payment terms. For a dormant commercial relationship, stop repeated nudges and attach a future trigger instead.

Set the cadence before you send the first follow-up:

Direct reminder tied to the missed expectation.
A second message that changes the angle, reduces the ask, or uses the appropriate alternate route.
A close-the-loop decision: park, archive, or escalate.

Do not leave the final state as "follow up again sometime." That is how the same names remain on the ghosting list for six months.

A client who does not answer today may still be valuable later. The dormant-client guide explains how to return with a changed fact instead of carrying an endless sequence forward.

Review the ghosting list once a week

The list should create a short operating rhythm, not another database to maintain.

Once a week, spend 20 minutes on four questions:

Which new open loops passed their expected response date?
Which follow-ups are due now?
Which accounts need a different route, future trigger, or escalation?
Which rows can be closed?

Sort by Next action date, not by client value or last contact alone. The goal is to make today's commitments visible.

Keep one owner per row. If sales, delivery, and finance all care about the same silent client, choose the person responsible for the next external message. Everyone else can contribute context. Multiple owners usually means nobody sends.

For a solo operator or a small list, a spreadsheet is enough. When several people manage the same relationships and context is scattered across email, meetings, and notes, a follow-up CRM can reduce the reconstruction work. Dealpilot is built for that narrower job: surfacing the account that needs attention, preserving why, and helping draft the next message.

Do not add software before the weekly review works. A broken operating habit inside a more capable tool is still broken.

The list is finished when every silence has a state

Tracking clients who stopped responding is not about counting unanswered emails. It is about closing open loops.

Each silent client needs one of four outcomes: contact now, try another route, return at a real future trigger, or close the account. Add the owner, context, and next date required to make that outcome happen.

That turns a ghosting list from a pile of names into a working queue.

Silence will still happen. It just will not disappear.