Healthcare · Managed platform (eFax Corporate)

Cloud Fax

Inbound faxes routed to the right EMR inbox, without paper or fax machines

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph resells, implements and runs eFax Corporate to replace fax machines and on-premises fax servers with cloud fax. eFax Corporate receives and sends faxes on your existing numbers, and Moraph builds the routing that delivers each inbound document to the right department queue or EMR inbox, where your staff confirm the patient and document type before it is filed. Moraph's service team watches delivery every day, maintains routing as departments change, and keeps the records your privacy officer needs.

The problem it solves

Referrals, orders, prior authorization responses, lab results and records requests still arrive by fax in most health systems, because many senders cannot send any other way. Fax machines print pages that sit in trays, fax servers age without an owner, and documents are scanned and indexed by hand before a clinician sees them. Pages go to the wrong department, numbers are misdialed, and nobody can say quickly whether a fax was received or where it went.

  • Paper faxes sit in trays where anyone passing can read them
  • Documents are scanned and indexed by hand before reaching the chart
  • Faxes are misrouted between departments with no record of where they went
  • Aging fax servers and phone lines have no clear owner

Who uses it

  • Health information management and document intake teams
  • Referral, scheduling and prior authorization staff who work faxed documents daily
  • Hospital and clinic IT teams retiring fax machines and on-premises fax servers
  • Privacy officers concerned about PHI on printed and misrouted faxes
  • Ambulatory groups and post-acute providers that exchange records by fax

Requirements it supports

HIPAA Privacy Rule (45 CFR Part 164, Subpart E)HIPAA Security Rule (45 CFR Part 164, Subpart C), including transmission security at 45 CFR 164.312(e)HIPAA Breach Notification Rule (45 CFR 164.400 to 164.414)Confidentiality of Substance Use Disorder Patient Records (42 CFR Part 2)ONC information blocking rules under the 21st Century Cures Act (45 CFR Part 171)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Consensus Cloud Solutions provides and operates eFax Corporate, Moraph configures it and runs the routing into your EMR, and your organization decides how documents are handled and files them to the chart.

