OpenText Extended ECM - Business Workspaces - Kentico Integration and Automation

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

1. Customer Portal Content Linked to Customer Workspaces

Data flow: OpenText Extended ECM - Business Workspaces ? Kentico

Customer-facing content in Kentico can be dynamically sourced from OpenText business workspaces tied to specific customers, accounts, or service cases. This allows account-specific documents such as contracts, onboarding packs, product manuals, or case-related updates to be published in a secure portal without duplicating content.

• Improves self-service by giving customers access to relevant, approved documents
• Reduces manual publishing effort for customer service and web teams
• Maintains governance by keeping the system of record in OpenText

2. Approved Marketing Assets Published to Kentico

Data flow: OpenText Extended ECM - Business Workspaces ? Kentico

Marketing teams can manage approved brochures, datasheets, images, and campaign collateral in OpenText workspaces and publish selected assets to Kentico for website or campaign use. Kentico then serves the latest approved version across landing pages, product pages, and campaign microsites.

• Ensures only approved content is exposed on public channels
• Eliminates version confusion between marketing and web teams
• Speeds up campaign launches by reusing governed content

3. Web Form Submissions Routed into Case or Project Workspaces

Data flow: Kentico ? OpenText Extended ECM - Business Workspaces

Lead forms, support requests, partner applications, or project intake forms submitted through Kentico can automatically create or update a corresponding business workspace in OpenText. Submitted documents, metadata, and customer details are stored in the workspace for review, approval, and follow-up by operations teams.

• Creates a structured handoff from digital channels into back-office processes
• Reduces rekeying and manual case creation
• Improves response times for sales, service, and project teams

4. Personalized Content Delivery Based on Workspace Metadata

Data flow: Bi-directional

Metadata from OpenText workspaces such as customer segment, project status, contract stage, or case priority can be synchronized to Kentico to drive personalized website experiences. Kentico can then present different content, offers, or support resources based on the current business context stored in OpenText.

• Enables more relevant digital experiences for customers and partners
• Aligns web content with real-time business status
• Supports targeted messaging for high-value accounts or active cases

5. Secure Document Access from Kentico Customer and Partner Portals

Data flow: OpenText Extended ECM - Business Workspaces ? Kentico

Kentico portals can provide authenticated users with secure access to documents stored in OpenText workspaces, such as statements, project deliverables, compliance certificates, or service reports. Access can be controlled by workspace permissions and user identity rules.

• Provides a single portal for both content and transactional information
• Improves customer and partner experience with easy document retrieval
• Preserves enterprise security and auditability in OpenText

6. Campaign Response and Lead Qualification Workspace Creation

Data flow: Kentico ? OpenText Extended ECM - Business Workspaces

When a visitor engages with a Kentico campaign, downloads gated content, or requests a demo, the interaction can trigger creation of a lead or opportunity workspace in OpenText. The workspace can store the lead record, related documents, follow-up tasks, and approval history for sales operations.

• Connects digital engagement directly to sales execution
• Improves lead tracking and accountability across teams
• Supports faster qualification and handoff to sales representatives

7. Compliance-Managed Content Publishing Workflow

Data flow: Bi-directional

Content created in Kentico for regulated industries such as financial services, healthcare, or manufacturing can be routed to OpenText for review, legal approval, and retention before publication. Once approved, the final version is published back to Kentico, while OpenText retains the governed record and audit trail.

• Supports controlled publishing for regulated content
• Reduces compliance risk by enforcing approval workflows
• Creates a defensible record of what was approved and published

8. Project or Case Status Updates Reflected on Public or Partner Sites

Data flow: OpenText Extended ECM - Business Workspaces ? Kentico

For customer projects, warranty cases, or service engagements, status updates maintained in OpenText can be surfaced in Kentico portals as milestone progress, delivery updates, or service notifications. This gives external users visibility without exposing internal workspace details.

• Improves transparency for customers and partners
• Reduces inbound status inquiries to support teams
• Keeps operational updates synchronized with the source of truth