Home | Connectors | OpenText Cloud Fax | OpenText Cloud Fax - OpenText Content Metadata Service Integration and Automation
Data flow: OpenText Cloud Fax ? OpenText Content Metadata Service
Incoming faxes such as claims, purchase orders, signed agreements, or patient referrals are automatically ingested into OpenText Core Content and assigned standardized metadata through the Content Metadata Service. This ensures each document is classified consistently by document type, department, case ID, customer ID, or retention category.
Business value: Reduces manual indexing, improves search accuracy, and supports downstream workflow automation for records management, case handling, and compliance.
Data flow: OpenText Content Metadata Service ? OpenText Cloud Fax
Business applications or content workflows can use standardized metadata to determine when a document must be faxed, who the recipient is, and which template or routing rules apply. For example, a legal team can send a signed notice or a healthcare provider can transmit a referral packet directly from a content workflow, with metadata controlling delivery instructions and audit attributes.
Business value: Speeds up regulated communications, reduces errors in recipient selection, and ensures fax activity is tied to governed content records.
Data flow: OpenText Cloud Fax ? OpenText Content Metadata Service
Fax transmissions and receipts can be stored with metadata such as sender, recipient, timestamp, document category, legal hold status, and retention policy. The metadata service enforces consistent classification across all fax-related records, making it easier to apply retention schedules and support audits or eDiscovery requests.
Business value: Strengthens compliance posture, simplifies records governance, and provides a reliable audit trail for regulated communications.
Data flow: OpenText Cloud Fax ? OpenText Content Metadata Service ? downstream workflow systems
When a fax arrives, the document is classified using metadata rules and routed to the appropriate queue based on attributes such as department, line of business, patient account, claim number, or matter ID. For example, a faxed insurance authorization can be tagged and routed to the claims team without manual triage.
Business value: Shortens processing time, reduces misrouted documents, and improves service levels across operations teams.
Data flow: OpenText Content Metadata Service ? OpenText Cloud Fax and connected content repositories
Organizations can define a single metadata model for faxed document types, then reuse it across Core Content repositories and fax workflows. This is especially useful for enterprises that manage similar document categories across multiple business units, such as consent forms, HR documents, or government submissions.
Business value: Creates consistency across teams, reduces duplicate configuration effort, and supports scalable cloud content architecture.
Data flow: OpenText Cloud Fax ? OpenText Content Metadata Service
Faxed documents are archived with rich metadata so users can search by business context instead of only by file name or date. A user can quickly locate a fax by claim number, customer name, case status, or document subtype, which is especially valuable in high-volume service environments.
Business value: Improves information retrieval, reduces time spent searching for documents, and supports faster customer and patient response times.
Data flow: OpenText Cloud Fax ? OpenText Content Metadata Service
Failed fax attempts, delivery exceptions, or incomplete inbound documents can be captured as metadata-rich records for review and remediation. Operations teams can track exception type, retry count, business owner, and resolution status, enabling structured follow-up and reporting.
Business value: Improves operational control, accelerates issue resolution, and provides visibility into fax process performance.