Most cloud fax services describe themselves in the same words. The differences that matter show up in the answers to specific questions: about numbers, protocol handling, contractual terms and what happens when you leave.
This is the list we would use. It applies to us as much as to anyone else, and several of the questions are ones a supplier would prefer you did not ask.
What to ask
About your numbers
- Can you port every number on this list, and how long will it take? Get the answer per number, not in general. Porting depends on the losing carrier and the number's current arrangement, and a number printed on forms or a license is not one you can quietly replace.
- What happens to my numbers if I leave? Ask this before you sign, not after. A number you cannot port out is a number that owns you.
- Can I get a toll-free number, and what does it cost?
About the transmission
- How do you handle fax over IP? You are looking for a specific answer about T.38 or an equivalent, not a reassurance. Fax was designed for analog lines and does not survive ordinary VoIP intact.
- What happens when a transmission fails? Is it retried, how many times, and how am I told? A failure nobody is told about is the failure mode that costs most.
- What is the largest document I can send reliably?
- Do you deliver a transmission record I can keep? Timestamp, destination, page count, result.
About security and compliance
- Is the document encrypted in transit and at rest, and with what?
- Will you sign a Business Associate Agreement? If you handle protected health information, this is not negotiable and the answer is yes or no.
- What exactly is certified, by whom, against which version, and when was it last assessed? A logo is not an answer. This is the single question that separates a real compliance posture from marketing.
- Who at your end can see my documents, and under what circumstances?
- Where is the data stored, and where is it processed? Relevant to GDPR and to some public-sector contracts regardless of GDPR.
About access and administration
- Can I control who sends from which number?
- Can I see who sent what, after the fact?
- What happens when someone leaves? How quickly can access be revoked, and what happens to their stored faxes.
About the fit with your systems
- Can faxes reach the system where the work actually happens? Email delivery is table stakes; a records system, case management tool or line-of-business application is an integration.
- Is that integration a product or a project? Both are legitimate answers. Being told it is a product when it is a project is not.
About the money
- What happens when I exceed the page allowance? Overage rate, throttling, or a forced upgrade, and is it charged per page or per plan step.
- Is storage included, and what happens when it fills?
- What is the contract term, and what is the notice period?
- Can I export everything, in a usable format, without asking?
What to compare
Once you have the answers, three comparisons are worth making and the rest is noise.
Total cost at your real volume, in your busiest month. Not the headline plan price, and not your average month. Add the toll-free number, the extra users and any storage you will genuinely need.
The failure path. What happens when a fax does not go through, and how long it takes you to find out. This is where cloud fax services actually differ from each other, and it is almost never on the comparison page.
The exit. Number portability out, data export, notice period. Evaluate the leaving as carefully as the joining, because you are choosing a supplier for a number that may be printed on your stationery.
Red flags
A compliance claim with no specifics. "HIPAA compliant" as a badge, with no answer to what is certified and by whom. No service makes an organization compliant; a service provides safeguards that the organization builds on. A supplier that blurs that line is either careless or hoping you are.
Vagueness about fax over IP. If the answer to the protocol question is a reassurance rather than a mechanism, the reliability problem you are trying to escape may follow you.
Numbers you cannot port out. Sometimes disclosed only in the terms, and occasionally not until you try.
Silent failures. If failed transmissions are not surfaced, you will find out from the counterparty who never received the document.
Unbounded overage. A per-page overage rate with no ceiling is a budget you do not control, and fax volumes spike seasonally.
Migration described as trivial. Moving the service is straightforward. Porting numbers, redirecting workflows and retiring hardware is a project with a critical path, and a supplier who says otherwise has not done many.
How to decide
Score on constraints first, then cost. Anything that cannot port your numbers, cannot sign the agreements you need, or cannot say how it handles fax over IP is out, not cheaper.
Of what remains, choose on the failure path and the exit rather than on feature lists. Feature lists converge; the behavior when something goes wrong does not.
Then run a real test before you commit. Send to and receive from the counterparties that matter most: the hospital, the claims processor, the court, and include a long document and a poor-quality scan. Those are the transmissions that fail, and they fail on the far end, which no demonstration environment reproduces.
Where to go next
How Much Does Electronic Fax Cost? sets out what drives the number and what LABUSA charges. Guide to Electronic Fax covers the whole subject, and What Is Electronic Fax? defines the terms.
If you would like these questions answered about our own service, ask us. We will answer them in writing.
Sources
- 45 CFR Part 164, Subpart C: HIPAA Security Rule, Electronic Code of Federal Regulations.
- Regulation (EU) 2016/679 (GDPR), official text.
- ITU-T Recommendation T.38: real-time Group 3 facsimile over IP networks.