Enterprise Cloud Fax: What It Is and What to Require From a Provider

What is enterprise cloud fax?

Enterprise cloud fax is a cloud fax service built for organizations with many users, teams, and fax numbers. Faxes are sent and received over the internet and managed from one admin console, so there is no fax server to maintain and no phone line to keep in service.

What makes it "enterprise" is everything around the fax itself:

• Central control. Admins manage members, roles, and fax numbers for the whole organization, with single sign-on and enforced two-factor authentication.
• Security and compliance. Encryption, audit trails, and the agreements regulated teams need, such as a HIPAA Business Associate Agreement.
• Control over data. A choice of where fax files are stored, and how long they are kept.
• Integration. An API, webhooks, and connections to the tools teams already use, including AI assistants.

A basic online fax account covers sending and receiving. An enterprise service covers how hundreds of people, and an increasing number of automated systems, send and receive faxes safely.

Fax that works with AI assistants: MCP

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to outside tools and take actions in them. For fax, that means a member of your team can ask an assistant to send a document, find a fax that arrived this morning, or check whether a fax was delivered, and the assistant does it directly in your fax account.

Fax.Plus offers a hosted MCP server, and was the first enterprise fax provider to ship one. It works with assistants that support remote MCP connections, including Claude, ChatGPT, Perplexity, Gemini, and Copilot. Through it, an assistant can:

• Send faxes to numbers worldwide
• Search and read incoming faxes
• Check delivery status and confirmations
• Create and update contacts
• View fax numbers and manage queued faxes

The MCP server is available on paid plans starting with Basic, using OAuth sign-in, and the assistant works within the permissions granted when the user signs in. Enterprise adds Personal Access Tokens with configurable scopes, for teams that want tighter control over what an assistant can do. Developers can find setup details in the MCP documentation.

One limit to plan around: MCP is not available on accounts with Advanced Security Controls, which includes HIPAA and PHIPA accounts. For workflows that handle protected health information, use the Fax.Plus API with fax streaming and webhooks, covered below.

Real-time fax streaming

A standard fax arrives as one file, after the last page is received. For a 30-page referral packet, that means waiting for the whole transmission before anyone, or any system, can start working on it.

Fax streaming changes that. With streaming on, Fax.Plus sends a fax_page_received webhook event the moment each page is decoded, and that page is available right away through the API as a single-page file. Your intake system can read page 1 while page 2 is still coming in. The fax shows as in progress while pages arrive, and as complete when the transmission ends.

That matters wherever the first page decides what happens next:

• Healthcare: referral triage and admissions, where a cover sheet or first page routes the packet to the right team.
• Insurance: claims intake, where documents can be checked as they arrive.
• Legal and finance: filings and loan documents that start a time-sensitive process.

Streaming is an on-demand feature, enabled for the whole account by the Fax.Plus team, and it works on HIPAA accounts. The webhook event carries details about the fax and the page, not the document itself, which is downloaded through the Fax.Plus API.

Webhooks built for production

Most fax integrations depend on webhooks: your server is told when a fax is sent, received, or fails, and acts on it. In production, the hard part is not receiving an event. It is trusting it, and not losing one when your server is down. Fax.Plus webhooks are built for both.

• Clear events. Separate events for sent faxes (including failures), received faxes, and individual received pages for streaming.
• Signed requests. Every event carries a signature and a timestamp, so your server can verify it came from Fax.Plus and reject stale requests. Retries keep the same event ID, so duplicates are easy to skip.
• Filters. Point each endpoint at the event types and fax numbers it needs, so one system handles a single department's lines without seeing the rest.
• Delivery log and replay. See which events were delivered or failed, and replay the ones your server missed.
• Retries and alerts. Failed deliveries are retried automatically, and you are alerted when an endpoint keeps failing.
• No documents in the payload. Events carry metadata such as page count and status. The fax itself is fetched through the API, which keeps document content out of webhook traffic.

Webhooks and the REST API are part of Fax.Plus Enterprise, with public documentation at apidoc.fax.plus. For a side-by-side look at how fax providers handle webhooks, see our guide to the best fax API and webhooks.

Users, access, and admin control

When fax runs across many departments, the first questions from IT are about access: who can sign in, what they can see, and how to remove access when someone leaves. An enterprise service should answer all three from one place.

• Single sign-on. Members sign in with your company identity provider, so they use the same company login as for the rest of your tools.
• Two-factor authentication. On Enterprise, admins can enforce it for the whole team.
• Roles. Members see only what their role allows, and admins manage everything else.
• Audit trail. A record of account and fax activity, for internal reviews and audits.
• No per-user pricing. Fax.Plus Enterprise includes unlimited members, so adding a department, a new site, or temporary staff doesn't change the bill.

