OpenText Cloud Fax - OpenText TeamSite Authoring Services Integration and Automation

Common Integration Use Cases Between OpenText Cloud Fax and OpenText TeamSite Authoring Services

• Publish fax submission instructions and regulated forms on public or partner web pages

  Direction: OpenText TeamSite Authoring Services ? OpenText Cloud Fax

  Marketing or operations teams can use TeamSite to publish downloadable forms, fax cover sheets, and submission instructions for customers, patients, or partners. Those documents can include a dedicated Cloud Fax number or fax routing details for specific departments such as claims, admissions, legal intake, or government services. This reduces call center volume and ensures users send documents to the correct fax destination.

• Route web-generated requests into fax workflows for regulated document exchange

  Direction: OpenText TeamSite Authoring Services ? OpenText Cloud Fax

  When users submit requests through TeamSite-hosted web forms, the captured data can trigger a fax transmission to an external party that still requires faxed documentation. Examples include sending signed consent forms, application packets, or supporting documents to insurers, clinics, or public agencies. This helps organizations maintain digital intake while meeting fax-based compliance requirements downstream.

• Expose fax status and delivery confirmations in customer or partner portals

  Direction: OpenText Cloud Fax ? OpenText TeamSite Authoring Services

  TeamSite-powered portals can display fax delivery status, confirmation numbers, or exception messages to authenticated users. For example, a provider portal can show whether a referral packet or prior authorization was successfully faxed. This improves transparency, reduces support inquiries, and gives users a self-service view of document transmission outcomes.

• Publish approved content that includes fax-based escalation paths

  Direction: Bi-directional

  TeamSite can manage approved web content that references fax as an escalation channel for urgent or regulated submissions, while Cloud Fax can receive the actual documents generated from those workflows. For instance, a legal or healthcare site can publish a policy page with instructions to fax signed documents, and the same page can link to a form that triggers fax delivery. This keeps customer-facing content aligned with operational fax processes.

• Support document intake from website to fax archive for compliance retention

  Direction: OpenText TeamSite Authoring Services ? OpenText Cloud Fax

  Documents uploaded through TeamSite forms can be sent via Cloud Fax and then archived in a compliance repository or ECM system. This is useful for industries that need a web front end but must preserve faxed records as part of the official business record. It streamlines intake while maintaining auditability and retention controls.

• Enable content teams to manage fax-related communications without IT dependency

  Direction: OpenText TeamSite Authoring Services ? OpenText Cloud Fax

  Digital teams can update web pages, landing pages, and content blocks in TeamSite to reflect current fax numbers, department-specific routing, service hours, and submission requirements. If Cloud Fax routing changes, the updated information can be published quickly across the website and partner portals. This reduces errors caused by outdated fax instructions and lowers operational risk.

• Trigger internal review and approval workflows for faxed documents referenced on the website

  Direction: Bi-directional

  TeamSite can manage approval workflows for content that references fax submission, while Cloud Fax handles the transmission of the underlying documents to internal or external recipients. For example, a marketing or compliance team can approve a web page that instructs users to fax signed forms, and the submitted forms can be faxed to the appropriate business unit for processing. This creates a controlled process for regulated communications and reduces manual handling.