Contents
Overview
If voicemail-to-email and/or missed-call alert emails are not arriving for inbound numbers configured in the Nucleus/BCH portal, the cause is typically either (1) a configuration mismatch (the number is not actually pointing to the intended mailbox) or (2) a carrier/provider-side email-notification delivery incident.
In the scenario documented here, configuration was verified and controlled testing still showed no delivery, confirming a provider-side delivery incident. Delivery resumed after provider remediation; no application defect or version-specific fix was identified.
Solution
Issue
Voicemail and/or missed-call notification emails are not received for inbound numbers configured in the Nucleus/BCH portal, even though notification email addresses are already configured.
How it presents
- Missed calls occur but no missed-call alert email arrives.
- Voicemail is left but no voicemail-to-email message/attachment arrives.
- Nothing appears in the destination mailbox (including Inbox and Junk/Spam).
Common root-cause patterns
- Configuration mismatch: The number’s notification destination email may not be set to the mailbox you expect (for example, an old or unintended address).
- Provider-side delivery incident: Even with correct configuration, the carrier/provider’s email-notification service can be degraded or interrupted, preventing delivery.
Resolution / Mitigation Steps
1) Verify the Nucleus configuration for each affected number
In the Nucleus/BCH portal, confirm for each affected number:
- Missed Call Alerts: confirm the saved destination email (or email group) is correct.
- Voicemail settings: confirm voicemail is configured to send messages via email (voicemail-to-email) to the intended destination.
If an affected number is configured to an unexpected mailbox, update it to the intended mailbox and save changes.
2) Run a controlled test to separate “mailbox issue” vs “platform/provider issue”
After confirming configuration:
- Temporarily set the notification destination to a mailbox you can directly access (for example, a test mailbox at your organization or a controlled external mailbox).
- Place a test call to the affected number:
- Create a missed call (do not answer) to trigger a missed-call alert.
- Leave a voicemail to trigger voicemail-to-email.
- Check the destination mailbox (Inbox and Junk/Spam at minimum).
Interpretation:
- If delivery works to the controlled mailbox, the issue is likely mailbox-side filtering/routing for the original recipient(s).
- If delivery still fails to the controlled mailbox, the issue is more likely provider-side notification delivery.
3) Escalate to the carrier/provider when configuration is correct but delivery fails
If configuration is correct and a controlled test still produces no notification emails, escalate to the carrier/provider and include the following details:
- Affected number(s):
<number_1>,<number_2> - Configured notification mailbox(es):
<notification_mailbox_1>,<notification_mailbox_2> - Test call timestamp(s) with timezone
- Calling number(s) used for the test
- Whether a missed-call alert, voicemail email, or both were expected
- Observed result: “No email received (including Junk/Spam)”
If the provider identifies an incident on their side, delivery may resume only after provider remediation.
Validation (Confirm It’s Fixed)
- Confirm each number’s Missed Call Alerts and Voicemail-to-email destinations are set to the intended mailbox(es).
- Place test calls for each number:
- One missed call (no answer)
- One call leaving voicemail
- Confirm:
- Missed-call alert email arrives
- Voicemail email arrives (with attachment if configured)
- If the provider indicates resolution, re-test and record the first successful delivery time for reference.
Frequently Asked Questions
- 1. How do I know this is the same issue?
- You see missed calls and/or voicemails occurring, but no missed-call alert or voicemail-to-email messages arrive (including Junk/Spam), often reported as “Nothing appeared”, despite having email destinations configured in the Nucleus/BCH portal.
- 2. What’s the first thing to check if notifications aren’t arriving?
- Confirm the Nucleus configuration is actually pointing to the intended mailbox for each number (Missed Call Alerts and voicemail-to-email destination). A common cause is that one number is configured to an unexpected mailbox.
- 3. If the email address is correct, what’s the next best test?
- Temporarily set notifications to a mailbox you can directly access and run a controlled missed-call + voicemail test. If nothing arrives even there, escalate as a likely provider-side notification delivery problem.
- 4. When should this be escalated to the carrier/provider?
- Escalate when (1) configuration is confirmed correct and (2) controlled testing still produces no notification emails (including Junk/Spam). Provide timestamps, calling numbers, affected number(s), expected notification type(s), and the observed “no email received” outcome.
- 5. What should I do after the provider says the incident is resolved?
- Restore the intended notification mailbox(es) (if you changed them for testing), then run fresh missed-call and voicemail tests on each affected number to confirm delivery has resumed.
Matthew Mrosko
Comments