Home | Connectors | OpenText Cloud Fax | OpenText Cloud Fax - OpenText Extended ECM - Content Server Integration and Automation

OpenText Cloud Fax - OpenText Extended ECM - Content Server Integration and Automation

Integrate OpenText Cloud Fax Document Management and OpenText Extended ECM - Content Server Document Management apps with any of the apps from the library with just a few clicks. Create automated workflows by integrating your apps.

Common Integration Use Cases Between OpenText Cloud Fax and OpenText Extended ECM - Content Server

1. Automated fax capture into governed case files

Flow: OpenText Cloud Fax ? OpenText Extended ECM - Content Server

Incoming faxes such as referrals, signed forms, claims, purchase orders, or legal notices are automatically routed into the correct matter, patient, customer, or project file in Content Server. Metadata from the fax cover sheet, sender ID, or routing rules can be used to classify and file the document in the right workspace.

Business value: Reduces manual scanning and indexing, improves retrieval speed, and ensures faxed documents are stored under enterprise retention and governance controls.

2. Outbound document delivery with archived proof of transmission

Flow: OpenText Extended ECM - Content Server ? OpenText Cloud Fax ? OpenText Extended ECM - Content Server

Documents approved in Content Server, such as contracts, notices, medical records requests, or compliance letters, can be sent through Cloud Fax directly from the repository. The transmission confirmation, delivery status, and fax audit trail are then stored back in Content Server alongside the original document.

Business value: Creates a complete compliance record, supports audit readiness, and eliminates the need to manage fax logs separately from business content.

3. Fax-based intake for regulated document workflows

Flow: OpenText Cloud Fax ? OpenText Extended ECM - Content Server ? business workflow

Organizations that still receive critical documents by fax can use Cloud Fax as the intake channel and Content Server as the controlled repository that triggers downstream workflows. Examples include prior authorizations in healthcare, court filings in legal operations, or permit applications in government.

Business value: Shortens intake-to-action time, standardizes processing, and ensures documents enter formal workflow instead of remaining in shared inboxes or local drives.

4. Secure distribution of records to external parties

Flow: OpenText Extended ECM - Content Server ? OpenText Cloud Fax

Teams can send sensitive documents stored in Content Server to external recipients who still rely on fax, such as clinics, law firms, insurers, vendors, or public agencies. The integration allows users to select a document from the repository and transmit it securely without downloading or rekeying content.

Business value: Maintains security and access control while supporting legacy communication requirements that remain common in regulated environments.

5. Centralized retention of fax correspondence for records management

Flow: OpenText Cloud Fax ? OpenText Extended ECM - Content Server

Both inbound and outbound fax communications can be automatically archived in Content Server as official records, linked to the related business object or case. Retention schedules, legal holds, and disposition rules are then applied consistently with other enterprise content.

Business value: Improves records governance, reduces compliance risk, and gives legal and records teams a single system of record for fax communications.

6. Claims, onboarding, and service case document assembly

Flow: OpenText Cloud Fax ? OpenText Extended ECM - Content Server ? case management teams

When customers, patients, or citizens submit signed forms by fax, the documents are captured into Content Server and attached to the relevant case file. Case workers can then review, annotate, route for approval, or combine the faxed document with other supporting records.

Business value: Speeds case completion, reduces missing-document follow-up, and gives service teams a complete view of the case history.

7. Exception handling for faxed approvals and signatures

Flow: OpenText Extended ECM - Content Server ? OpenText Cloud Fax ? OpenText Extended ECM - Content Server

For processes that require a wet signature or faxed approval, Content Server can generate the document package, send it by fax, and then capture the signed return fax into the same workspace. This is useful for procurement approvals, consent forms, HR documents, and vendor agreements.

Business value: Supports end-to-end process completion without manual tracking, while preserving the signed artifact and its associated workflow history.

8. Enterprise fax audit and operational reporting

Flow: OpenText Cloud Fax ? OpenText Extended ECM - Content Server

Fax transmission reports, delivery confirmations, failed-send notifications, and usage logs can be stored in Content Server for reporting and audit purposes. Business and compliance teams can correlate fax activity with related documents, cases, or transactions.

Business value: Improves visibility into fax-dependent processes, supports operational review, and helps identify bottlenecks or failed communications that could affect service delivery.

How to integrate and automate OpenText Cloud Fax with OpenText Extended ECM - Content Server using OneTeg?