May 16, 2026 · 7 min read read

When to Send a Second Invoice Reminder: Timing, Channels, and What to Do If It's Ignored

Exact timing for a second invoice reminder based on invoice size, which channel to use (email, text, or call), and what to do when the second reminder gets no response.

# When to Send a Second Invoice Reminder: Timing, Channels, and What to Do If It's Ignored

Your first invoice reminder went out. You kept it polite — a brief "just checking in" with the invoice attached. A week went by. Nothing.

Now you're staring at the account, wondering: do I send another email? Do I call? Do I wait a few more days? Am I being too aggressive?

The answer depends on three things: how much the invoice is for, how many days past due it is, and what channel you used the first time. This guide covers exactly when to send a second reminder and, more importantly, what to do when the second reminder also gets no response.

---

## Why Most Second Invoice Reminders Don't Work

The problem isn't that you're reminding too often. It's that you're using the same channel twice.

When a customer ignores your first email reminder, sending a nearly identical email a week later produces the same result: nothing. You haven't changed anything about the interaction — same format, same visual, same level of urgency. The customer who mentally filed the first one under "deal with later" will do the same with the second.

Research on payment collection consistently shows that customers who ignore two consecutive email reminders are unlikely to respond to a third email. The channel has been tuned out. The only thing that reliably breaks through after a customer goes quiet on email is a different medium — specifically, a direct phone call. Studies show 60% of overdue invoices get paid within 48 hours of a live phone conversation, a number that no email sequence comes close to matching.

The second-reminder problem is less about timing and more about escalation. An effective follow-up system doesn't repeat the same nudge — it steps up.

---

## The Right Timing: When to Send Your Second Reminder

Timing depends heavily on invoice size. A $200 invoice and a $3,000 invoice should not follow the same reminder schedule. Here is a practical framework:

**For invoices under $500:** - Upcoming notice: 3 days before due date - Due-date reminder: Day 0 - Second reminder: Day 7 past due (email or text) - Escalation: Day 14 past due (phone call or formal notice)

**For invoices $500–$2,500:** - First reminder: Day 3 past due (email) - Second reminder: Day 7 past due — shift to text or phone if email was the first channel - Escalation: Day 14 past due (formal demand notice + phone)

**For invoices over $2,500:** - First reminder: Day 1 past due (email + confirm receipt) - Second reminder: Day 5 past due — phone call only, not another email - Escalation: Day 14 past due (written demand + payment plan offer)

The principle: the larger the invoice, the faster you escalate and the sooner you pick up the phone. A $4,000 invoice sitting 14 days past due with no response is not a situation for another email. It is a phone call on day 5.

---

## Should the Second Reminder Be an Email, Text, or Phone Call?

The channel for your second reminder should almost always be different from the first.

**If your first reminder was an email → send a text or call.** Text messages have an open rate of around 98%, compared to 20–30% for commercial email. A short, direct text referencing the invoice number and amount gets seen. For invoices over $1,000, skip the text and go straight to a call. The stakes are high enough to warrant direct communication, and a two-minute voice conversation resolves ambiguity — a dispute, a lost invoice, a timing issue — far faster than another email chain.

**If your first reminder was a text → call.** Customers who ignored a text are not waiting to read a follow-up text. Escalate.

**If your first reminder was a call and they didn't answer → leave a specific voicemail and immediately follow with a text.** The voicemail should include the invoice number, the dollar amount, and one clear action they can take right now: "Invoice #4421 for $1,850 from March 3rd is now 7 days overdue. Please pay at [link] or call me back at [number]." Send the same information by text within 60 seconds — some customers will tap a text link before they return a call.

---

## A Real-World Example: How the Channel Switch Changes Everything

A landscaping contractor in the Dallas area had a recurring client on a $900/month maintenance contract. The April invoice went out on April 1st with Net 30 terms, due April 30th. By May 7th — seven days past due — no payment had come in.

The contractor had already sent an email reminder on May 1st. No response.

**The wrong second move:** Send another email on May 7th with the subject line "Second reminder: Invoice due."

**The right second move:** A direct text on May 7th: "Hi [Name], this is [Company]. Invoice #2031 for $900 (April maintenance) is now a week past due. Pay here: [link] or reply if there's a problem."

