Agility - OpenText Core Signature Integration and Automation

Common Integration Use Cases Between Agility and OpenText Core Signature

1. Digital Contract and Agreement Publishing with Embedded eSignature

Agility can manage the public-facing content for contract or agreement pages, such as terms, service descriptions, pricing summaries, and onboarding instructions, while OpenText Core Signature handles the legally binding signature workflow for the actual document. This is useful for customer-facing portals where users review content in Agility-powered pages and then complete signing in OpenText Core Signature.

• Data flow: Agility to OpenText Core Signature
• Business value: Faster contract execution, consistent customer experience, reduced manual handoffs
• Example: A telecom provider publishes plan details and service terms in Agility, then routes the customer to OpenText Core Signature to sign the service agreement

2. HR Policy Acknowledgement and Employee Onboarding

HR teams can use Agility to publish onboarding content, policy pages, and employee guidance, while OpenText Core Signature captures signed acknowledgements for employment contracts, confidentiality agreements, and policy acceptance forms. This creates a structured onboarding journey with content and signature steps connected in one workflow.

• Data flow: Agility to OpenText Core Signature, with signed records returned to HR systems
• Business value: Improved onboarding speed, better compliance tracking, fewer paper-based processes
• Example: New hires access onboarding content in Agility, then sign employment documents in OpenText Core Signature before their start date

3. Customer Onboarding and Account Activation

Organizations can use Agility to deliver onboarding content such as product setup guides, welcome pages, and required disclosures, while OpenText Core Signature manages the signature of account opening forms, consent documents, and service agreements. This is especially valuable in banking, insurance, telecom, and SaaS onboarding flows.

• Data flow: Agility to OpenText Core Signature, bi-directional status updates back to customer portals
• Business value: Shorter time to activation, fewer drop-offs, improved compliance and auditability
• Example: A financial services firm uses Agility for onboarding instructions and OpenText Core Signature for customer consent and account opening approvals

4. Marketing Campaign Landing Pages with Signature-Based Lead Conversion

Marketing teams can build campaign landing pages in Agility and connect them to OpenText Core Signature for high-intent actions such as event registrations, partner agreements, demo approvals, or quote acceptance. This allows a campaign page to move a prospect from interest to signed commitment without leaving the digital experience.

• Data flow: Agility to OpenText Core Signature, with completion status returned to CRM or marketing automation
• Business value: Higher conversion rates, faster lead qualification, reduced friction in campaign journeys
• Example: A software company publishes a webinar landing page in Agility and uses OpenText Core Signature to capture signed participation terms or trial agreements

5. Contract Content Management with Signature Workflow Triggering

Agility can serve as the content source for contract templates, clause libraries, and approval instructions, while OpenText Core Signature executes the signature workflow once the document is finalized. This is useful when legal, sales, and operations teams need controlled content and a standardized signing process.

• Data flow: Agility to OpenText Core Signature
• Business value: Better version control, fewer template errors, faster legal review cycles
• Example: A professional services firm maintains approved contract language in Agility and sends finalized agreements to OpenText Core Signature for client execution

6. Signed Document Confirmation Pages and Post-Signature Content Delivery

After a document is signed in OpenText Core Signature, Agility can deliver a branded confirmation page, next-step instructions, or relevant content such as onboarding resources, product setup guides, or support articles. This improves the post-signature experience and helps users complete the next business step quickly.

• Data flow: OpenText Core Signature to Agility
• Business value: Better customer experience, reduced support calls, faster downstream adoption
• Example: After signing a lease or service agreement, the user is redirected to an Agility-powered page with welcome information and setup instructions

7. Compliance and Audit Content Distribution with Signed Record Retention

Agility can publish compliance-related content such as policy updates, regulatory notices, and internal guidance, while OpenText Core Signature captures acknowledgements and signed attestations. Signed records can then be stored in ECM or compliance repositories, supporting audit readiness and governance requirements.

• Data flow: Agility to OpenText Core Signature, then to ECM or records systems
• Business value: Stronger compliance evidence, centralized policy communication, easier audit preparation
• Example: A healthcare organization publishes updated privacy policies in Agility and uses OpenText Core Signature to collect employee acknowledgements

8. Partner and Vendor Agreement Portals

Agility can power partner or supplier portals that present onboarding content, program requirements, and operational instructions, while OpenText Core Signature handles the execution of partner agreements, NDAs, and vendor onboarding forms. This creates a more streamlined external collaboration process.

• Data flow: Agility to OpenText Core Signature, with signed agreement status returned to portal or back-office systems
• Business value: Faster partner onboarding, improved process visibility, reduced administrative effort
• Example: A manufacturer uses Agility for supplier onboarding content and OpenText Core Signature for signing procurement and compliance documents