Per-invoice fiddling and half-baked free tiers create exactly the revenue leak you’re trying to stop. They hide costs: missed service windows, late payments, double-bookings, and staff time wasted chasing payments. Fix the flow; stop treating reminders as an afterthought.
Why this decision matters
Picking the wrong tool or leaving reminder toggles split across systems costs cash and time. Missed or misconfigured reminders mean unpaid invoices sit for weeks, crews idle waiting for payment clearance, and office staff double their work.
Audit who touches an invoice (creates, sends, marks sent) — that single check surfaces most failure modes. Treat free tiers as testing grounds only; they usually lack SMS or reliable automation for production.
Common bottlenecks
- The Silent Credit Drain: Unsent or misfired reminders push collections weeks out, increasing write-offs and manual chase time.
- The Setup Tax: Per-invoice toggles plus global toggles create easy configuration gaps that stop automation cold.
- Duplicated Noise: Two systems sending reminders (bookkeeping + FSM) doubles client contacts and increases disputes.
Use invoice status as the source of truth for reminders.
Decision logic
- IF If budget = $0 for start OR team size ≤ 2 → Start on the free FSM Lite to validate templates and manual flows; plan to upgrade once you hit ~50 invoices/month or need SMS automation.
- IF If >100 invoices/month OR more than 3 crews → Choose a paid tier with native batch invoice generation and built-in Automations—don’t rely on CSV hacks or manual sends at scale.
- IF If you require SMS reminders and controlled send windows → Pick a tool that exposes SMS Settings and reminder timing. Enable SMS in settings before turning on reminders and set a daytime send window (e.g., 08:00–20:00) with a 24–48 hour lead to avoid late-night sends.
- IF If you must attach invoices/receipts to reminders → Confirm the tool supports Attach PDF copy and that attachments travel via both email and any SMS-linked delivery; test with real customers before rolling out.
- IF If an external accounting system also sends reminders → Centralize reminder authority: disable reminders in one system (preferably the bookkeeping app) so only the FSM suite manages overdue notifications and avoids duplicates.
Scenarios
Low volume, tight control: Use a free FSM Lite tier to test templates and manual reminders. Generate invoices at job completion and send once manually. Rely on email if SMS costs are blocking; upgrade only once volume or missed payments justify paid automations.
Bulk generation and hands-off follow-ups: Pick a paid FSM tier that supports native batch invoice creation and Automations (Tool 1 paid tier or Tool 3). Build rules that trigger on invoice status so reminders fire reliably without manual CSV workarounds.
Attach receipts, reduce disputes: Choose a tool that can attach PDF copies to reminders and optionally send SMS copies (Tool 3 or Tool 2). Configure templates, limit send windows, and audit messaging quarterly to avoid awkward timing or tone.
Frequently Asked Questions
Reminder didn’t send — what do I check first?
Check the invoice status and toggle state. Open the invoice and verify it’s marked Sent (not Draft), confirm both global and per-invoice reminder toggles, and ensure the Email/SMS channel is enabled. Then view the invoice activity log (All time + timeframe) to see what actually ran.
Can I get production-grade email + SMS on a free tier?
No. Most free plans limit users or omit SMS and advanced automations. Expect to pay once you need reliable SMS delivery, controlled cadence, or higher volume.
Why are clients getting duplicate reminders?
It depends. Usually duplicates come from two systems both sending (bookkeeping tool + FSM) or from forgetting to Mark Sent when invoices were sent externally. Disable one reminder source or standardize the Send→Mark Sent workflow so only the system owning the invoice status sends follow-ups.
Tools that will probably work best for: How to set up invoice reminder email and SMS
Compare all tools →
How this guide was made: The structure and research for this guide were developed by Rafał Woźniak based on hands-on experience with SaaS workflows. The content was written with AI assistance and reviewed before publication. Editorial policy →