OpenText Cloud Fax - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between OpenText Cloud Fax and OpenText Core Signature

1. Fax-to-Signature Workflow for Regulated Document Approvals

Data flow: OpenText Cloud Fax ? OpenText Core Signature

Organizations in healthcare, insurance, and government often receive paper-based forms by fax that still require formal approval or consent. With this integration, inbound faxes are automatically captured, classified, and routed into OpenText Core Signature for electronic signing. This reduces manual scanning, printing, and rekeying while preserving a compliant audit trail.

• Inbound fax is received in OpenText Cloud Fax
• Document is routed to a signing workflow in OpenText Core Signature
• Signed document is returned to the ECM or business system for storage and follow-up

Business value: Faster turnaround on approvals, lower administrative effort, and improved compliance for regulated document handling.

2. Signature-Triggered Fax Distribution for External Parties

Data flow: OpenText Core Signature ? OpenText Cloud Fax

After a document is signed electronically, some counterparties still require a faxed copy for legal, operational, or legacy process reasons. Once the signature workflow is complete in OpenText Core Signature, the final executed document can be sent automatically through OpenText Cloud Fax to external recipients such as clinics, law offices, agencies, or vendors.

• Document is signed in OpenText Core Signature
• Final PDF is generated with signature evidence
• OpenText Cloud Fax sends the executed document to fax-only recipients

Business value: Supports hybrid digital and legacy communication channels without manual reprocessing.

3. Patient or Client Consent Capture Across Fax and E-Signature Channels

Data flow: Bi-directional

In healthcare, legal, and public sector workflows, consent forms may arrive by fax from one group of users and be completed electronically by another. OpenText Cloud Fax can receive initial consent requests or supporting documents, while OpenText Core Signature can be used to obtain the final signature from the patient, client, or authorized representative. This creates a unified consent process across channels.

• Faxed intake or consent packet is received and stored
• Missing signatures are requested through OpenText Core Signature
• Completed packet is archived with full audit history

Business value: Improves completion rates for consent and intake processes while accommodating user preference and accessibility needs.

4. Contract Exception Handling for Fax-Based Redlines and Signature Completion

Data flow: OpenText Cloud Fax ? OpenText Core Signature

Some suppliers, partners, or customers still return contract changes by fax. This integration allows faxed redlines, approvals, or exception pages to be ingested and attached to the contract record, then routed into OpenText Core Signature for final execution. Legal and procurement teams can manage the full contract lifecycle without losing visibility into fax-based changes.

• Counterparty sends redlines or approval notes by fax
• Fax is linked to the contract record in ECM or CLM
• Final contract is sent for electronic signature in OpenText Core Signature

Business value: Reduces contract delays and keeps legacy counterparties in the process without sacrificing digital control.

5. HR Onboarding for Employees and Third-Party Verifications

Data flow: OpenText Core Signature ? OpenText Cloud Fax

HR teams can use OpenText Core Signature to collect signed employment documents, policy acknowledgements, and benefit forms. If third-party verification is required, such as sending signed medical, background check, or benefits-related documents to external providers that still rely on fax, OpenText Cloud Fax can distribute the completed records automatically.

• New hire signs onboarding documents in OpenText Core Signature
• Completed forms are stored in the HR system or ECM
• Required documents are faxed to external agencies or providers

Business value: Speeds onboarding, reduces HR admin work, and supports external compliance requirements.

6. Claims and Case File Processing with Signed Authorizations

Data flow: OpenText Cloud Fax ? OpenText Core Signature ? OpenText Cloud Fax

In insurance and public services, claims often begin with faxed supporting documents and require signed authorization before processing can continue. OpenText Cloud Fax receives the initial claim packet, OpenText Core Signature captures the authorization or release signature, and OpenText Cloud Fax can then send the signed authorization to external adjusters, providers, or agencies that still require fax delivery.

• Claim documents arrive by fax
• Authorization form is sent for e-signature
• Signed authorization is faxed to the external party if needed

Business value: Shortens claim cycle times and improves coordination between digital and fax-dependent stakeholders.

7. ECM-Centered Document Routing with Mixed Channel Completion

Data flow: Bi-directional

When both platforms are integrated with an ECM, documents can move seamlessly between fax intake, signature workflows, and archival storage. A document may enter through OpenText Cloud Fax, be routed to OpenText Core Signature for approval, and then be returned to the ECM as a completed record. The same process can work in reverse for outbound documents that require fax delivery after signing.

• ECM stores the master document and metadata
• Faxed inbound items are indexed and linked to the record
• Signature workflow is launched from the ECM
• Final signed version is archived automatically

Business value: Creates a controlled, auditable document lifecycle and reduces manual handoffs across departments.