Fax was supposed to disappear twenty years ago. It did not. In healthcare, legal services, financial services and government, the fax number is still a working address: often the one an institution will accept a signed document at when it will not accept an email. What has changed is the machine. The document still travels as a fax; almost nothing about the office around it needs to.
This guide covers what electronic fax is, why the format has outlived its obituaries, how a cloud fax service actually works, and what to weigh before moving off physical machines and analog lines.
Why fax is still here
Three things keep fax in service, and none of them is inertia alone.
It is an accepted channel for signed documents. Many institutions treat a received fax as an acceptable record of a document that was sent, at a time, to a number they control. That is a workflow decision made by the receiving organization, and a sender rarely gets to overrule it. If your referral partner, claims processor or county clerk accepts fax and not email attachments, the argument is over.
It is point to point. A fax goes to a number, not to an inbox that forwards, auto-replies, or sits on a device somebody left in a taxi. That is a narrow property, but in regulated workflows a narrow, predictable delivery path is worth something.
The alternative is not one thing. Replacing fax across a supply chain means agreeing on a portal, a secure email standard, or an interchange format with every counterparty. Organizations that have tried this generally find that they can move some partners and not others, and that the fax line has to stay up for the remainder either way.
The practical consequence is that most organizations are not choosing between fax and no fax. They are choosing between fax on hardware and fax as a service.
What electronic fax actually is
Electronic fax (cloud fax, online fax, fax as a service) keeps the fax number and the fax protocol, and removes the machine, the dedicated analog line and the paper.
A provider hosts your fax numbers on their infrastructure. Inbound faxes arrive at that infrastructure, are converted to a digital document, and are delivered to you by email, a web portal, or an API into another system. Outbound faxes go the other way: you submit a document from email, a browser or an application, and the provider converts it and transmits it to the destination fax number using the fax protocol that the receiving machine expects.
The important consequence is asymmetry. You stop operating fax hardware; your counterparties do not have to change anything at all. The clinic still has a fax machine and still receives a fax. That is precisely why this migration is possible without a negotiation.
The protocol detail that matters
Traditional fax is defined by ITU-T Recommendation T.30 and was designed for analog telephone lines. When voice networks moved to IP, fax did not survive the transition cleanly: the compression and packet loss that are inaudible in a phone call are destructive to a fax transmission. The standard response is ITU-T Recommendation T.38, which carries fax over IP networks as fax data rather than as audio.
This is worth understanding because it explains a common and frustrating failure: fax machines plugged into ordinary VoIP lines that work intermittently, drop pages, or fail on long documents. A fax service handles the protocol conversion on infrastructure built for it. If you have been fighting unreliable fax over a VoIP line, that is the problem you are actually solving.
How it changes the work
The visible change is that faxes arrive as documents and leave from applications. The changes that matter operationally are less obvious.
Faxes become searchable records. A received fax is a file with a timestamp and a sender number, stored with the rest of them, rather than paper in a tray that somebody has to notice.
Receiving stops depending on presence. A fax arriving at 6pm reaches the person who needs it wherever they are, instead of waiting on a machine until somebody walks past it.
Failures become visible. A transmission that did not complete is reported. On a physical machine, a failed send is a confirmation page nobody reads and a document nobody knows did not arrive.
Access becomes something you administer. Who can send from which number, and who can see what arrived, becomes an account question rather than a question of who is standing near the machine.
That last point is the one regulated organizations should sit with. A fax machine in a shared corridor has no access control at all. Most of the compliance argument for cloud fax is not that faxing becomes secure. It is that faxing becomes administrable.
What to weigh before moving
Your real volume, in pages
Fax services are priced by pages, not by documents or users. Before comparing anything, find your actual monthly inbound and outbound page count. Organizations routinely guess this wrong in both directions: a practice that "barely faxes" may be receiving several hundred pages a month of returned forms.
What has to keep working
List the numbers that must survive the move. If a number is printed on forms, referral pads, or a state license, it has to port rather than be replaced. Number porting is a scheduling exercise with the losing carrier, not a switch you flip, and it should be started early.
Where the documents need to end up
Email delivery is the easy case. If faxes need to land in a records system, a case management tool or a shared drive, that is an integration question and it belongs in the evaluation rather than after it.
Who has to be able to send
Fax services are usually licensed per user as well as per page. Count the people who need to send in their own name, not the people who occasionally walk to the machine.
Retention and storage
Cloud fax turns every fax into a stored document, which is useful until it becomes a retention obligation. Decide how long faxes should be kept and confirm that the storage included in a plan matches that decision.
The compliance question, stated carefully
Faxing is not prohibited under HIPAA, and no service can make an organization compliant on its own. The HIPAA Security Rule sets requirements for the confidentiality, integrity and availability of electronic protected health information, and a covered entity remains responsible for meeting them. What a service can do is provide the safeguards you build on: encryption in transit and at rest, access control, an audit trail of what was sent and received, and a Business Associate Agreement where the provider handles PHI on your behalf.
The same distinction applies elsewhere. GDPR governs personal data of people in the EU regardless of the channel it moves through; PCI DSS governs cardholder data. A provider can hold certifications and offer contractual terms. It cannot decide what your staff fax, to whom, or how long you keep it.
Treat a compliance claim in a supplier's marketing as the beginning of a question, not the end of one. Ask what is certified, by whom, against which standard, and when it was last assessed.
Where to go next
If you are still establishing what the term covers, start with What Is Electronic Fax?. If the decision is close and the question is budget, How Much Does Electronic Fax Cost? sets out what drives the number. If you are comparing providers, What to Look For in Electronic Fax is the list of questions worth asking.
You can also talk to us about your fax requirements. We will look at your page volumes, the numbers that need to port and where the documents have to end up, and tell you what a move would involve.
Sources
- ITU-T Recommendation T.38: procedures for real-time Group 3 facsimile over IP networks.
- ITU-T Recommendation T.30: procedures for document facsimile transmission.
- 45 CFR Part 164, Subpart C: HIPAA Security Rule, Electronic Code of Federal Regulations.