Agility - OpenText Extended ECM - Business Workspaces Integration and Automation

Common Integration Use Cases Between Agility CMS and OpenText Extended ECM - Business Workspaces

1. Customer-facing portal content linked to customer workspaces

Flow: Agility CMS – OpenText Extended ECM - Business Workspaces

Marketing teams manage customer portal pages, FAQs, onboarding guides, and service updates in Agility CMS, while OpenText Extended ECM stores the supporting customer-specific documents, contracts, and case files in a workspace tied to each customer record. The portal can surface approved content from Agility alongside contextual documents from the workspace, giving account teams and customers a single, consistent view of relevant information.

• Improves self-service for customers
• Reduces duplicate content storage
• Ensures portal content stays aligned with governed customer records

2. Project microsites connected to project workspaces

Flow: Bi-directional

For large programs or client engagements, Agility CMS can power a project microsite with milestones, announcements, and stakeholder updates, while OpenText Extended ECM Business Workspaces holds project plans, approvals, meeting notes, and deliverables. Updates from the workspace can trigger content changes on the microsite, and published project communications can be archived back into the workspace for audit and reference.

• Supports project transparency across internal and external audiences
• Creates a governed record of project communications
• Helps project managers and marketing teams work from the same source of truth

3. Case management content delivery for service teams

Flow: OpenText Extended ECM - Business Workspaces – Agility CMS

Service and support teams working in CRM or case management tools can use OpenText workspaces to store case-related correspondence, evidence, and resolution documents. Agility CMS can publish approved knowledge articles, troubleshooting steps, and customer-facing case updates that are linked to the relevant case workspace. This helps agents and customers access the right guidance without searching across disconnected systems.

• Speeds up case resolution
• Improves consistency of customer communications
• Reduces reliance on manual document sharing

4. Product launch content tied to product governance files

Flow: Bi-directional

Product marketing teams can use Agility CMS to publish launch pages, campaign landing pages, and product feature content, while OpenText Extended ECM Business Workspaces stores product specifications, compliance approvals, legal reviews, and launch checklists. When a product is approved in the workspace, Agility can automatically release the corresponding web content. If product details change, the workspace can notify content owners to update the public pages.

• Reduces launch delays caused by manual approvals
• Improves compliance control over published content
• Keeps marketing content aligned with approved product data

5. Documented sales enablement content for account teams

Flow: OpenText Extended ECM - Business Workspaces – Agility CMS

Sales teams often need current collateral, proposal templates, and customer-specific materials stored in governed workspaces. Agility CMS can publish approved sales enablement pages, campaign assets, and account-specific landing pages, while OpenText workspaces retain the underlying contracts, proposals, and supporting documents. This gives sales teams a controlled way to access current content while preserving document governance.

• Ensures only approved materials are used externally
• Improves access to account-specific content
• Supports faster proposal and response cycles

6. Compliance-approved content publishing workflow

Flow: Agility CMS – OpenText Extended ECM - Business Workspaces

Regulated organizations can manage content approval in OpenText workspaces, where legal, compliance, and business stakeholders review documents and metadata before release. Once approved, the final version is pushed to Agility CMS for publication on websites, portals, or campaign pages. This creates a controlled publishing process that separates content creation from content release.

• Supports auditability and approval traceability
• Reduces risk of publishing unapproved content
• Fits regulated industries such as financial services, healthcare, and manufacturing

7. Centralized knowledge hub for internal and external audiences

Flow: Bi-directional

Organizations can use Agility CMS to publish a public or partner-facing knowledge hub, while OpenText Extended ECM Business Workspaces stores the authoritative internal documents, policies, and reference materials behind the scenes. Content owners can update internal documents in OpenText, and selected approved content can be syndicated to Agility for external consumption. This keeps internal governance intact while enabling broader content reuse.

• Eliminates duplicate content authoring
• Improves consistency across internal and external channels
• Makes it easier to maintain a single governed content source

8. Customer onboarding experience linked to onboarding workspaces

Flow: Agility CMS – OpenText Extended ECM - Business Workspaces

Agility CMS can power onboarding journeys with step-by-step instructions, checklists, and instructional content for new customers or partners. OpenText Extended ECM Business Workspaces can store signed agreements, onboarding forms, implementation documents, and task-related correspondence tied to each onboarding case. The integration allows onboarding teams to present a polished digital experience while maintaining full document control and process visibility in the workspace.

• Improves onboarding completion rates
• Reduces manual follow-up and document chasing
• Provides a structured record of onboarding activities