AreaMoraphConsensus Cloud Solutions (eFax Corporate)Your organization
LicensingResells eFax Corporate and keeps numbers and plans aligned with your useSets license terms and product availabilityAgrees the numbers and users to license and pays under the order
Platform availabilityMonitors delivery, raises incidents with the provider and keeps you informedOperates the fax platform under its own service commitmentsTells Moraph about clinical impact
NumbersCoordinates porting and new numbersHosts the numbers and carries the callsAuthorizes ports with your carrier
RoutingBuilds and maintains routing to queues and EMR inboxesDelivers received faxes to Moraph's routingApproves which number goes where
EMR interfaceBuilds and supports the delivery interfaceProvides the platform's delivery methodsConfigures the EMR side and maintains document types
Indexing and filingNot applicableNot applicableConfirms the patient and document type and files to the chart
MonitoringRuns the daily delivery check and watches the fallback queueProvides delivery logsWorks documents in department queues
RetentionApplies the approved retention settingsRetains and deletes copies under the settings and its termsOwns the retention policy and the legal record
IncidentsLeads incident handling for the service and reports cause and fixResolves platform incidents and provides root cause where availableDecides on any breach notification
Regulatory obligationsProvides evidence of routing, delivery and changes under its business associate agreementMeets its obligations under its own business associate agreementRemains responsible for HIPAA and 42 CFR Part 2 compliance

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of eFax Corporate itself, which belongs to its vendor.

  1. Step 1

    Cutover tracker

    During onboarding, each department moves from inventory to live cloud fax, with porting and routing tests visible.

    DepartmentNumbersRouting approvedPortRouting testStatus
    Example Medical Center, Referrals3YesCompletePassedLive
    Example Medical Center, HIM release of information2YesCompletePassedLive
    Example Medical Center, Cardiology1YesScheduledPassedWaiting on port
    Example Clinic, Primary Care2YesRejected by carrierNot startedPort resubmitted
    Example Medical Center, Behavioral Health1Part 2 review pendingNot startedNot startedOn hold
    During onboarding, each department moves from inventory to live cloud fax, with porting and routing tests visible.

  2. Step 2

    Daily delivery check

    Each morning Moraph compares faxes received with documents delivered and works anything that did not arrive.

    Fax numberDestinationReceivedDeliveredExceptionsAction
    Number ending 0101Referrals EMR inbox1481480None
    Number ending 0102Prior auth EMR inbox96951Interface retry succeeded
    Number ending 0215Cardiology EMR inbox41410None
    Number ending 0330Release of information queue22202Sent to fallback queue
    Each morning Moraph compares faxes received with documents delivered and works anything that did not arrive.

  3. Step 3

    A fallback queue item

    A document that could not be delivered is held in a monitored queue with the reason, so it can be sent on.

    Fallback item FB-0612 · Received on number ending 0330

    Received
    Fictional sample time
    Pages
    6
    Intended destination
    Release of information queue
    Reason
    Destination queue unavailable during maintenance
    Age
    40 minutes
    Assigned to
    HIM lead

    Next steps

    • Re-send to the intended destination once the queue is available
    • Or forward to another department if the sender used the wrong number
    • Record the outcome on the item
    A document that could not be delivered is held in a monitored queue with the reason, so it can be sent on.

  4. Step 4

    A routing change request

    A new clinic number is added only after the HIM lead and client IT approve where its documents should go.

    Change CR-3301 · New number for Example Clinic, Orthopedics

    Requested by
    Clinic manager
    Number
    New number to be issued
    Destination
    Orthopedics referrals EMR inbox
    Fallback
    Central fallback queue
    Part 2 records expected
    No
    Status
    Approved, scheduled

    Approvals

    • HIM lead: approved
    • Client IT and interface team: approved
    • Privacy officer: not required, standard routing
    A new clinic number is added only after the HIM lead and client IT approve where its documents should go.

  5. Step 5

    A misdirected fax

    When a fax arrives at the wrong department or is sent to a wrong number, each step is recorded for the privacy officer.

    Misdirected fax MD-0088 · Inbound to Cardiology, intended for Oncology

    1. Intake staff notice document is for another departmentDepartment intake staff
    2. Document returned to the fallback queue with a noteDepartment intake staff
    3. Document forwarded to Oncology intakeHIM lead
    4. Sender's fax number checked; sender used the wrong numberMoraph service team
    5. Record passed for privacy reviewHIM lead
    6. Assessed: internal misroute, no disclosure outside the organizationPrivacy officer
    When a fax arrives at the wrong department or is sent to a wrong number, each step is recorded for the privacy officer.

  6. Step 6

    Monthly service review

    Each month, Moraph, HIM and your IT team review volumes, exceptions and changes, using fictional figures here.

    MeasureThis monthLast monthNote
    Inbound documents18,42017,960Two clinics added
    Delivery exceptions3144Interface retry tuned
    Fallback items over age limit39Weekend coverage gap
    Outbound failures after retries212198Mostly busy or wrong numbers
    Misdirected fax reports46All internal
    Fax machines retired1712On plan
    Each month, Moraph, HIM and your IT team review volumes, exceptions and changes, using fictional figures here.

Workflows

The principal workflows

  1. Receive

    eFax Corporate receives faxes on your existing numbers, ported from your carrier, and on new numbers as needed. No pages are printed.

    • Your fax numbers are ported to eFax Corporate or new numbers issued
    • Senders keep dialing the same numbers
    • eFax Corporate receives each fax as a digital document
    • The document is passed to Moraph's routing by number
    • Delivery failures are logged for the service team

  2. Route

    Routing rules agreed with each department send every fax number to the right queue, mailbox or EMR inbox, so documents arrive where the people who act on them work.

    • Each fax number is mapped to a department queue or EMR inbox
    • Documents are delivered through the EMR's document import interface or to a secure queue
    • Documents that cannot be delivered go to a fallback queue for review
    • Routing changes are made through approved change requests
    • Moraph checks daily that routed documents arrived

  3. Index and file

    Staff in the receiving department open each document, confirm the patient and document type, and file it to the chart or pass it on. Nothing is filed to a chart without a person confirming the match.

    • The document appears in the department's EMR inbox or queue
    • Staff search for and confirm the patient
    • Staff choose the document type and any routing to a clinician
    • The document is filed to the chart or forwarded to another department
    • Misdirected faxes are returned to the fallback queue or the sender is contacted

  4. Send

    Staff send faxes from the EMR or a secure web portal through eFax Corporate, and the delivery confirmation is kept.

    • Staff send from the EMR's fax function or the eFax Corporate portal
    • Cover sheet with your confidentiality notice is applied
    • eFax Corporate attempts delivery and retries busy lines
    • Delivery confirmation or failure is returned to the sender
    • Failed faxes are visible for staff to correct and resend

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

