Client Ghosted After Delivery? A Week-by-Week Plan

You delivered the work. The client said it looks great. You sent the invoice. Then nothing: blue ticks, no reply, no payment.

Ghosting after delivery is the late payment that stings most, because the work has already left your hands. The usual advice is "send a legal notice" or "you should have taken an advance". Neither helps you this week.

What helps is a plan with dates on it: what to send, what to check, what to stop doing, and when to escalate or let it go.

The example I will follow: you built a ₹60,000 website for a client called Rohan, who paid ₹15,000 as an advance. You delivered on 1 October and sent INV26-031 for the ₹45,000 balance, due on 8 October. He has not replied, and it is now 9 October.

One thing first. I am not a lawyer. The legal parts below are a general map as of October 2026, the rules change, and you should confirm anything you act on with a lawyer or a CA.

The plan at a glance

Count from the day the invoice was due. If your invoice had no due date, count from the day you sent it, and fix that in the first step.

Day 1 to 3: check your side before you chase

Silence in the first three days after the due date is usually a busy client or a buried PDF. Check four things.

1. Did the invoice reach the right person, and was it opened? A PDF sent on WhatsApp sinks under forty other messages. Send it on email too. If someone else handles payments, they need it, not Rohan.
2. Is the amount and the due date clear? The invoice should show the invoice number, the pending amount after the advance (₹45,000, not ₹60,000), a due date written as a date, and UPI or bank details that work.
3. Did money arrive that you missed? Check your UPI and bank statement. If a payment came in short by a round percentage, often 10% on professional fees, it may be TDS and not underpayment. Then the next message is a request for the deduction details, not a chase.
4. Is anything pending on your side? An unanswered feedback request or a pending approval gives a client an easy reason to wait. Close it or say in writing that the delivery is complete.

Then send this.

Hi Rohan, sharing INV26-031 again for the website balance: ₹45,000, due 8 October. UPI and bank details are on the invoice. Can you confirm it has reached the right person?

I built Riffit, and this is one of the few places it is relevant. An invoice shows as overdue on its own once the due date passes, and you get a WhatsApp ping the first time the client opens the invoice link. That answers half of check one: it was opened, though not by whom. It cannot tell you whether he paid. Riffit never touches the money, so you mark invoices paid yourself.

Week 1: ask for a date, on a second channel

By day seven, a resend is not enough. The job of this message is to get a date.

Hi Rohan, INV26-031 for ₹45,000 was due on 8 October and is now 7 days overdue. What date will it be paid? If someone else handles payments, share their name and I will send it to them directly.

Do three things around it.

• Switch channel. If the first message went on WhatsApp, send this one on email, and the other way round.
• Call once. One call, in working hours.
• Write down what happened. Date, channel, what you sent. You will need this list in week four.

Two posts already cover the full reminder sequence. The 4-touch late payment follow-up has the timing, and the WhatsApp payment reminder scripts have six stages of wording, including one for a silent client. If he breaks the silence with an excuse instead of a date, I have replies for payment pushback too.

In Riffit, every unpaid invoice you have sent has a Send Reminder button. It emails the client on every plan and adds a WhatsApp message on Pro, once a day per invoice. Free also sends one automatic email on the due date. Pro sends a schedule you set, before, on and after the due date.

Week 2: stop giving

Two weeks of silence after two written messages is a pattern. Your position now depends on what you still hold. Stop doing these:

• More free work. No "small changes", no extra revision round, no new task from the same client.
• Handing over source files. Figma files, code repositories, raw footage, editable documents. If they are not delivered yet, they stay with you.
• Transferring logins. Domain, hosting and admin access that are still in your name.
• Offering a discount nobody asked for. It tells the client the invoice was negotiable all along.

Do not do these without talking to a lawyer first: taking down a live website, locking the client out of something already delivered, or naming them on LinkedIn. Holding back what you have not handed over is one thing. Disabling delivered work, or shaming a client in public, can turn you into the person with the legal problem.

Send this.

Hi Rohan, INV26-031 (₹45,000) is now 14 days overdue and I have not had a reply. I am pausing the pending changes and the source file handover until it is cleared. Please pay by 29 October, or reply with a date I can plan around.

Use this week to put your proof in one folder: the message where the price was agreed, the delivery message, the invoice, every reminder, and any reply where the client acknowledges the work or the amount.

Week 4: the formal payment request letter

A formal letter makes sense when the invoice is about 30 days overdue, at least two written reminders have gone unanswered or promised dates have been missed, and there is no real dispute about the quality of the work.

The letter is one page. It states the invoice number, the amount, the original due date, the reminders you sent, and one final date, usually seven days out. You send it yourself, by email. It is not a lawyer's notice, and it should not pretend to be one.

I have a copyable template in Payment Request Letter: The Step Before a Legal Notice. Send the letter, then send this on WhatsApp so it is not missed.

Hi Rohan, I have emailed a formal payment request for INV26-031 (₹45,000, due 8 October). It asks for payment by 12 November. Please read it today.

After week 4: three routes, with rough cost and effort

If the letter's date passes, you have to choose. Treat the costs below as rough, and ask a lawyer which route fits your case.

The police will usually call an unpaid invoice a civil dispute and decline to act. A bounced cheque is a separate matter, and worth a lawyer's opinion.

How to decide to write it off

Here is the test I would use.

• Compare the next step to the amount. A ₹3,000 notice against ₹45,000 is a fair bet. The same notice against a ₹6,000 invoice is not.
• Ask for a settlement before you give up. ₹30,000 this week can be better than ₹45,000 in a year. If you accept less, get it in writing that it closes the invoice. In Riffit, you record the ₹30,000 as a part payment, then choose Close Invoice from the invoice menu. It closes at what you were paid and reads Closed, not Paid.
• Set a decision date. Say 30 November. After it, you either take a route above or close the file.

If you write it off, keep the folder. If you are GST registered and have already paid GST on that invoice, do not assume you can get it back. GST already paid on an invoice that is never paid generally cannot be adjusted, so ask your CA before you issue a credit note or write the invoice off.

What makes this less likely next time

Almost every ghosting story has the same gaps.

• An advance before you start. Then the worst case is losing the balance, not the whole fee. If a client pushes back on it, here is what to say when a client refuses an advance.
• Scope and price in writing, accepted by the client. One dated record in place of scattered chats.
• Final files after final payment. Show the work. Hand over the editable files once the balance is paid.
• A due date written as a date. "Due 8 October" is easier to act on than "payable on completion".

If you only adopt two of these, take the advance and hold the final files back until the balance clears.

FAQ