Introducing Fax Streaming: Real-Time Fax Page Delivery with Fax.Plus

By
Alohi Team
-
April 17, 2025
arrow left
BACK
Alohi logoScan.plusSign.plus
Fax.plus
Clock icon
10 min read
Last updated: March 11, 2026

Most fax services work the same way they always have: a document transmits, page by page, and your system receives nothing until the very last page has landed. Whether the document is 2 pages or 200, you wait for the entire batch before you can act on any of it.

For a lot of use cases, that's fine. But for industries where incoming documents trigger time-sensitive decisions (a patient referral, a loan application, a court filing, a customs release) that wait isn't just inconvenient. It's a competitive liability.

Fax Streaming is a feature available on the Fax.Plus API that eliminates that wait entirely. Instead of batching, it delivers each page the moment it's decoded, in real time, sequentially, as the fax comes in. This post explains how it works, where it matters most, and how to integrate it.

What Is Fax Streaming?

Fax Streaming is a real-time document delivery method that sends each individual page of an incoming fax to your application as soon as it is decoded, before the full transmission session is complete.

In a standard cloud fax setup, documents are delivered as a complete file: you receive a notification and a PDF only once every page has arrived and been assembled. Fax Streaming replaces this with an event-driven webhook model.

When Fax Streaming is enabled on your Fax.Plus account, the API fires a fax_page_received webhook event the moment each page is decoded. Each event delivers a lightweight JSON payload containing the fax session ID, page number, sender number, and destination number. The page itself is immediately available as a single-page TIFF file via the API. The in-progress fax carries a status of in_progress, allowing your system to start processing partial documents while the rest continues to arrive.

Full technical documentation is available in the Fax.Plus API webhook reference.

Batch Fax vs. Fax Streaming: What's the Actual Difference?

The difference comes down to when your application gets access to the content.

Standard batch delivery

Fax transmits page by page over the telecom session.
System waits for the session to close (all pages received).
Complete PDF is assembled and delivered via webhook or polling.
Your application acts on the document. Total wait: 2–50+ minutes depending on page count and line quality.

Fax Streaming delivery

Page 1 is decoded.
Webhook fires immediately. Your application receives the payload and can retrieve the single-page TIFF.
Pages 2, 3, 4… each trigger their own webhook event as they arrive.
Your application is processing content in parallel with the ongoing transmission. Time to first data: seconds.

For a 50-page document at standard baud rates, the difference between batch and streaming is the difference between acting at minute 45 and acting at second 10.

How do competing fax providers compare?

No competing provider offers per-page streaming delivery as a standard included feature. All major platforms use a batch model: the complete document is assembled server-side and only delivered after the final page is received. The one partial exception is Concord Technologies, which offers first-page preview during an active transmission, but only as a paid add-on bundle, not included in their base plan.

Provider Per-page streaming What their "real-time" actually means
Fax.Plus Yes
Standard on Enterprise
fax_page_received webhook fires on each decoded page during active transmission.
Concord Technologies First page only
Paid add-on
"Real-time status and job reporting" - status tracking in base plan; first-page preview only via paid "Advanced Next Step Bundle".
eFax (Consensus) No Webhook fires after full document is stored as PDF/TIFF on eFax servers. Application must then call API to download. "Real-time" = status update only, no per-page access.
RingCentral No Webhook or email notification fires on successful fax read or delivery. SDKs: C#, PHP, JS, Python. No inbound per-page event documented.
InterFAX (Upland) No Two-step inbound model: "Web Feedback" callback notifies app that fax arrived, then app must make a separate API call to retrieve the image. REST + SOAP. No per-page event.
iFax No Webhook fires on fax completion. Payload includes faxTotalPages and faxTransferredPages - but as post-completion data, not in-progress events.
Notifyre No Webhook fires on successful delivery, failed send, or incoming fax - all complete-document events. No per-page trigger.
ETHERFAX No REST API with Inbox controller for poll-based retrieval. No webhook per-page event documented; inbound access is pull-based.

Where Fax Streaming Makes the Biggest Difference

Real-time page delivery matters most wherever the first page of a document determines what happens next. Here's how it plays out across industries.

Healthcare: patient admissions and referral triage

Healthcare fax volume remains substantial. Penn Medicine alone receives an estimated 1.3 million records via fax annually (KLAS Research, 2023; Streiffer et al., 2024), and industry research confirms fax remains the dominant channel for referral data across health systems (KLAS Research, 2023). In acute and behavioral health settings, the speed at which a facility responds to an inbound referral directly determines whether they secure the patient.

With batch delivery, an admissions coordinator waits for a full patient history to arrive before they can read the name, insurance ID, or referring physician. With Fax Streaming, page one arrives in seconds: the coordinator identifies the patient, begins eligibility verification, and contacts the referring provider, all while pages 2 through 80 are still transmitting.

"The financial stakes are significant: U.S. hospitals lose an estimated $150 billion annually to referral leakage (patients lost to faster-responding competitors). (Modern Healthcare, 2020) That figure traces back, in large part, to document latency."

The Fax.Plus HIPAA-compliant fax API is purpose-built for this environment: AES-256 encryption at rest, TLS 1.2+ in transit, PHI omitted from webhook payloads, and BAAs available for all covered entities.

Law firms and legal operations teams receive high volumes of multi-page documents (contracts, discovery packages, court orders) where terms on page one can change the entire strategic posture of a case. Waiting 30 minutes for a batch to complete before a partner can read a filing deadline or a settlement figure is an unnecessary risk.