The text got a reply within an hour: "Sorry, I missed it — I'll pay today." Payment came through the same day.

The issue had nothing to do with the customer avoiding payment. The original email had landed in Gmail's Promotions tab and the customer never saw it. Switching to a text fixed the problem in 60 seconds.

This is the most common outcome with a properly executed second reminder: the customer wasn't ignoring you, they just missed the first one. Changing the channel surfaces the invoice to someone who fully intends to pay. The failure scenario — where a customer sees two reminders and still doesn't respond — is where you need the escalation steps below.

---

## What to Do When the Second Reminder Gets No Response

If your second reminder — whether it was a text, a call, or a voicemail — goes unanswered for 48 hours, the situation has shifted. This is no longer a "they'll probably pay soon" scenario. It requires active resolution.

**Step 1: Call during business hours and ask for the right person.** For residential clients, call between 10 AM and 6 PM local time. For commercial accounts, contact accounts payable directly rather than just your project contact — your contact may not be the one who initiates payment.

**Step 2: When you reach someone, keep it short and factual.** "I'm following up on invoice #[X] for $[amount], which is [N] days past due. I want to make sure there isn't an issue on our end, and if there is, I'd like to resolve it today." This framing is collaborative rather than accusatory, and most customers respond better to it than to a confrontational opener.

**Step 3: If calls go unanswered and the invoice is 14+ days past due, send a formal written demand.** Deliver it by email and by certified mail for amounts over $1,000. State the balance, the original due date, and a specific deadline for what happens next: "If we do not receive payment or a confirmed payment arrangement by [date], we will [charge late fees / pause service / escalate to collections]." In many states, a written demand is also required before you can file a mechanics lien on service work.

**Step 4: Follow through on every stated consequence.** If you said service pauses at day 21 and it doesn't, you've signaled that your deadlines are negotiable. Customers who are intentionally stalling will extend indefinitely once they learn your follow-ups don't have teeth.

---

## The Common Mistake: Identical Reminders With Different Subject Lines

A pattern worth naming directly: sending the same reminder email three times with slightly different subject lines.

"Reminder: Invoice #4421 is past due" "REMINDER: Invoice #4421 — payment needed" "Final reminder: Invoice #4421"

This sequence looks like escalation but isn't. Every message lands in the same inbox, uses the same format, and asks for the same thing. A customer who is avoiding payment learns quickly that "final" doesn't mean anything. A customer who missed the first email won't see the second or third for the same reason they missed the first.

Escalation means a different medium, a different level of directness, or a different consequence. Escalation does not mean sending the same email with a more alarming subject line.

---

## Building a Reminder Schedule You'll Actually Execute

The biggest obstacle to running a consistent two-reminder sequence isn't knowing the right approach — it's applying it consistently across 15 or 20 open invoices at different points in their billing cycles.

A system that holds:

1. **A weekly AR aging review on a fixed day.** Every Monday morning, 10 minutes. Know which invoices cross the 7-day and 14-day thresholds this week before the day starts.

2. **A defined rule for each threshold.** Day 7 past due = text or call. Day 14 past due = formal written demand. Decide the rule once and apply it to every account — don't decide case by case, because case-by-case decisions always skew toward inaction.

3. **A logged record of every outreach.** Date, channel used, what was said or left as a voicemail. If an account reaches the point of small claims court or a collections escalation, documented attempts are meaningful. "I called on May 7th at 2:14 PM, left a voicemail, and sent a follow-up text at 2:15 PM" is a record. "I tried to reach them several times" is not.

4. **A tool or person for volume you can't personally manage.** If you have more than 10 overdue invoices at once, manually executing a channel-escalating reminder cadence for each becomes a significant time commitment. Either delegate it or use a system that handles the outreach automatically.

---

## The Hands-Off Alternative

If tracking which invoice needs its second reminder this week — and whether that second reminder should be a text, a call, or a voicemail — sounds like more than your schedule allows, Syntharra handles it automatically. The AI voice agent calls your overdue customers directly, references the specific invoice, and asks about payment — the same direct voice conversation that gets 60% of overdue invoices paid, without requiring your time. No monthly fee. You pay 10% only when an invoice is recovered.

See how it works →