This article covers common voice call delivery issues in Finalsite, including how to diagnose calls that silently fail with a "No Answer" status and how to resolve carrier-level spam filtering that prevents recipients from receiving voice messages.
💡Quick answers
- Why are recipients getting "No Answer" when their phone never rang? The most common cause is carrier-level spam filtering. The carrier silently drops the call before it reaches the handset, so the recipient's phone never rings, but the platform still logs the outcome as No Answer.
- What is the fastest first step? Have an affected recipient add the district's outbound caller ID number to their Contacts app. This often bypasses local device filters immediately.
- What is the long-term fix? Register the district's calling numbers with the three major carrier registrars: First Orion, TNS, and Hiya. This establishes the number as a legitimate caller across all major networks. See the registration guide for step-by-step instructions.
- How long does carrier registration take? Up to three weeks for full network-wide propagation across all three registries.
In this article
Why calls silently fail
When a carrier's system flags an outbound caller ID as possible spam or a possible scam, it silently drops the call before it reaches the recipient's handset. Because the network processes the call but the physical device never receives it, the platform logs the outcome as No Answer, even though the recipient's phone never rang.
This behavior is triggered by carrier-level spam-detection algorithms that score calling numbers on volume, duration, and pattern. High-volume, short, repetitive calls, the profile of mass school notifications, can match the spam profile. The fix involves both immediate device-level steps and a longer-term carrier registration process.
Troubleshoot a "No Answer" delivery issue
Work through the steps below in order. Steps 1-3 can resolve individual cases quickly. Step 4 is the long-term fix that prevents the issue from recurring.
Step 1: Run a test call and record the details
Send a test call or voice message to the exact phone number(s) affected. Record the following before moving on:
- The precise timestamp of the test
- The recipient phone number(s)
- The delivery status shown in the platform
These details are needed to investigate further if the issue persists.
Step 2: Add the caller ID number to the recipient's contacts
Have the affected recipient add the district's outbound caller ID phone number directly to their device's Contacts app. This often whitelists the number or bypasses basic local filters and can resolve the issue immediately without any further steps.
Step 3: Check carrier and device-level filters
If adding to contacts does not resolve the issue, the recipient's carrier app or device settings may be blocking the number.
Carrier apps: Some carriers run their own spam-filtering apps that can auto-block numbers. For example, Verizon subscribers should open the My Verizon or Verizon Call Filter app, review the block list, and remove the district's caller ID number if it appears there.
Apple iOS (iPhone):
- Go to Settings > Apps > Phone > Unknown Callers under Call Filtering. If "Silence Unknown Callers" is turned on, unsaved numbers are sent straight to voicemail without ringing.
- Also check Settings > Phone > Blocked Contacts to confirm the number has not been manually blocked.
Google Pixel and Android:
- Open the Phone app, go to Settings > Spam and Call Screen. Confirm that "Filter spam calls" or "Call Screen" is not silently intercepting the call.
- Also go to Phone app > Settings > Blocked Numbers to confirm the caller ID number is not listed.
Step 4: Register calling numbers with the carrier registrars
Steps 1-3 address individual cases. To prevent the issue from recurring across all recipients and carriers, register the district's outbound caller ID numbers with the three primary carrier registrars. This establishes the number as a verified, legitimate caller across all major networks.
| Registrar | Carrier coverage | Where to register |
|---|---|---|
| First Orion | T-Mobile and associated MVNOs | portal.firstorion.com |
| TNS | Verizon, Charter, Comcast, and major regional carriers | voicespamfeedback.com/vsf |
| Hiya | AT&T, major Canadian and international carriers | hiya.com/products/connect/number-registration |
For full step-by-step registration instructions, check out the article, "Register district calling numbers to prevent spam labeling".
Propagation timeline: after submitting to all three registrars, allow up to three weeks for full network-wide propagation.
Additional resources
- First Orion portal: portal.firstorion.com
- TNS - Voice Spam Feedback: voicespamfeedback.com/vsf
- Hiya Connect: hiya.com/products/connect/number-registration