Why Faxes Fail (and How to Fix It) | SecurelyFax
Most fax failures come down to a handful of predictable causes — wrong destination number, a voice line that doesn't answer fax tones, a file that's too large for the recipient's machine, a busy line, or a recipient machine that's offline. Online fax services like SecurelyFax retry automatically on transient errors and surface the specific failure reason so you know what to fix.
The most common causes (ranked roughly by frequency)
1. **Wrong destination number** — by far the most common. Double-check every digit on the recipient's instructions.
2. **Voice line, not fax line** — the number dials but a person or voicemail picks up instead of fax tones. The recipient may have a separate fax number; ask.
3. **Recipient machine busy** — someone else's fax is in progress. Retry in a few minutes.
4. **Recipient machine offline** — out of paper, jammed, or powered down. Less common today since many recipients use online fax services that don't have these failure modes.
5. **Page count too large** — older fax machines may reject a fax over 50-100 pages. Split into smaller batches if the recipient's setup is older.
6. **Connection dropped mid-transmission** — a noisy line or a carrier hiccup. Retry usually fixes it.
7. **Wrong file type** — most online fax services accept PDF, JPG, PNG, and similar; unusual formats may be rejected before transmission.
Voice line vs fax line — the trickiest case
Many businesses moved off dedicated fax lines years ago. The published "fax number" on a website might now ring to a voice menu, a cell phone, or a number that no longer exists. Symptom: SecurelyFax dials, the carrier connects, but no fax handshake happens — and the receipt reports something like "no answer" or "voice line detected." The fix is to call the recipient at a known phone number and confirm the current fax number.
What to do when a fax fails
-
1
Read the failure reasonSecurelyFax records the specific reason on the failed fax. "Busy" means retry; "no answer" or "voice line" means double-check the number.
-
2
Verify the destination numberLook at the original recipient instructions, not a number you copied earlier. Numbers change.
-
3
Retry onceMany failures are transient — busy line, dropped call. A single retry resolves most of them.
-
4
Call the recipient if it fails againConfirm the current fax number with the receiving office. Update your records.
-
5
Try a smaller batchIf the recipient's machine is older and the fax was very long, split into two sends.
Why SecurelyFax sends don't fail the way old machines did
Online fax bypasses most of the old failure modes. There's no toner, no paper jam on your side, no analog line noise, and the carrier handles retries on transient errors. The failures that remain are recipient-side: wrong number, busy line, recipient machine offline. Those are fixable; old fax-machine failures often weren't.
Failed sends don't charge against your account credits — only successfully delivered pages are billed. If a failure appears to be on SecurelyFax's side rather than recipient-side, contact support with the fax ID and we'll investigate the carrier-side log.
Frequently asked questions
Why does my fax say "no answer" but the number works?
The number probably rings to a voice line rather than a fax line. Call the recipient and ask for their current fax number.
Why does my fax keep failing on the same recipient?
Either the number is wrong, the recipient's machine is offline, or there's a persistent issue with the receiving line. Call the recipient to confirm.
Do I get charged for failed faxes?
No. SecurelyFax only bills for successfully delivered pages.
How many times will SecurelyFax retry?
Transient errors like "busy" get automatic carrier-side retries within a short window. Hard failures ("no answer," "no fax detected") are reported back to you immediately so you can fix the underlying problem.
What's the largest fax I can send?
SecurelyFax accepts files up to the platform's max upload size. Many recipients' machines comfortably handle 50-100 pages; split into multiple sends if you have a very long document and the recipient's setup is older.
Last reviewed: 2026-05-30