OpenText Exstream - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between OpenText Exstream and OpenText Core Signature

OpenText Exstream and OpenText Core Signature complement each other well in document-heavy, regulated business processes. Exstream is strong in generating high-volume, personalized customer communications, while Core Signature adds legally binding electronic approval and signature workflows. Together, they help organizations move from document creation to final execution without printing, scanning, or manual handoffs.

1. Digitally sign customer statements, notices, and policy documents

OpenText Exstream generates personalized statements, policy updates, renewal notices, or account disclosures and sends them to OpenText Core Signature when a signature or acknowledgment is required. Core Signature routes the document to the customer for electronic signing and returns the signed copy to the business system or repository.

• Data flow: OpenText Exstream to OpenText Core Signature
• Business value: Reduces paper handling, speeds customer response times, and improves compliance for regulated communications
• Typical users: Insurance operations, banking, utilities, and customer service teams

2. Customer onboarding document packages with signature capture

During onboarding, OpenText Exstream assembles a tailored package such as welcome letters, terms and conditions, account disclosures, and consent forms. OpenText Core Signature is then used to capture signatures on the required forms before the onboarding process is completed in the core business application.

• Data flow: OpenText Exstream to OpenText Core Signature
• Business value: Shortens onboarding cycle times and reduces incomplete applications
• Typical users: Retail banking, insurance enrollment, telecom activation, and utility service setup

3. Policy renewal and consent acknowledgment workflow

For renewals that require customer acceptance, OpenText Exstream creates the renewal notice and associated consent or acceptance form. OpenText Core Signature captures the customer?s electronic signature, and the signed acknowledgment is stored for audit and regulatory review.

• Data flow: OpenText Exstream to OpenText Core Signature, then back to ECM or policy administration systems
• Business value: Improves renewal completion rates and creates a clear audit trail for compliance
• Typical users: Insurance carriers, membership organizations, and subscription-based service providers

4. Exception-based correspondence requiring internal approval before release

When Exstream generates sensitive customer correspondence such as settlement letters, fee waivers, claim decisions, or exception notices, the document can be routed to Core Signature for internal approval before it is sent to the customer. This ensures the right manager or compliance officer signs off on the final version.

• Data flow: OpenText Exstream to OpenText Core Signature
• Business value: Reduces approval delays and enforces controlled release of high-risk communications
• Typical users: Claims teams, finance operations, legal departments, and customer care

5. Signed customer correspondence archived with the original generated document

After a document is signed in OpenText Core Signature, the signed PDF and signature metadata can be returned to the content repository or case management system alongside the original Exstream-generated document. This creates a complete record of what was sent, what was signed, and when it was executed.

• Data flow: OpenText Core Signature to ECM, case management, or downstream business applications
• Business value: Supports audit readiness, legal defensibility, and easier retrieval during disputes or reviews
• Typical users: Records management, compliance, legal, and operations teams

6. Employee communications and HR acknowledgments

OpenText Exstream can generate HR letters, policy updates, benefit enrollment documents, and employment agreements. OpenText Core Signature captures employee signatures or acknowledgments for items such as handbook acceptance, remote work agreements, or benefits elections.

• Data flow: OpenText Exstream to OpenText Core Signature
• Business value: Improves HR process efficiency and ensures policy acknowledgments are documented
• Typical users: HR operations, payroll, and employee onboarding teams

7. Bi-directional workflow for document completion status and follow-up actions

OpenText Core Signature can return signature status updates to the originating system after a document is sent from OpenText Exstream. If a document is signed, rejected, or expires, the business application can trigger the next step such as account activation, case closure, or a reminder communication generated again by Exstream.

• Data flow: Bi-directional between OpenText Exstream and OpenText Core Signature
• Business value: Enables automated follow-up, reduces manual tracking, and improves process visibility
• Typical users: Operations teams, workflow owners, and customer onboarding teams

Together, OpenText Exstream and OpenText Core Signature support a seamless document lifecycle from generation to approval and final execution. This integration is especially valuable in regulated industries where communication accuracy, customer experience, and auditability must all be maintained.