Consonance - OpenText Cloud Fax Integration and Automation

Common Integration Use Cases Between Consonance and OpenText Cloud Fax

• Rights and permissions document intake from agents, authors, and licensors
  

  Data flow: OpenText Cloud Fax to Consonance

  Publishing teams often receive signed rights agreements, permissions letters, and license confirmations by fax from agencies, estates, and legal representatives. OpenText Cloud Fax can capture these inbound documents and route them into Consonance as attachments to the correct title, author, or rights record. This reduces manual scanning, improves auditability, and ensures rights teams can quickly verify usage permissions before production begins.

• Editorial approval packets for external contributors
  

  Data flow: Consonance to OpenText Cloud Fax

  When publishers need to send editorial approval forms, contributor agreements, or release notices to external parties who still rely on fax, Consonance can trigger outbound fax delivery through OpenText Cloud Fax. This is useful for high-friction workflows involving freelance editors, illustrators, estates, or international partners. It shortens turnaround time and keeps the approval trail linked to the manuscript or title workflow.

• Contract and royalty correspondence archiving
  

  Data flow: OpenText Cloud Fax to Consonance, and Consonance to OpenText Cloud Fax

  Royalty and contracts teams frequently exchange signed amendments, payment dispute letters, and contractual notices by fax. Integrating the two systems allows faxed correspondence to be automatically stored against the relevant contract, author, or title record in Consonance, while outbound notices can be sent directly from the publishing workflow. This creates a single source of truth for contractual communications and supports compliance reviews and dispute resolution.

• Production sign-off and final proof distribution to external approvers
  

  Data flow: Consonance to OpenText Cloud Fax

  For titles requiring formal sign-off from legal, rights holders, or institutional stakeholders, Consonance can send final proof PDFs or approval forms via fax when email is not acceptable or not reliable enough. OpenText Cloud Fax provides secure delivery and transmission confirmation, while Consonance retains the status update and proof of approval. This is especially valuable for time-sensitive production schedules where missing sign-off can delay print release.

• Inbound fax capture for manuscript submissions and proposal materials
  

  Data flow: OpenText Cloud Fax to Consonance

  Some publishers still receive unsolicited submissions, proposal forms, or supporting documents by fax, particularly from agents, academic institutions, or government-related authors. OpenText Cloud Fax can ingest these inbound faxes and create or update submission records in Consonance, attaching the documents to the appropriate acquisition workflow. This reduces administrative handling and helps acquisitions teams triage submissions faster.

• Compliance-driven document retention for regulated or sensitive publishing content
  

  Data flow: Bi-directional

  Publishers handling sensitive content such as legal references, medical titles, educational materials, or government publications may need a defensible record of document exchange. By integrating fax transmission logs, delivery confirmations, and inbound fax images into Consonance, teams can maintain a complete compliance archive tied to each title or project. This supports internal audits, legal discovery, and policy enforcement without relying on separate manual filing processes.

• External review and corrections workflow for distributed editorial teams
  

  Data flow: Consonance to OpenText Cloud Fax, with status updates back to Consonance

  In some publishing operations, external reviewers or regional partners may require faxed copies of page proofs, correction sheets, or approval forms. Consonance can initiate the fax from the relevant workflow stage, and OpenText Cloud Fax can return delivery status to Consonance so editorial coordinators know when review materials have been received. This improves coordination across distributed teams and reduces delays caused by uncertain document delivery.