With Fax Streaming, document review can begin the moment transmission starts. For high-volume litigation support teams, this also means earlier queue routing: an intake system can read the cover page metadata and assign the document to the right attorney or matter before the full document has arrived.

Financial services: loan applications and transaction documents

Banks, mortgage processors, and financial advisors regularly receive multi-page application packages where the first page includes applicant identity, loan amount, property address and determines which underwriter or advisor handles the file. Streaming enables instant routing and earlier credit checks, compressing processing windows that currently stretch hours.

Logistics and customs: shipping documentation

For freight operators and customs brokers, a delayed bill of lading or commercial invoice can hold a shipment at port. Fax Streaming allows logistics systems to begin customs pre-clearance the moment documentation starts arriving, rather than waiting for a complete package.

Insurance: claims and policy documents

Claims adjusters can begin validation and coverage checks from page one of an incoming claim (with policy number, incident date, claimant identity) while supporting documentation continues to transmit. For high-volume claims operations, this removes a meaningful bottleneck from the triage queue.

How to Enable and Integrate Fax Streaming

Fax Streaming is available as an on-demand feature on Fax.Plus. It is enabled account-wide by contacting the Alohi sales team. Once activated, every member account with an assigned fax number automatically has access.

Integration overview

Configure your webhook endpoint to receive fax_page_received events in your Fax.Plus API settings.
When a fax begins arriving, your endpoint will receive an HTTP POST for each page as it is decoded.
Use the id (fax session ID) and page fields from the payload to retrieve the individual TIFF file via the Fax.Plus API.
Monitor the fax status field: in_progress while streaming, success when the session closes.
Process pages in your application logic as they arrive. Populate your intake form, route to a queue, begin a lookup, without waiting for the final page.

The architecture is stateless and developer-friendly: no polling loops, no session management overhead. A single webhook handler and the standard REST endpoints are all you need. SDKs are available for rapid integration.

Security and Compliance

Every page delivered via Fax Streaming is protected by the same infrastructure that governs the full Fax.Plus platform:

AES-256 encryption at rest, with per-user unique encryption keys.
TLS 1.2+ for all data in transit.
PHI omitted from webhook payloads entirely: server logs on your side are not contaminated with sensitive patient or client data.
Full compliance stack: HIPAA, ISO/IEC 27001 (certified by EY CertifyPoint), SOC 2 Type II, PCI-DSS, GDPR, CCPA, CSA STAR.
Business Associate Agreements (BAAs) available for all covered entities.
99.99% uptime. 4 million+ users across 190+ countries.

Alohi is headquartered in Geneva, Switzerland, and operates under the Swiss Federal Data Protection Act (FADP), with 20+ data residency locations globally. Full details are available in the Alohi Trust Center.

Who Should Enable Fax Streaming

Fax Streaming is the right choice when any of the following apply:

Your application needs to act on incoming fax content before a full document has been received.
You process multi-page documents where page one carries actionable data: a patient name, a claimant ID, a loan number, a case reference.
You are building a custom intake, routing, or triage workflow on top of the Fax.Plus API.
You are in a time-competitive environment where faster document access translates directly to faster decisions and better outcomes.
You are currently on a batching-based fax platform and experiencing delays that affect your workflow responsiveness.

If your use case is simpler (occasional low-volume faxes where delivery latency doesn't matter), standard webhook delivery remains fully available and works exactly as before. Fax Streaming is additive, not a replacement.

Getting Started

To enable Fax Streaming on your Fax.Plus account, contact the Alohi sales team. For technical integration, the full webhook reference is in the Fax.Plus API documentation, and the fax object reference is at apidoc.fax.plus/concepts/fax.

If you're evaluating Fax.Plus for a healthcare environment specifically, the HIPAA-compliant fax API guide and the healthcare industry page cover compliance architecture and BAA availability in detail.


Frequently Asked Questions

What is fax streaming?

Fax streaming is a real-time fax delivery method that sends each page of an incoming fax to your application individually, the moment it is decoded, rather than waiting for the complete document to finish transmitting before delivering anything.

How is fax streaming different from regular cloud fax?

Standard cloud fax services use a batch model: your application receives the full document only after every page has been transmitted and assembled. Fax streaming uses an event-driven webhook model that fires on every single page, giving your system access to content in seconds rather than minutes.

What is the fax_page_received webhook?

fax_page_received is a Fax.Plus API webhook event that fires the moment a single fax page is decoded during an active transmission. It is the core mechanism behind Fax Streaming, enabling applications to process pages in real time without polling.

Is fax streaming available for HIPAA-regulated environments?

Yes. The Fax.Plus fax streaming API is fully HIPAA compliant. All data is encrypted with AES-256 at rest and TLS 1.2+ in transit. PHI is omitted from webhook payloads. Business Associate Agreements (BAAs) are available for covered entities.

Which industries benefit most from fax streaming?

Any industry where incoming fax documents trigger time-sensitive decisions benefits from streaming. The highest-impact use cases are healthcare (patient admissions and referral triage), legal (contract and court filing intake), financial services (loan processing), logistics (customs documentation), and insurance (claims handling).

No items found.
No items found.
No items found.
No items found.
Related tags
No tag related
Secure eSignature Solution
Get your documents signed, sealed, and securely delivered with our compliant solution.
Secure Online Fax Service
Make paperwork unfold with ease as you send and receive faxes online across multiple platforms.
Fully Encrypted AI Powered Scanner
Transform your device into a powerful, portable document scanner.
Work that flows
We help companies and teams streamline document flows securely and efficiently.

Featured Articles

See All

Get Started Now

One intuitive account for all Alohi products. Sign up for a free account and seamlessly manage documents globally from any device.
Create Account