Short Answer
Most notification issues are caused by filters (e.g., sending to the wrong group), missing or invalid contact information, or message volume hitting email/SMS limits.
Why This Happens
Filters: Sending to “all riders” works, but sending to a single bus or subset can miss riders if filters don’t match your intent (e.g., route vs. trip vs. rider list).
Contact data: Some riders have no email/phone or are not marked as text-capable, so notifications quietly fail for those contacts.
Volume & limits: Large batches can trigger limits or delays on district email servers or SMS gateways.
What You Can Do
-
Verify who you’re actually targeting
-
In Notifications / Real-time Notifications, double-check:
You filtered on the correct route / trip / bus.
You’re not accidentally targeting a broader or different group than intended.
-
-
Spot-check sample students
-
Open a few student records:
Confirm at least one parent/guardian has a valid email or mobile number.
Verify the mobile number is marked as allowed to receive texts (if you’re using SMS).
-
-
Check notification status/logs
-
Look for:
Messages in queued/pending state.
Bounced/invalid addresses or error messages.
-
-
Try a smaller test batch
-
Send a short test message to:
A single route, or
A small set of riders you can easily verify with.
-
When to Contact Support
Reach out to EZRouting Support when:
Messages to a small test group still don’t send.
You see errors in notification logs you don’t recognize.
You suspect rate limits or spam filtering and need help coordinating with IT.
Related article: How do I send mass notifications to parents and what should I check if messages won’t send?
Updated