Platform reference · Zendesk Guide · Zendesk Suite · ADA Title III · WCAG 2.1 AA · SaaS support training · Agent enablement

Zendesk captions: Help Center video, agent training, and ADA compliance for SaaS support teams

Zendesk is the customer service platform used by tens of thousands of SaaS companies, ranging from ten-person startups to multi-thousand-seat enterprise support organisations. Zendesk's two distinct content domains each carry their own captioning obligations. The first is Zendesk Guide — the Help Center and knowledge base platform where companies publish customer-facing articles, walkthroughs, and video tutorials explaining their product. Help Center video is public-facing content that sits on a subdomain of the company's product (support.company.com or company.zendesk.com) and is accessible to any visitor, including visitors with hearing disabilities. This is ADA Title III "place of public accommodation" territory: US businesses with public-facing websites that contain video must caption that video to WCAG 2.1 AA SC 1.2.2 accuracy. The second domain is internal agent training — onboarding video for new support agents, Zendesk product-walkthrough training, QA calibration session recordings, Zendesk Suite feature-update walkthroughs — which is internal L&D content that carries employer accommodation obligations under ADA Title I and state disability laws for hearing-impaired support agents.

TL;DR

Zendesk Guide Help Center video is typically embedded from YouTube or Vimeo — the caption track on the embedded video comes from the originating platform (YouTube Studio, Vimeo). To caption Help Center video, upload a corrected SRT/VTT to the YouTube or Vimeo video, and the corrected track displays in the embedded player on the Zendesk Help Center article page. Internal agent training video hosted on Loom, Vimeo, Wistia, or Microsoft Stream uses the same source-platform caption workflow. For video files uploaded directly to Zendesk Guide articles (rare — Zendesk Guide is primarily a text+embed platform), Zendesk does not have a built-in caption upload UI; the preferred workflow is to host the video on a captioning-capable platform (Vimeo, YouTube, Stream) and embed from there. Compliance: Help Center video needs WCAG 2.1 AA-accurate captions under ADA Title III. Agent training video needs WCAG 2.1 AA-accurate captions for hearing-impaired agents under ADA Title I and state law (California FEHA, New York HRL, etc.). The Zendesk Suite proper-noun vocabulary — Zendesk Suite product names, workflow terminology, and the customer's product-specific vocabulary discussed in support training — is a systematic auto-caption failure point that glossary-biased captioning addresses.

Zendesk Guide Help Center — caption surface and ADA Title III obligation

Zendesk Guide is Zendesk's knowledge management system that powers customer-facing Help Centers, internal agent knowledge bases, and community forums. The video content in a Zendesk Help Center falls into two categories:

Embedded YouTube and Vimeo video

The vast majority of video in Zendesk Guide articles is embedded from YouTube or Vimeo. When an author inserts a YouTube or Vimeo URL in a Zendesk Guide article, Zendesk renders an embed of that video in the article page. The caption track that displays is the caption track on the originating YouTube or Vimeo video. The captioning workflow for embedded Help Center video:

Go to YouTube Studio (for YouTube-hosted video) or your Vimeo account (for Vimeo-hosted video).
Upload a corrected SRT or VTT caption file to replace or supplement the auto-generated caption track.
The corrected caption track propagates automatically to all embeds of that video — including the Zendesk Guide article embed.

The auto-generated captions on YouTube or Vimeo do not satisfy WCAG 2.1 AA SC 1.2.2 for Help Center video that discusses product-specific terminology, support workflows, or technical features. YouTube auto-captions for a SaaS product walkthrough video will mangled every product-specific term — feature names, menu paths, integration names, API concepts — that appears in the narration.

ADA Title III for public-facing Help Center video

ADA Title III (42 U.S.C. § 12181 et seq.) prohibits discrimination by "places of public accommodation" on the basis of disability. US courts and the DOJ have consistently held that commercial websites providing goods and services to the public are places of public accommodation. A Zendesk Help Center hosted at support.company.com or company.zendesk.com, accessible to any member of the public including prospective customers and existing customers with hearing disabilities, is a public accommodation for Title III purposes. Video in that Help Center that lacks accurate captions discriminates against visitors with hearing disabilities by denying them equal access to the information the video conveys.

Key Title III considerations for SaaS companies with Zendesk Help Centers:

California Unruh Act exposure. Help Centers accessible to California residents carry per-violation Unruh Act exposure of $4,000 per incident in addition to federal Title III claims. California plaintiffs' counsel has brought cases against SaaS companies with inaccessible Help Center video.
New York Human Rights Law. NY HRL's "place of public accommodation" definition covers commercial websites accessible to New York residents. A Help Center that includes product walkthrough video without accurate captions is a potential NYCHRL violation for companies with New York users.
DOJ Title III settlements. The DOJ has settled with companies over web accessibility including video captioning failures under Title III. Settlements typically require WCAG 2.1 AA remediation of all video content, annual accessibility reports, and user feedback mechanisms for reporting accessibility barriers.

