Refresh: Silence after delivery is not always malice, but it is always a process problem. Use this structured recovery playbook to confirm receipt, protect payment, and decide when to walk away.
13 min readThe stomach-drop moment
You sent the final package Friday: SOP library, inbox handoff doc, Loom walkthrough. Monday, nothing. Tuesday, their Slack status is green. They are posting on LinkedIn. Your message sits on read.
If you are a virtual assistant, ghosting hits different. You were inside their operations. Silence feels like judgment on your work and your worth. Both feelings are human. Neither is a strategy.
This playbook gives you steps, not vibes.
Ghosting is three different problems wearing one mask
Before you act, sort the situation:
| Type | Signals | Likely driver |
|---|---|---|
| Acknowledgment ghost | Work delivered, no "received" | Busy, disorganized |
| Approval ghost | They will not confirm sign-off | Internal debate, scope fear |
| Payment ghost | Delivery done, invoice ignored | Cash flow, avoidance |
Your first messages differ slightly, but all three get structure, not novels.
Step 0: Verify delivery (facts, not stories)
Check:
- Email open/read receipt (if available)
- Project Delivery release log or download timestamp
- Shared drive version history
- Slack/Teams upload confirmation
If delivery failed technically, fix that before any emotional follow-up.
Save proof now:
- PDF of sent email
- Screenshot of upload
- Link to proof of work trail entry for that deliverable
Step 1: Soft check-in (2–3 business days, no acknowledgment)
Goal: Confirm receipt. Open door for questions.
Subject: Deliverable check-in: [Project name]
Hi [Name],
Following up on the [deliverable name] sent [date] via [channel/link].
Can you confirm it reached you? If anything needs adjustment, I can schedule a quick review call or handle revisions per our agreement.
Thanks,
[You]
Rules:
- 4–6 sentences
- No "I noticed you're online"
- No guilt about your weekend anxiety
- One ask: confirm receipt or flag issues
Step 2: Direct check-in (5–7 business days)
Goal: Yes/no on status. Surface blockers.
Hi [Name],
Checking in again on [deliverable], delivered [date]. Our agreement lists [approval / invoice step] as the next step.
Please reply with either:
- Received, approved, or
- Specific items to revise, or
- A date when your team can review.
I have paused new tasks until we confirm this milestone.
Note the pause. Professional, not punitive.
Step 3: Structured summary (14+ days)
Goal: Paper trail. Finance-ready if invoice is open.
Send one email with:
- Deliverable list + dates
- Agreement excerpt on approval/payment
- Invoice number and due date (if applicable)
- What you are holding (new work paused)
This mirrors non-payment escalation without assuming they will stiff you. Many ghosts reappear at this message because it looks like records, not drama.
Use Payment Reminder for tone-calibrated wording if money is overdue.
If they reappear with "sorry, crazy week"
Good. Reset with structure:
- Confirm deliverable status (approved or revision list)
- Confirm invoice timeline if unpaid
- Agree response window for future deliverables (e.g., 48 hr acknowledgment)
- Update payment terms if this repeats
Forgiveness is optional. Updated terms are mandatory.
If they reappear only to add work
Classic pattern: ignore delivery, request "one quick thing."
Script:
Happy to help with [new request] once we close [open deliverable approval] and [invoice #, if any]. That keeps our project log accurate for both sides.
You are not difficult. You are consistent.
When ghosting means walk away
Walk-away signals:
- 30+ days silence across two channels
- Deliverable used publicly (site live, doc shared) but no reply to you
- New stakeholder claims they "never agreed" without reviewing trail
- Unpaid invoice + new scope requests
- Repeated ghost/pay cycles
Offboard cleanly: final email, files archived, access revoked per agreement, kill fee if contracted.
Prevention for the next client
| Habit | Effect |
|---|---|
| Milestone approvals in writing | Blocks "I never saw it" |
| Weekly Executive Update | Creates rhythm of response |
| Invoice tied to delivery gate | Payment follows acceptance |
| Shorter Net terms for new clients | Less float during silence |
| Deposit or prepay first month | Skin in the game |
Ghosting is harder when silence has a visible cost (paused work, no new slots).
Related guides
This guide works best with the rest of your protection stack. Start inside Salag: Engagements.
Related guides:
How Salag helps
- Project Delivery: timestamped handoffs and client release actions
- Executive Update: weekly touchpoints that reduce long silences
- Payment Reminder: factual follow-ups when ghosting pairs with overdue pay
- Time Ledger: evidence of work completed during silent periods
Related: client silent before payment, follow up late payment.
- Engagements
- Document work clients can't dispute
- How to deliver files safely
- Proof of work trail
- Agreement Builder
Bottom line
Client ghosted after delivery? Confirm receipt, escalate in timed steps, pause new work, document, and update terms if they return. You cannot control their responsiveness. You can control your process.
Move safer. Not faster.
In short
When a client ghosts after delivery, do not spiral. Confirm they received the work, send a short factual check-in with deliverable name and date, then escalate in timed steps while pausing new tasks. Silence may be chaos, not scam, but your payment and scope rules still apply. Document everything.
Common questions
When a client ghosts after delivery, do not spiral. Confirm they received the work, send a short factual check-in with deliverable name and date, then escalate in timed steps while pausing new tasks. Silence may be chaos, not scam, but your payment and scope rules still apply. Document everything.
Common reasons include internal chaos, stakeholder changes, dissatisfaction they have not voiced, payment processing delays, or avoidance because they owe money. The cause varies; your response should be structured either way.
Confirm the deliverable was received (read receipt, platform log, or resend link). Send a short factual message naming the file, delivery date, and any invoice or approval step still open. Do not assume malice on day one.
First check-in: 2–3 business days after delivery if no acknowledgment. Second: 5–7 business days. Structured summary with pause on new work: 14+ days. Adjust for agreed response windows in your contract.
No new deliverables until delivery is acknowledged and open invoices are addressed. Continuing work rewards silence and weakens your position.
It is a risk signal, not a verdict. Many ghosts are organizational. Payment risk rises when silence pairs with overdue invoices, new requests without acknowledgment, or avoidance of finance contacts.
Consider ending the engagement when silence exceeds 30 days, multiple channels go unanswered, unpaid invoices stack, or they reappear only to request more work without settling open items.