HIM or intake lead

HIM director, document management supervisor, patient access manager

Owns how faxed documents reach the chart: which department receives what, how documents are indexed, and what happens to misrouted faxes.

Sees

  • The routing table for their areas
  • Fallback queue items and delivery exceptions
  • Volumes by number and department

Does

  • Approves routing changes for their areas
  • Sets indexing procedures for intake staff
  • Works or assigns fallback queue items
  • Raises intake problems at the monthly service review

Cannot

  • Change retention or access settings without the privacy officer
  • Make changes directly in eFax Corporate administration
Approvals
Approves routing changes for their areas.
Notified about
Fallback queue items waiting, delivery failures for their numbers, and routing changes applied.

Department intake staff

Referral coordinator, HIM specialist, prior authorization specialist, front desk staff

Turns each incoming fax into a filed document or a task for the right person.

Sees

  • Faxes delivered to their department's queue or EMR inbox
  • Send confirmations for faxes they sent

Does

  • Opens faxes and confirms the patient
  • Chooses the document type and files to the chart
  • Forwards faxes to another department
  • Sends outbound faxes from the EMR or portal
  • Returns misdirected faxes to the fallback queue

Cannot

  • See other departments' queues
  • Change routing or fax numbers
  • Delete faxes from the service's retained copies
Approvals
None; their work follows your indexing procedures.
Notified about
New faxes in their queue and failed outbound faxes they sent.

Client IT and interface team

Integration engineer, EMR interface analyst, telecom manager

Owns the EMR interfaces, network and telephony that cloud fax depends on, and is Moraph's technical counterpart.

Sees

  • The full routing table and interface status
  • The configuration baseline and change history
  • Service reports and open incidents

Does

  • Approves technical change requests
  • Maintains the EMR's document import interface settings
  • Coordinates number porting with your carrier
  • Retires fax machines and fax servers after cutover
  • Joins the monthly service review

Cannot

  • Change retention or access settings without the privacy officer
  • Edit the change record after the fact
Approvals
Approves technical changes and interface changes.
Notified about
Interface failures, incidents, vendor notices that affect you, and change requests waiting for approval.

Privacy officer

HIPAA privacy officer, compliance officer

Sets retention and access rules for faxed PHI and handles misdirected faxes.

Sees

  • Retention and access settings and their history
  • Misdirected fax reports
  • Administrator access, including Moraph staff

Does

  • Approves retention settings and cover sheet notices
  • Reviews misdirected faxes for breach assessment
  • Approves who can access retained fax copies
  • Reviews administrator access periodically

Cannot

  • Edit or delete delivery and change records
  • Make configuration changes directly in eFax Corporate
Approvals
Approves retention, access and cover sheet changes.
Notified about
Misdirected faxes reported, retention changes requested, and access reviews due.

Moraph service team

Moraph integration engineers and service managers

Runs the service on your behalf: eFax Corporate configuration, routing, monitoring, changes and incidents.

Sees

  • eFax Corporate configuration, numbers and delivery logs
  • Routing rules and interface status
  • Change requests and their approvals

Does

  • Maintains numbers, users and routing to the approved baseline
  • Runs the daily delivery check and investigates gaps
  • Monitors the fallback queue and alerts the right department
  • Coordinates number ports and new numbers
  • Raises and follows incidents with the vendor
  • Prepares the monthly service review

Cannot

  • Change routing or retention without an approved change request
  • Open fax content except to investigate a delivery problem you have logged
  • Use privileged access outside approved, time-bound work
