KoltrixPlan-Limit Emails: Prompting Upgrades Without Breaking Trust
Telling customers they're near a plan limit is a moment of trust. When to warn, what to show, what happens at 100%, and how to suggest an upgrade calmly.
On this page(8 sections)
A plan-limit email arrives at a delicate moment. The customer is using your product enough to hit a ceiling, which is good news for both of you, and you're about to ask them for more money, which they may or may not be ready for. Handle it well and the upgrade feels like a natural next step. Handle it badly and it feels like a toll booth that appeared on the road without warning.
Why limits deserve careful email
Usage-based limits are everywhere in SaaS: seats, projects, storage, API calls, contacts, messages sent. They exist for good reasons. They align price with value, protect shared infrastructure, and give growing customers a reason to upgrade.
The trouble starts when customers discover limits by running into them. A blocked workflow at 4 p.m. on a Friday, with no warning, damages trust far more than the upgrade price justifies. Good limit emails make sure that never happens.
The three moments to email
1. The early warning (around 80%)
The first email goes out when the customer has used most of their allowance, with enough time left to act calmly. Eighty percent is a common threshold; for limits that reset monthly, consider timing too. Hitting 80% on day 25 of the cycle is different from hitting it on day 5.
This email should be informational, not a sales pitch:
- What the limit is and how much they've used
- When it resets, if it does
- What happens if they reach it
- Their options, including doing nothing
2. At the limit (100%)
When the customer reaches the limit, tell them immediately and plainly what has changed. If something is now paused or blocked, say exactly what, and how to restore it.
This is the email that most needs to be accurate. "You've reached your limit" with no detail sends people hunting through settings pages, or to support.
3. After the limit (optional)
If the limit is soft, meaning you allow overage at extra cost or keep working with a grace period, a follow-up a few days later explaining what's accruing is good practice. Nobody likes discovering overage charges on an invoice.
Hard limits and soft limits
How you handle the 100% moment depends on what kind of limit it is.
| Limit type | What happens at 100% | Email tone |
|---|---|---|
| Hard, non-critical | Feature pauses until reset or upgrade | Clear, calm, options listed |
| Hard, critical (e.g. sending, API) | Workflow blocked | Urgent, specific, fast path to fix |
| Soft with overage | Keeps working, extra charges apply | Transparent about cost per unit |
| Soft with grace period | Keeps working for N days | Clear deadline, no surprise |
For anything business-critical, think hard before choosing a hard stop with no warning. If a customer's password reset emails stop sending because they hit a cap, their customers can't log in. A grace period or an overage option is often kinder and better for retention. Where hard caps are necessary, for example to protect shared sending reputation, warn early and make the limits visible in the product, not just in email.
For a concrete example: Koltrix enforces per-plan daily inbox and monthly API send caps in the API itself, and on its Pro plan API sends beyond the monthly allowance are billed as overage per thousand rather than blocked. The limits reference documents the numbers. Whatever your model, document it publicly so customers can plan.
Show real numbers
Vague limit emails create anxiety. Specific ones create decisions.
Weak:
You're approaching your plan limit. Upgrade now to avoid interruption.
Strong:
Subject: You've used 8,100 of your 10,000 monthly emails
Hi Leo,
Your workspace has sent 8,100 of the 10,000 emails included
in your Basic plan this month. Your allowance resets on
June 1, in 9 days.
At your current pace you'll reach the limit around May 27.
If that happens, new sends will pause until June 1 unless
you change plans.
Your options:
- Do nothing. If you stay under 10,000, nothing changes.
- Move to Plus (50,000 emails a month) from your billing page.
- Reply to this email if you're expecting a one-off spike
and we'll talk it through.
Usage details: [link to usage page]The plans in that example are illustrative. The email states the numbers, the date, the projection, the consequence and three honest options, including doing nothing.
Suggest the plan that fits
When you do suggest an upgrade, recommend the plan that matches their actual usage pattern, not the most expensive one. If they're slightly over the limit once a quarter, a big permanent upgrade isn't the right answer; an add-on or temporary bump might be. Customers notice when you recommend the right size, and they remember it at renewal time.
Also check who receives the email. Limit warnings should go to the account owner or billing admin, and ideally to anyone with permission to change the plan. Sending them to a user who can't act on them just creates internal forwarding.
Things to avoid
- Fake urgency. "Act now!" on an 80% warning with three weeks left.
- Surprise blocks. Reaching a hard limit with no prior warning.
- Hiding the reset date. Customers need to know whether waiting is an option.
- Repeated nagging. One email per threshold, not daily reminders.
- Upsell-only replies. If someone replies asking for a one-time exception, a human should answer.
A threshold plan to start from
| Threshold | Also show in product | |
|---|---|---|
| 80% | Informational warning with projection | Usage bar turns amber |
| 100% | Clear statement of what changed and how to fix it | Banner on relevant screens |
| 100% + 3 days (soft limits) | Accrued overage or grace period reminder | Banner with amount or deadline |
| After upgrade | Confirmation of new limits | Updated usage bar |
Key takeaways
- Warn before the limit, at a threshold that leaves time to act.
- At 100%, say exactly what's paused or charged and how to fix it.
- Show real usage numbers, reset dates and honest options, including doing nothing.
- Prefer grace periods or overage over hard stops for business-critical workflows.
- Recommend the plan that fits their pattern, and send it to someone who can act.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