Customer self-service equity and product metrics

Beyond compliance, Help Center video accessibility directly affects customer self-service rates. A support team that invests in video walkthroughs to deflect support tickets loses that deflection value for customers with hearing disabilities who cannot access uncaptioned video. Accessible Help Center video expands the population for whom self-service is possible — which is why accessibility and deflection-rate optimisation are complementary, not competing, goals.

Internal agent training — Zendesk L&D content types

The second captioning domain is internal: the training and enablement video that support-operations and L&D teams produce for Zendesk agents. This content includes:

Zendesk onboarding training. New agent onboarding walkthroughs that explain how the company uses Zendesk: ticket workflow, ticket views, macros, triggers, automations, SLAs, escalation paths, how tickets move between groups, how CSAT surveys are configured, and how the company's product-specific knowledge base is organised. Typically produced as Loom or Camtasia screen-capture walkthroughs of the company's Zendesk instance.
Zendesk product update training. When Zendesk releases new features (new Agent Workspace UI, new Sunshine Conversations channel, new Workforce Management or QA features), the support-ops team often produces an internal video explaining the change and the new workflow. These update videos reference Zendesk product names and UI element names by definition.
QA calibration session recordings. Zendesk QA (formerly Klaus, acquired by Zendesk) is a quality-assurance tool for support agents. QA calibration sessions — where the QA team reviews tickets together and aligns on scoring criteria — are often recorded and posted as training reference for agents. These recordings reference Zendesk QA terminology, the company's internal QA rubric, and ticket-handling vocabulary.
Product deep-dive training for support agents. Internal training on the product that the company's support agents are supporting — feature walkthroughs, bug-vs-feature-request distinction training, release-note walkthroughs explaining what changed in the product that week. This content combines Zendesk vocabulary with the company's own product vocabulary (which is the densest proper-noun layer for glossary purposes).

Employer accommodation obligation for hearing-impaired agents

Support agents with hearing disabilities are a real population at SaaS customer support teams. ADA Title I (federal, 15+ employees), California FEHA (5+ employees), New York HRL (4+ employees), and New Jersey LAD (all employers) each independently require employers to provide reasonable accommodation to employees with disabilities. Providing accessible training — training that hearing-impaired agents can access with accurate captions — is a core reasonable accommodation. An employer that deploys Loom-recorded Zendesk onboarding training with Loom's auto-generated caption track (which fails on every Zendesk-specific and product-specific term) may not be providing a reasonable accommodation to a hearing-impaired new-hire who relies on that training to learn their role.

The Zendesk Suite proper-noun failure mode

Zendesk training video has a compound proper-noun failure mode: the Zendesk platform's own vocabulary combined with the SaaS company's product vocabulary. Both layers are outside generic STT training data:

Zendesk platform vocabulary

Zendesk Suite product names. Zendesk Suite, Zendesk Support, Zendesk Guide, Zendesk Chat, Zendesk Talk, Zendesk Sell (CRM), Zendesk Sunshine (CRM platform), Zendesk Explore (analytics), Zendesk QA (formerly Klaus — the acquisition name still used colloquially), Zendesk WFM (Workforce Management, formerly Tymeshift — again, the prior brand still circulates), Zendesk Bots (the AI/automated resolution product), Zendesk Agent Workspace, Zendesk Messaging.
Zendesk workflow and configuration terms. Triggers (automated actions that fire on ticket conditions), Automations (time-based automatic actions), Macros (one-click agent-response templates), Views (filtered ticket queues), Ticket Fields (custom data fields on tickets), Ticket Forms (multi-field input forms for ticket submission), Side Conversations (internal side threads on a ticket), Organizations (account-level grouping of users), Groups (agent groupings for routing), Brands (multi-brand Help Center support), Dynamic Content (locale-aware content strings), Business Hours (SLA schedule configuration), Routing Rules (Skills-based routing configuration).
Zendesk metrics and reporting terms. CSAT (Customer Satisfaction score, 1-5 stars or good/bad), First Reply Time, Full Resolution Time, SLA (Service Level Agreement), OLA (Operational Level Agreement), TTFR (Time to First Reply), TTTF (Time to Full Resolution), Ticket Volume, Deflection Rate, One-Touch Ticket Rate, Ticket Backlog, Reopened Tickets — all of which appear frequently in QA calibration videos and support-metrics training.
Zendesk AI and automation vocabulary. Zendesk AI (the product line), Intent Detection, Intelligent Triage, Intelligent Routing, Automated Resolutions, Answer Bot, Flow Builder, Sunshine Conversations, messaging channels (WhatsApp, Line, WeChat, Twitter DM, Apple Messages for Business, Slack).

Customer product vocabulary layer