Approvals
Every configuration change is made against a change request approved by the owner you name.
Notified about
Delivery failures, interface errors, fallback queue items over the age you set, and vendor notices.

Auditor (read-only)

Internal auditor, compliance analyst, external assessor under temporary access

Reviews evidence that faxed PHI is routed, retained and accessed as policy requires.

Sees

  • The routing table and change history
  • Delivery and exception reports for the period in scope
  • Administrator access reviews

Does

  • Reads and exports evidence within their scope, with each export logged
  • Requests further evidence through the privacy officer

Cannot

  • See fax content
  • Change, approve or delete anything
  • Keep access after the agreed end date
Approvals
Access is approved by the privacy officer with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionHIM leadIntake staffClient ITPrivacyMoraph teamAuditor
Work faxes in a department queueFullOwn work onlyNo accessNo accessNo accessNo access
File a fax to the chartFullOwn work onlyNo accessNo accessNo accessNo access
Send faxesFullOwn work onlyNo accessNo accessNo accessNo access
Work the fallback queueFullNo accessView onlyView onlyFullNo access
Change routing rulesApprovesNo accessApprovesNo accessFullView only
Add, port or remove fax numbersApprovesNo accessApprovesNo accessFullNo access
Change retention settingsView onlyNo accessView onlyApprovesFullView only
Change EMR interface settingsNo accessNo accessApprovesNo accessFullNo access
View delivery logsView onlyNo accessView onlyView onlyFullView only
View the configuration baselineView onlyNo accessView onlyView onlyFullView only
Manage administrator accessNo accessNo accessApprovesApprovesFullNo access
View service reportsView onlyNo accessView onlyView onlyFullView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph changes routing, numbers and retention only against a change request approved by the owner you name, and each change is recorded with the request it came from.
  • Moraph's staff open fax content only to investigate a delivery problem you have logged, and each access is recorded.
  • Intake staff see only their own department's queue or inbox. Departments and access are agreed with you during onboarding and can follow your identity provider's groups.
  • Auditors receive temporary read-only access to routing, delivery and change evidence, not fax content, with a defined scope and an end date.

Features

What it does

Number porting

Your existing fax numbers move to eFax Corporate so senders do not need to change anything; Moraph coordinates the port with your carrier.

Routing by number

Each fax number is mapped to a department queue, shared mailbox or EMR inbox, and the routing table is documented and maintained by Moraph.

EMR inbox delivery

Inbound documents are delivered into your EMR's document intake through its supported import interface, built and maintained by Moraph.

Fallback queue

Documents that cannot be delivered to their destination go to a monitored queue rather than being lost or printed.

Person-confirmed filing

Staff confirm the patient and document type before a fax is filed to a chart; routing never files to a chart on its own.

Sending from the EMR

Outbound faxes are sent from the EMR's fax function or the eFax Corporate web portal, with delivery confirmations kept.

Encrypted transmission and storage

eFax Corporate encrypts documents in transit and at rest under its terms, and Moraph's routing uses encrypted connections end to end.

Daily delivery check

Moraph compares faxes received with documents delivered each day and investigates any that did not arrive.

Routing change requests

New departments, moved clinics and new numbers are added through change requests approved by the owner you name.

Retention settings

How long eFax Corporate keeps copies of faxes is set to your retention policy, with the chart as the record of care.

Fax server retirement

Moraph plans the move off fax machines and on-premises fax servers department by department, with routing tested before each cutover.

Service reporting

A monthly service review covers volumes, delivery exceptions, fallback queue items, changes, incidents and open issues.

Integrations

How it connects to your systems