All of this is managed from one admin console in the Fax.Plus web app.

Admins also need to see what is happening on the account:

• Delivery status you can rely on. A fax is marked as delivered only when the receiving fax machine confirms it. When a fax fails, the status shows why, such as a busy line or no answer, so the sender knows whether to retry or check the number.
• Usage by member. On Enterprise, owners and admins can open an analytics dashboard with fax consumption per member and per billing cycle, and download the report as CSV.
• Fax records export. Members can export their sent and received fax records to CSV, with status, page count, date, and send duration.

Teams and fax numbers

In most organizations, a fax number belongs to a function, not a person: the referral line, the claims line, the front desk. The people behind it change, and the number should keep working regardless.

On Fax.Plus, admins assign fax numbers to members or teams, so everyone who handles a line sees its faxes in their inbox. When someone joins or leaves the team, an admin updates the assignment, and the number keeps working for everyone else on the line. Enterprise includes two fax numbers, with more available at $4.99 a month each.

If you are moving to the cloud from another provider, you can usually bring your existing fax numbers with you. Porting to Fax.Plus is free, so senders keep using the numbers they already have.

Compliance and where your data lives

For regulated teams, the fax provider becomes part of the compliance picture. Three things decide whether it fits.

• The right agreement. Healthcare teams in the US need a signed Business Associate Agreement. Fax.Plus Enterprise includes HIPAA-compliant faxing with a signed BAA and Advanced Security Controls, applied to the whole account. In Ontario, Enterprise comes with a signed PHIPA Service Provider Agreement. Our guide to HIPAA fax requirements explains what changes when HIPAA mode is on.
• Where faxes are stored. On Enterprise, admins choose where fax files and backups are stored from more than 40 locations, including the United States and Canada. For Canadian healthcare, see data sovereignty in Canada.
• How long faxes are kept. Admins set a retention period, down to zero days, after which faxes are permanently deleted. Teams can also turn off fax storage and archive faxes in their own systems through the API.

Underneath, fax files are encrypted at rest with 256-bit AES and protected in transit with TLS. Alohi, the company behind Fax.Plus, holds ISO 27001 certification and a SOC 2 Type 2 report, both issued by EY CertifyPoint. Details are on the Alohi compliance page.

Integrations and the API

Beyond MCP, streaming, and webhooks, enterprise fax should fit into the tools people already use:

• REST API. Send and receive faxes, download files or single pages, and manage members, numbers, and contacts from your own applications.
• Fax AI. Enterprise includes 1,000 AI credits a month for AI Data Extraction, which pulls names, dates, IDs, and custom fields out of each fax, and can run automatically on received faxes.
• EHR integration. Fax.Plus Enterprise integrates with EHR systems, so healthcare teams can work with faxes alongside their patient records.
• Everyday apps. Fax from Microsoft Office apps, Gmail, and Google Drive, and get fax notifications in Microsoft Teams and Slack. See all Fax.Plus integrations.
• Signatures in the same suite. Faxes that need a signature can be forwarded to Sign.Plus, Alohi's own e-signature product, to sign or request signatures under the same account.

Enterprise cloud fax checklist

Use these questions when you compare providers, and ask for the answers in writing.

1. Pricing and billing: Is enterprise pricing published, is it per user or per account, and can you pay by invoice or purchase order?
2. Access and visibility: Is single sign-on included? Can admins enforce two-factor authentication, assign roles, and see delivery status and usage per member?
3. Numbers: Can numbers be assigned to teams, and can you port your existing numbers in?
4. Compliance: Which agreements are available (such as a HIPAA BAA), and on which plan?
5. Data: Where are fax files and backups stored, can you choose the region, and can you set retention?
6. API and webhooks: Is the API documentation public? Are webhooks signed, filterable, logged, and replayable?
7. Real-time intake: Can received pages reach your systems one by one, before the whole fax arrives?
8. AI: Can AI assistants work with fax through MCP, and can data be extracted from faxes automatically?
9. Audits: Which independent certifications cover the provider?

How Fax.Plus fits

Fax.Plus Enterprise answers every question on the checklist, at a published price: $79.99 a month billed annually, or $99.99 billed monthly, with 4,000 pages a month and unlimited members. It brings single sign-on, the API and signed webhooks, fax streaming, Fax AI, HIPAA with a signed BAA, and data residency into one plan, and the hosted MCP server lets your team's AI assistants work with fax from day one.

Enterprise customers can pay by invoice, with a purchase order, or by ACH or bank transfer. For higher volumes or a migration across many numbers, talk to the Fax.Plus team.