OpenText DAM (OTMM) - Zendesk Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Zendesk

OpenText DAM (OTMM) manages rich media assets such as product images, campaign creative, event footage, and broadcast content, while Zendesk centralizes customer support across email, chat, social, and voice. Integrated together, they help support teams resolve issues faster by giving agents direct access to approved visual content, while also helping marketing and content teams understand which assets are driving customer questions and incidents.

1. Agent Access to Approved Product Images for Faster Case Resolution

Data flow: OpenText DAM (OTMM) to Zendesk

When customers submit tickets about product appearance, packaging, missing parts, or setup issues, Zendesk agents can retrieve approved product images directly from OTMM within the ticket view. This reduces time spent searching shared drives or asking other teams for visuals.

• Support agents attach the correct product image to explain assembly steps or identify the right SKU.
• Agents use version-controlled assets to avoid sharing outdated packaging or discontinued product visuals.
• Improves first response quality for retail, manufacturing, and consumer goods support teams.

2. Embedding Campaign and Promotional Assets in Customer Responses

Data flow: OpenText DAM (OTMM) to Zendesk

Customer service teams often need to reference current promotions, event materials, or product launch visuals when answering inquiries. OTMM can provide approved campaign assets to Zendesk so agents can include the right banner, flyer, or video in responses.

• Agents send consistent promotional content tied to active campaigns.
• Reduces risk of using expired or non-compliant marketing materials.
• Useful for retail, hospitality, and subscription businesses handling offer-related questions.

3. Support Ticket Enrichment with Asset Metadata for Better Routing

Data flow: OpenText DAM (OTMM) to Zendesk

OTMM asset metadata such as product line, campaign name, region, language, usage rights, or publication date can be passed into Zendesk to help classify and route tickets more accurately. This gives support managers better context for triage and escalation.

• Tickets related to a specific product image or video can be routed to the correct product support queue.
• Regional or language-specific assets help direct cases to the right team.
• Metadata improves reporting on which content assets generate the most support demand.

4. Customer-Reported Media Issues Sent from Zendesk to OTMM for Review

Data flow: Zendesk to OpenText DAM (OTMM)

When customers report broken links, incorrect images, outdated videos, or missing media on a website or in a catalog, Zendesk can send the issue details and related ticket context to OTMM for content review and correction. This creates a direct workflow between support and content operations.

• Support tickets can trigger review tasks for DAM administrators or content owners.
• Teams can identify whether the issue is an asset problem, a publishing problem, or a channel-specific rendering issue.
• Speeds correction of customer-facing content defects.

5. Sharing Museum or Heritage Collection Media with Public Inquiry Teams

Data flow: OpenText DAM (OTMM) to Zendesk

Museums and heritage organizations often receive public inquiries about artifacts, exhibits, or archival material. OTMM can supply curated images and videos to Zendesk so support or visitor services teams can respond with accurate visual references.

• Agents can attach collection images to answer identification or provenance questions.
• Approved media helps maintain consistency in public communications.
• Supports visitor services, education teams, and donor relations with fast access to collection content.

6. Video Asset Delivery for Technical Support and How-To Guidance

Data flow: OpenText DAM (OTMM) to Zendesk

For products that require setup, troubleshooting, or maintenance, OTMM can provide short-form instructional videos to Zendesk agents. These videos can be shared in tickets or chat to guide customers through resolution steps.

• Agents use step-by-step videos instead of long text instructions.
• Reduces repeat contacts for common issues.
• Works well for electronics, appliances, and complex consumer products.

7. Support Insights Informing Asset Updates and Content Governance

Data flow: Zendesk to OpenText DAM (OTMM)

Zendesk ticket trends can be analyzed to identify which images, videos, or campaign assets are causing confusion, complaints, or repeated questions. Those insights can be sent back to OTMM teams to update or retire problematic assets.

• Frequent tickets about a product image can trigger asset replacement or relabeling.
• Support feedback helps content teams improve clarity and compliance.
• Creates a closed loop between customer support and digital asset governance.

8. Cross-Team Workflow for Broadcast and Event Content Requests

Data flow: Bi-directional

When support teams receive requests for event footage, broadcast clips, or media assets from customers, partners, or internal stakeholders, Zendesk can capture the request and send it to OTMM for fulfillment. Once the asset is approved or located, OTMM can return the asset link or status update to the Zendesk ticket.

• Centralizes media requests in Zendesk while keeping asset control in OTMM.
• Improves turnaround time for high-value media requests.
• Useful for media companies, marketing teams, and organizations managing large video libraries.

Overall, integrating OpenText DAM (OTMM) and Zendesk helps organizations connect customer support with governed media access, improving response speed, content accuracy, and collaboration between support, marketing, and content operations teams.