Connects toHowWhat flows
EMR document intakeInbound faxes are delivered into your EMR's document intake or inbox through its supported import interface, such as HL7 document messages or the vendor's document API.Out: fax documents with number, time and routing metadata.
EMR outbound faxThe EMR's fax function sends through eFax Corporate, so letters and records leave from the chart.In: outbound documents and destination numbers. Out: delivery status.
Integration engineWhere you route interfaces through an integration engine, including Moraph's Integration Engine service, fax delivery runs through it.In and out: document messages and acknowledgments.
Carrier and telephonyMoraph coordinates porting your existing fax numbers from your carrier to eFax Corporate.In: number ownership and port details.
Email and secure queuesDepartments without an EMR inbox receive faxes in a secure queue or shared mailbox, as your privacy officer approves.Out: fax documents to the approved destination.
Single sign-onStaff using the eFax Corporate portal sign in through your identity provider where the platform supports it.In: user identity and group membership.
IT service managementFax tickets flow between your service desk and Moraph's service team, including Moraph's IT Service Management service where you use it.In and out: tickets, status and resolution.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Your staff and Moraph's staff sign in through identity providers with multi-factor authentication where the platform supports it, and access is removed when people leave.

Role-based access

Intake staff see their department's faxes, administrators manage configuration, and auditors see evidence rather than fax content.

Logged content access

Every opening of fax content by Moraph staff is recorded with the person, time and the ticket it served.

Controlled privileged access

Moraph staff use administrative access only for approved work, with keys and credentials they cannot use without explicit, time-bound authorization.

Independent audits

Moraph's operations are audited under SOC 2 Type II and ISO/IEC 27001. eFax Corporate's own assurance documentation is available from its provider under its terms.

Business associate agreements

Moraph signs a business associate agreement for the service, and the provider of eFax Corporate signs its own under its terms. Moraph's routing runs in the United States region.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Daily delivery check

For moraph service team and HIM lead

Faxes received compared with documents delivered to each destination, with any that did not arrive.

Break down by
Fax number, Destination, Delivery status
Delivered as
Daily list; live view
Used for
Making sure no inbound fax is lost between eFax Corporate and the EMR.

Fallback queue

For hIM lead and Moraph service team

Documents that could not be delivered to their destination, with their age and reason.

Break down by
Reason, Fax number, Age
Delivered as
Live view; alerts by age
Used for
Getting undeliverable documents to the right department quickly.

Outbound failures

For department leads

Outbound faxes that failed after retries, with the sender, destination and reason.

Break down by
Department, Reason, Period
Delivered as
Daily email; live view
Used for
Making sure documents that were meant to go out did go out.

Volume by number and department

For hIM lead and client IT

Inbound and outbound pages and documents by number and department over time.

Break down by
Fax number, Department, Direction, Period
Delivered as
Monthly; CSV export
Used for
Planning staffing, licensing and which senders to move off fax.

Security and compliance

Misdirected faxes

For privacy officer

Faxes reported as misdirected, inbound or outbound, with the actions taken.

Break down by
Direction, Department, Outcome, Period
Delivered as
Live view; PDF export
Used for
Supporting breach assessments and fixing routing causes.

Routing table and changes

For hIM lead, privacy officer, auditors

Every fax number with its destination, and every change with the request, approver and date.

Break down by
Fax number, Department, Change date, Approver
Delivered as
Quarterly review pack; PDF export
Used for
Evidencing that faxed PHI goes only where it was agreed to go.

Administrator and content access

For privacy officer

Everyone with administrative access, including Moraph staff, and each time Moraph staff opened fax content, with the ticket.

Break down by
Organization, Role, Period
Delivered as
At each access review; PDF export
Used for
Certifying access and showing content was opened only for logged reasons.

Service

Monthly service review

For client IT, HIM lead and service owners

Volumes, delivery exceptions, fallback items, outbound failures, changes, incidents and open issues for the month.

Break down by
Month, Site, Category
Delivered as
PDF; review meeting
Used for
Reviewing the service with Moraph and agreeing priorities.

Change request log

For hIM lead, client IT, privacy officer

Every change request with its requester, approver, status and the date it was applied.

Break down by
Status, Requester, Change type, Period
Delivered as
Live view; CSV export
Used for
Tracking what is changing in routing and who agreed it.

Cutover tracker

For client IT and HIM lead

Departments and numbers moving from fax machines or servers to cloud fax, with porting, routing test and cutover status.

Break down by
Department, Site, Status
Delivered as
Live view during migration
Used for
Following the retirement of fax machines and servers.

