Home Troubleshooting & Error Resolution Missing Call Allowance Expiration Notifications โ€“ Causes & Prevention

Missing Call Allowance Expiration Notifications โ€“ Causes & Prevention

Last updated on Jun 18, 2025

๐Ÿงญ Overview

EvoVoice automatically sends call allowance expiration notifications to clients nearing or exceeding their usage limits. However, there are cases where clients report not receiving these alerts. This guide explains the underlying causes and outlines steps to ensure consistent delivery of these critical notifications.


โš ๏ธ What Is a Call Allowance Notification?

These alerts notify the client when they are:

  • Close to their monthly usage limit

  • About to be charged for overage

  • Reaching the expiration date of a prepaid allowance or usage cycle


๐Ÿ” Common Reasons Notifications Are Not Received

Cause Description
๐Ÿ“ญ Email Routing Issues Email flagged as spam or blocked by the recipientโ€™s mail server
๐Ÿ“ค Incorrect Notification Email The wrong or outdated recipient email is set in the client's PBX or billing profile
โ›” Notification System Disabled Allowance tracking notifications may be toggled off in system settings
๐Ÿงพ No Allowance Applied If no call allowance package is configured, there may be no threshold to trigger the alert
๐Ÿ” Automation Errors or Sync Delays Backend sync delays may skip or delay notifications if settings are not updated

โœ… How to Ensure Notifications Are Sent Consistently

๐Ÿ”น 1. Verify Call Allowance Package Is Active

  • Check client billing profile or system configuration:

    • A valid call allowance or usage bundle should be attached

    • Confirm start and end dates are accurate

๐Ÿ“Œ If no package is assigned, no expiration or usage alert will be triggered.


๐Ÿ”น 2. Confirm Notification Settings Are Enabled

  • In Evo Admin or PBX portal:

    • Go to Notifications > Usage Alerts

    • Ensure email alerts are enabled for call limits

    • Select frequency (e.g., 80% usage, 100%, expiration date)


๐Ÿ”น 3. Review and Update Notification Recipients

  • Check that a valid recipient email is on file:

    • Business owner

    • Billing contact

    • Primary admin user

  • Avoid generic or outdated email addresses (e.g., info@, support@)


๐Ÿ”น 4. Test Delivery and Whitelist Evo Notifications

  • Ask client to check spam/junk folder

  • Advise client to whitelist Evo system emails:

  • Run a test notification (where applicable) to validate delivery


๐Ÿ”น 5. Monitor for Automation Gaps

  • Review backend automation logs or usage rules to confirm:

    • No failures in threshold-based triggers

    • Allowance expiration triggers are up to date

  • Rebuild or restart automation if sync issues are suspected


๐Ÿงช Troubleshooting Tips

Symptom Possible Fix
Notifications not received at all Recheck notification toggle & recipient email
Received late or after allowance expired Check automation sync and cycle dates
Alerts go to wrong person Update contact email in billing settings
No notification even with usage Ensure correct package with thresholds is assigned

๐Ÿ†˜ Still Need Help?

If the issue persists:

  • Create a Freshdesk ticket with the clientโ€™s name and company

  • Include: screenshot of billing plan, intended recipient email, usage history

  • Evo Support can run a backend check and adjust notifications accordingly