OpenText TeamSite - LiveSite Content Services - ServiceNow Integration and Automation

Common Integration Use Cases Between OpenText TeamSite - LiveSite Content Services and ServiceNow

1. Self-Service IT and Service Catalog Portals with Personalized Content

Data flow: ServiceNow → OpenText TeamSite - LiveSite Content Services

Use ServiceNow as the system of record for service catalog items, request forms, approvals, and case status, while OpenText TeamSite - LiveSite Content Services delivers the customer-facing or employee-facing portal experience. The portal can personalize content based on user role, location, department, or request history, and surface the most relevant ServiceNow services and knowledge articles.

• Improves request deflection through guided self-service
• Reduces call center and help desk volume
• Creates a consistent branded experience across digital channels

2. Dynamic Incident and Case Status Updates on Customer Portals

Data flow: ServiceNow → OpenText TeamSite - LiveSite Content Services

When customers or employees submit incidents, complaints, or support cases in ServiceNow, the case status, milestones, and resolution updates can be displayed in real time on a portal powered by OpenText TeamSite - LiveSite Content Services. This is especially useful for high-volume support operations, such as telecom, utilities, healthcare, or internal IT support.

• Reduces inbound status-check calls and emails
• Improves transparency and customer satisfaction
• Supports branded, role-based case tracking experiences

3. Knowledge Article Publishing for Customer-Facing Support Content

Data flow: ServiceNow → OpenText TeamSite - LiveSite Content Services

ServiceNow knowledge articles, FAQs, and troubleshooting guides can be published or syndicated to OpenText TeamSite - LiveSite Content Services for public or authenticated portal consumption. Content can be filtered by product, region, language, or customer segment to ensure users see only relevant support information.

• Accelerates knowledge reuse across support and digital channels
• Improves first-contact resolution through better self-help content
• Enables controlled publishing workflows and content governance

4. Personalized Service Notifications and Proactive Communications

Data flow: ServiceNow → OpenText TeamSite - LiveSite Content Services

ServiceNow can trigger personalized portal messages for planned maintenance, outage notifications, policy changes, or service disruptions. OpenText TeamSite - LiveSite Content Services can render these messages dynamically based on affected users, business units, geography, or service subscriptions.

• Improves communication during incidents and maintenance windows
• Targets only impacted users to reduce noise
• Supports proactive service management and trust building

5. Employee Onboarding and Offboarding Experience Orchestration

Data flow: Bi-directional

OpenText TeamSite - LiveSite Content Services can provide the onboarding or offboarding portal experience, while ServiceNow manages the workflow tasks, approvals, and fulfillment steps across HR, IT, facilities, and security. The portal can show progress, required actions, and personalized next steps for each employee or manager.

• Coordinates cross-functional onboarding tasks in one experience
• Reduces missed handoffs between HR, IT, and facilities
• Improves employee experience during critical lifecycle events

6. Request Fulfillment for Digital Content and Portal Changes

Data flow: OpenText TeamSite - LiveSite Content Services → ServiceNow

Business users or content owners can submit requests from the OpenText TeamSite - LiveSite Content Services portal for new pages, content updates, access changes, or digital experience enhancements. These requests are created in ServiceNow as tasks or change records for review, approval, and fulfillment by IT or digital operations teams.

• Creates a governed intake process for content and portal changes
• Improves traceability and approval control
• Reduces ad hoc email-based requests

7. Unified Case Escalation from Digital Experience to Service Operations

Data flow: OpenText TeamSite - LiveSite Content Services → ServiceNow

When users interact with a portal and encounter issues such as failed transactions, broken forms, or missing content, the portal can automatically create incidents or problem records in ServiceNow with contextual details such as page URL, user segment, browser data, and transaction metadata. This helps support teams diagnose issues faster.

• Speeds root cause analysis with richer incident context
• Improves collaboration between digital, application, and support teams
• Supports faster restoration of service and content fixes

8. Service Health Dashboards and Operational Messaging for Business Users

Data flow: ServiceNow → OpenText TeamSite - LiveSite Content Services

ServiceNow operational data, such as major incident status, change windows, and service availability, can be surfaced in OpenText TeamSite - LiveSite Content Services dashboards or portal banners for business users and executives. This gives stakeholders a clear view of service health without requiring access to the ServiceNow interface.

• Improves visibility for non-technical stakeholders
• Supports executive communications during outages or major changes
• Reduces manual status reporting effort for IT teams