Exports, access and evidence

  • Reports come from eFax Corporate's delivery logs and Moraph's routing and service records. Moraph assembles the daily check and monthly review.
  • Every report can be exported to CSV, and review and evidence reports to PDF.
  • Reports show numbers, times, destinations and status, not fax content. Content stays in the EMR and in eFax Corporate under your retention settings.
  • Department leads see their own numbers; the HIM lead, client IT and privacy officer see the whole service.
  • Evidence reports can be run for a past period for audits, and producing them is recorded.

Deployment

Where and how it runs

eFax Corporate cloud, managed by Moraph

eFax Corporate runs in its provider's cloud; Moraph configures it and runs the routing to your EMR under a managed service agreement.

Moraph-managed with your existing account

If you already use eFax Corporate, Moraph can take over configuration, routing and operations, subject to its provider's terms.

Alongside other Moraph services

Run with Moraph's Integration Engine or Referral & Prior Auth Gateway so faxed documents feed the same intake as electronic ones.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Fax inventory

We list your fax numbers, machines, servers, the departments behind each and what kinds of documents arrive, and agree what moves first.

Routing design

HIM, department leads and the privacy officer agree where each number's documents should go and how undeliverable documents are handled.

Interface build

Moraph builds the delivery interface to your EMR's document intake with your interface team, and tests it with sample documents in your test environment.

Number porting

Existing numbers are ported from your carrier in batches, with new temporary numbers where a department needs to start before its port completes.

Department cutover

Departments move one at a time, with routing tested and intake staff shown their queue before the fax machine is switched off.

Handover to service

The daily delivery check, fallback queue monitoring, change requests and the monthly service review begin, and your contacts are confirmed.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not Consensus Cloud Solutions, the provider of eFax Corporate. The platform belongs to its provider, and the provider's own service commitments, roadmap, maintenance and outages apply to it.
  • Licenses and numbers are subject to the provider's terms, and some numbers may not be portable from your carrier.
  • Moraph does not index or file documents. Your staff confirm the patient and document type before anything is filed to a chart.
  • Delivery into the EMR depends on the import methods your EMR supports and on your interface team's configuration.
  • Fax remains an unstructured, page-image format. Cloud fax removes paper and manual routing; it does not turn faxes into structured data.
  • Faxes sent to a wrong number by the sender, or by your staff, still reach that number. Moraph can report misdirected faxes but cannot recall them.
  • Your organization remains responsible for HIPAA and 42 CFR Part 2 compliance, its retention policy and breach notification decisions.
  • Analog lines for devices that are not fax machines, such as alarms or elevators, are not part of the service.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. List your fax numbers and machines and ask which can be ported and which departments move first
  2. Pick one department and walk through a faxed referral from receipt to filing in the chart
  3. Review how undeliverable documents reach the fallback queue and who works it
  4. Check with your interface team how documents will arrive in your EMR's intake
  5. Ask your privacy officer to review the retention settings and misdirected fax procedure
  6. Confirm who at your organization approves routing changes

Questions

Frequently asked questions

Do senders need to change anything?

Usually not. Your existing numbers are ported to eFax Corporate where your carrier allows it, and senders keep dialing the same numbers.

Does a fax go straight into the patient's chart?

No. It arrives in the right department's EMR inbox or queue, and your staff confirm the patient and document type before filing it.

Is eFax Corporate suitable for PHI?

Its provider offers a business associate agreement and encrypts documents under its terms, and Moraph signs its own business associate agreement for the service. Your organization remains responsible for how PHI is handled.

Can Moraph see our faxes?

Moraph's staff open fax content only to investigate a delivery problem you have logged, and each access is recorded. Day to day, the service team works with numbers, times and delivery status.

What happens when eFax Corporate has an outage?

Moraph raises and follows the incident with the provider, keeps you informed and records the effect on delivery. The provider's own service commitments govern the platform itself.

How is it priced?

eFax Corporate is priced under its provider's terms, usually by numbers and pages, and Moraph's managed service is priced separately. See Working with Moraph for what drives a quotation.

Next steps

Evaluate Cloud Fax

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Cloud Fax guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Cloud Fax support guide.

Related products