Avoiding billing surprises is a numerical exercise, not a gut feel. With clear thresholds, the team makes upgrade or optimization decisions on time.
A threshold is not a panic button; it is a decision trigger. Notice at 70%, act at 90% — that simple rule removes billing surprises.
Metrics worth tracking
- Monthly active reviews.
- AI Co-Pilot draft count.
- API call volume.
- Active restaurants and team members.
- Webhook delivery count.
Threshold logic
At 70% of plan limit, a soft signal (color or badge) is enough. At 90%, an action-forcing notification helps. This pattern lets the team make plan changes calmly a few days before month end.
Reducing usage
Sometimes optimization is enough instead of upgrading: archive inactive restaurants, disable unused webhooks, cache unnecessary API calls.
Kontrol listesi / Checklist
- Threshold policy is written down.
- 70% and 90% reminders are active.
- Inactive restaurants archived.
- API call volume tracked.
- Upgrade decisions made 5 days early.
SSS / FAQ
Does the system upgrade automatically when a threshold is crossed?
No. Plan changes always require manual confirmation. This eliminates surprise charges.
Can I send threshold notifications to the manager only?
Yes. Notification emails should go to authorized people, not the whole team.