Question 1

How reliable is the Stripe webhook for stopping the sequence?

Accepted Answer

The blueprint watches Stripe for the invoice.paid event (and the equivalent status update in FreshBooks, Wave, QuickBooks, or HoneyBook). Stripe webhooks are highly reliable in practice, and Make retries failed webhook calls automatically. The scenario also re-checks payment status before each of the three follow-ups, so even a delayed webhook cannot cause a duplicate send.

Question 2

What is the tone of each of the three reminder emails?

Accepted Answer

Day 3 is a warm, low-pressure nudge — assumes the client simply overlooked the invoice. Day 7 is firm and direct, with clear payment instructions and a direct invoice link. Day 14 is the final notice — outlines next steps and signals consequences without hostility. All three copy files are fully editable, so you can adjust tone or reword per your client relationship.

Question 3

What happens after the day-14 final notice?

Accepted Answer

The final-notice email closes the sequence — no further automatic sends go out. You decide whether to take the next step manually (late-fee invoice, collections partner, write-off). The blueprint writes a "Final notice sent" marker on the invoice row so your records show the sequence ran to completion, and you can build a downstream handoff in Make if you want a Slack ping or a CRM update at that point.

Question 4

Does the sequence handle multi-currency invoices?

Accepted Answer

Yes. The blueprint reads the invoice amount and currency directly from your invoicing source and passes them into the email body as the original values — a 1,200 EUR invoice stays EUR through all three reminders. The day-7 follow-up includes the original currency code in the payment instructions so the client never has to guess at conversion.

Question 5

What happens if the client makes a partial payment?

Accepted Answer

A partial payment does not stop the sequence on its own — the remaining balance is still overdue. The blueprint includes an optional branch you can enable that swaps the day-7 copy to a "balance remaining" version once a partial payment is detected, so the reminder references the correct outstanding amount. Disable the branch and the standard day-7 reminder fires as written.

Stop chasing overdue invoices — let Make follow up for you

What you get when you buy

Four steps. One overdue invoice. Zero chasing.

From purchase to live in under an hour

Buy & download

Import the blueprint

Connect & go live

Overdue invoices that chase themselves

Questions before you buy

Pairs well with this

Stop writing the same follow-up email every time an invoice goes overdue.