Every SaaS company's agent training video references that company's product by name — feature names, plan tiers, integration names, pricing model terms. Generic STT systems that have never seen the company's product vocabulary cannot transcribe these terms correctly. The product-vocabulary layer is the reason that even a well-configured generic STT system fails on SaaS support training: a support agent training video for a SaaS product that discusses "the Canvas integration," "the Brightspace module," "the Salesforce sync," "the HIPAA-compliant data export," or "the SOC 2 Type II attestation" uses vocabulary that is dense, product-specific, and requires a company glossary to transcribe correctly.

Caption workflow for common Zendesk-adjacent video platforms

Support-operations teams at SaaS companies produce Zendesk training video on a mix of tools:

Loom. Loom is the async-video default for SaaS support teams. Loom captions covers the transcript-replacement workflow: on Loom Business/Enterprise plans, upload a corrected VTT to replace Loom's auto-generated transcript. The corrected transcript/caption track then displays in all embeds of that Loom video, including Zendesk Guide article embeds of Loom-hosted walkthroughs.
Vimeo. Support-ops teams that use Vimeo for video hosting (more control over player branding than YouTube) upload SRT or VTT to the Vimeo video settings. The corrected track displays in the Zendesk Guide embed. Vimeo captions covers the upload workflow.
YouTube. YouTube-hosted Help Center video and public Zendesk Guide walkthroughs: upload a corrected caption file via YouTube Studio → Subtitles. The corrected track replaces YouTube's auto-generated track in all embeds.
Wistia. Wistia is used by SaaS companies for customer-facing and internal video. Wistia supports SRT upload; the CC button appears in the Wistia player embedded in Zendesk Guide articles. Wistia's Channels feature for a customer-education knowledge base can be used alongside Zendesk Guide for a more polished video-first knowledge base experience.
Camtasia. Camtasia is used for recorded Zendesk screen-capture walkthroughs. Camtasia exports SRT and can burn captions into the video. For SRT-based captioning, the Camtasia SRT export feeds into the video hosting platform (YouTube, Vimeo, Wistia) as the corrected caption file.

See GlossCap pricing

FAQ — Zendesk captions

Does Zendesk Guide have a built-in caption tool for video articles?

No. Zendesk Guide is a text and embedded-media platform; it does not have a built-in speech-to-text caption generator or caption file upload UI for video. Video in Zendesk Guide articles is typically embedded from YouTube, Vimeo, Loom, or Wistia. The caption track for those embedded videos is managed in the originating platform (YouTube Studio, Vimeo, Loom, Wistia) — you upload the corrected SRT or VTT there, and it propagates to all embeds of that video including the Zendesk Guide article embed. If a video is uploaded directly to Zendesk Guide as a file attachment (uncommon), it plays in the browser's native video player, which does not render an attached caption file. The recommended workflow for captioning direct-upload Zendesk Guide video is to move the video to a captioning-capable platform and embed from there.

Does the ADA Title III obligation apply to our Zendesk Help Center if we're a B2B SaaS company?

Yes. ADA Title III applies to "places of public accommodation" — a category courts have extended to commercial websites accessible to the public. A Zendesk Help Center accessible to any member of the public, including prospective customers, is a public accommodation for Title III purposes regardless of whether the company's business model is B2B or B2C. The distinction between B2B and B2C is relevant to your customer mix, not to the legal public-accommodation analysis. If your Help Center is accessible to anyone who types your support URL (not behind authentication), it is public-facing content subject to ADA Title III accessibility requirements. A Help Center that is accessible only to authenticated users (behind a Zendesk Guide Restricted Help Center requiring login) has a narrower public-accommodation analysis, but the employer accommodation obligation under ADA Title I still applies for hearing-impaired customers who are your signed-up users.

What about Zendesk QA (formerly Klaus) video content?

Zendesk QA (formerly Klaus) records and replays ticket and voice interactions for QA review. QA calibration sessions where reviewers discuss ticket scores — typically in a video call (Zoom, Teams, Google Meet) that is then recorded and shared as training reference — are internal training content subject to employer accommodation obligations. The QA calibration video recording should be captioned with accurate captions that include both the QA-specific vocabulary (Klaus/Zendesk QA scoring dimensions, rubric names, calibration criteria) and the product vocabulary referenced in the ticket examples being reviewed. The recording platform (Zoom, Teams, Meet) produces an auto-transcript that can be corrected and used as the VTT sidecar for the recording.

Can we use YouTube's auto-generated captions for our Zendesk Help Center video?

YouTube auto-generated captions do not satisfy WCAG 2.1 AA SC 1.2.2's "accurately convey the audio" standard for product-specific or technical Help Center content. YouTube's speech-to-text model handles general English well but mis-transcribes product names, feature names, technical terminology, and proper nouns that appear in SaaS product walkthrough videos. A video walkthrough of your product that references your company's specific feature names, plan tiers, and integration names will have systematic caption errors on every product-specific term. The corrected caption approach — producing an accurate SRT via glossary-biased captioning and uploading it to YouTube Studio — replaces the auto-generated track and satisfies SC 1.2.2. The corrected track is what displays in all YouTube embeds, including the Zendesk Guide article embed.