Design Center / Empower
Browser-based template authoring with embedded business logic. Business users design; compliance approves; the change ships as a versioned template.
Insurance, banking, utilities, and telco customer-experience teams have hundreds of document templates trapped in legacy composition engines — Group1 DOC1, CSF, Xerox VIPP, or aging in-house systems. A simple disclaimer change takes six weeks and a developer ticket. Regulators add new rules. Marketing wants personalised digital delivery the legacy stack cannot produce. OpenText Communications (formerly Exstream) is the CCM platform that consolidates statements, bills, policies, welcome kits across print, email, web, and SMS — with business-user authoring instead of developer tickets. BCS implements the migration off the legacy composition stack onto Communications.
Marketing, compliance, and product teams update templates in browser. Developer tickets for disclaimer changes retire.
Same composition engine outputs print, email, web, SMS, and mobile from one template. The channel mix evolves without re-platforming.
Plain-language acts, state insurance commissioner rules, GDPR requirements implement as template versions with audit trail.
Legacy customer communications platforms are developer-dependent and channel-locked. A disclaimer change requires a code change. A new channel requires a separate output system. The marketing team cannot personalise digital delivery without engineering involvement.
OpenText Communications separates the composition engine from the authoring surface. Business users author templates in a browser with embedded business logic. The composition server outputs the same template to print, email, web, SMS, and mobile. Regulator-mandated changes ship as template versions with audit trail.
Browser-based template authoring with embedded business logic. Business users design templates; compliance approves; the change ships as a versioned template. No developer ticket for routine template changes.
The batch and interactive composition engine. Processes millions of documents per day for statements, bills, policies. Same engine handles batch overnight runs and on-demand interactive customer service composition.
Channel orchestration based on customer preferences, regulatory requirements, and document type. Same template outputs to the channel mix the customer has chosen.
Customer service agents compose customer-specific documents during the live interaction. Agent UI surfaces the template, prefills customer data, lets the agent personalise within compliance-approved variations.
Generative AI assists with content suggestions, tone adjustment for plain-language compliance, and multi-language drafts. The AI works within the template framework, not as a separate composition surface.
Communications programmes start when one of four operational realities forces the decision.
Group1 DOC1, CSF, Xerox VIPP, or an aging in-house composition engine is running on infrastructure approaching end-of-life. The team that maintains it is shrinking. The CIO has accepted that the migration is unavoidable; the question is the destination platform.
Statements, policies, and welcome kits go out in print and PDF only. Customers expect mobile-first delivery, the marketing team cannot deliver, and the digital adoption rate is below industry benchmarks. The competitive pressure makes the decision.
State insurance commissioners, banking regulators, GDPR, plain-language acts add rules faster than the developer ticket queue can absorb. Every regulator change creates a six-week project. The compliance team needs template-versioned change control with audit trail.
The CMO has approved a customer-experience programme. Personalisation requires the composition platform to handle customer-specific content variations. The legacy composition stack cannot; the marketing automation platform cannot produce regulated documents. Communications fills the gap.
Communications has a CX/CMO-led buyer panel. Each accordion names the specific lever.
For CX, customer communications are the brand at scale. The platform decides whether digital delivery, personalisation, and channel preference work or remain aspirational.
For the CMO, the composition platform decides whether marketing can ship a customer communication change in days or in six weeks. Communications puts that authoring in marketing's hands.
For Billing (utilities, telco, banking), the platform decides whether bills go out on time, with accurate calculations, and with the digital channel mix customers expect.
For insurance Policyholder Services, every policy issuance, endorsement, and claim communication is regulated. Communications handles them with state-specific compliance built into the template.
For the CIO, Communications retires a mainframe-era composition platform. The infrastructure footprint reduces; the developer dependency for routine template changes retires.
For Compliance, every customer communication is a regulator-relevant artefact. Communications tracks template versions, approvals, and the audit trail through the change cycle.
For the CFO, customer communications carry direct mail costs and the operating cost of the legacy composition platform. Communications reduces both: digital channel adoption shifts volume off print, and the legacy platform retires.
For the CTO, Communications is the composition substrate that needs to integrate with the rest of the customer-facing stack — CRM, marketing automation, billing, claims systems.
Five product components spanning authoring, composition, orchestration, interactive, and AI.
Browser-based template authoring with embedded business logic. Business users design; compliance approves; the change ships as a versioned template.
The composition engine. Handles millions of documents per day for batch statements, bills, and policies. Also handles on-demand interactive composition for service interactions.
Multi-channel delivery orchestration based on customer preferences, regulatory rules, and document type. The same template outputs to print, email, web, SMS, mobile.
Agent-facing tool for live customer-specific document composition during service interactions. The agent works in a guided UI within compliance-approved variations.
AI-assisted content suggestions, tone adjustment for plain-language compliance, and multi-language drafts. AI works within the template framework.
Pre-built connectors to Guidewire, Duck Creek, FIS, Temenos, SAP IS-U for utilities, and Salesforce Service Cloud.
Template versions with approval workflow, audit trail, and regulator-ready change history. Every customer communication carries the template version reference.
A Communications programme typically runs 20-32 weeks for the migration of the first major template estate. BCS sequences six workstreams.
The legacy template estate is inventoried. Volumes by document type, regulatory variations, channel mix per template, and customer-impact tier are catalogued. The migration scope is sequenced.
BCS owns: inventory tooling, scope analysis, migration sequencing. Client owns: template owners, regulatory variation data, business priority.
The template design system in Design Center / Empower is configured. Brand standards, compliance variations, and reusable components are codified. Business users are onboarded to authoring.
BCS owns: design system, authoring environment, training. Client owns: marketing and compliance owners for the design system sign-off.
The highest-priority templates (largest volume, highest customer impact, most regulator-relevant) migrate first. Communications Server batch composition validated against legacy output. Variation testing per state, channel, customer segment.
BCS owns: template migration engineering, output validation. Client owns: compliance review of migrated templates.
Communications Orchestration configured for the channel mix. Customer preference integration to the CRM or customer master configured. Print, email, web, SMS, mobile delivery paths tested.
BCS owns: orchestration configuration, channel testing. Client owns: CRM access, customer preference data.
Inspire Interactive configured for customer service composition. Guidewire / Duck Creek / FIS / Salesforce connectors activated for the policy or billing data sources. Pilot service agents trained on the interactive composition surface.
BCS owns: Inspire configuration, connector setup, agent training. Client owns: service agent enablement, connector source system access.
Production cutover for the migrated template estate. Legacy composition platform runs in parallel for a defined window. Decommissioning plan executes once stability is proven. Generative AI activation for content authoring assistance.
BCS owns: cutover orchestration, parallel-run management, decommissioning. Client owns: sign-off on stability criteria, decommissioning approval.
BCS implements Communications as part of the broader OpenText practice. The CCM team understands regulated communications — insurance policies, bank statements, utility bills — not just generic marketing automation.
The agentic system integrator model means three operating platforms travel with every Communications programme.
Identity governance over template authoring, approval, and version-release rights. Compliance, brand, and product authors carry the access certification each role needs.
Customer master validation that runs before composition binds. Inconsistent customer records, duplicate identities, and outdated preferences are remediated so personalisation lands on accurate customer identity.
Migration orchestration for the legacy-to-Communications cutover. Parallel-run management, validation gates per template wave, and rollback path execute as one workflow.
Three updates that shape the Communications conversation in 2026.
OpenText recognised as a Leader in IDC MarketScape: Worldwide Intelligent Customer Communications Management 2024 and Worldwide Automated Document Generation and CCM 2024 (both December 2024).
Source: OpenText IDC MarketScape recognitionKnowledge-driven generative AI assists template authors with content suggestions, tone adjustment for plain-language compliance, and multi-language drafts. The AI works within the template framework, not as a parallel composition surface.
Source: OpenText CommunicationsThe Exstream product name was simplified to OpenText Communications in the August 2025 rebrand. The Exstream heritage name remains in technical documentation. In-flight programmes are unaffected.
Source: OpenText rebrandThe five questions that decide the Communications programme.
BCS runs a 30-minute readiness session covering the legacy composition platform state, the template estate inventory, the channel mix priority, the regulatory variation scope, and the industry-system integration plan.
30-minute discovery session*