WebWorks Platform.
The cloud service that hosts AI Knowledge Bases and powers the Reverb AI Assistant for ePublisher-published help.
The cloud service behind AI-assisted help.
WebWorks Platform is a cloud service purpose-built for documentation teams shipping AI-assisted help. Documentation teams log in to Platform to create and configure Assistants — the chat objects that respond to end-user questions in published Reverb 2.0 help — upload and manage Knowledge Bases populated from ePublisher-generated Knowledge Files, and author the customer prompt that defines each Assistant's role, scope, and refusal behavior.
When an end user asks a question in published Reverb 2.0 help, the chat surface invokes the Platform-hosted Assistant by Assistant ID, Platform runs a fresh per-query search against the Knowledge Base, and the response returns with annotation links back into the help. Platform is where the Assistant and Knowledge Base live; it is not a destination end users visit directly.
How Platform fits in the WebWorks pipeline.
Platform sits between ePublisher (the publishing tool) and Reverb 2.0 published help (the deployed output) for any helpset that has Reverb AI chat enabled.
Generates Reverb 2.0 HTML output and matching Knowledge Files.
Hosts the Assistant. Stores the Knowledge Base. Runs per-query retrieval.
Renders the chat surface alongside topic pages.
The content bridge. ePublisher generates one markdown page per HTML page, sharing the helpset's landmark ID structure. Uploaded to Platform as a zip.
The wiring bridge. Configured in Platform, copied into the Reverb 2.0 Target Settings in ePublisher, so the published help knows which Assistant to invoke.
Platform is the enabler.
Publishing pipeline. No AI.
AI service. Scoped to your documentation.
Platform is the WebWorks ecosystem's AI-readiness layer. ePublisher is the publishing pipeline; no AI runs there. Platform is the separately scoped product where AI capabilities run.
For customers who want AI-assisted help: upload Knowledge Files to Platform, wire the Assistant ID into ePublisher, and the next Reverb 2.0 publish ships with chat. For customers who want documentation publishing without AI: keep using ePublisher, do not enable an Assistant, and nothing in the workflow changes.
This split matters for compliance reviews. AI screening questionnaires can be answered against ePublisher (no AI) and Platform (AI service, scoped to the customer's own documentation) as distinct products.
Built for documentation teams shipping AI-assisted help.
Platform is not a general-purpose AI chat tool. The differentiation is structural rather than feature-list — the service is shaped around how technical documentation actually ships.
The Knowledge Base is populated by Knowledge Files that ePublisher generates from the same source you publish as Reverb 2.0 help. Answers are grounded in your documentation set, not in a vendor index of the open web.
Assistants are wired to Reverb 2.0 targets through Assistant IDs configured in ePublisher Target Settings. Enabling chat is a publishing-pipeline change, not a separate deployment project.
Platform runs a new search against the Knowledge Base for every end-user question. There is no static snapshot baked at index time and no nightly re-index step you have to manage.
End users of the published help do not have Platform accounts. The chat surface is part of the help; Platform sits behind it. The customer-facing login is for the documentation team configuring Assistants, not for readers.
Who Platform is for.
Documentation teams deploying AI-assisted help.
The teams responsible for shipping Reverb 2.0 help with the AI Assistant enabled. They configure Assistants, upload Knowledge Bases, and author the customer prompt.
- · Platform is where the Assistant lives. Assistant configuration and Knowledge Base management happen here; the published help just invokes what you set up.
- · The Knowledge Base is generated from your published documentation. ePublisher emits Knowledge Files as part of the Reverb 2.0 build; you upload the zip to Platform; the Assistant retrieves from it on every question.
- · The customer prompt is yours to author. Platform stores it; the Assistant uses it. No vendor-authored persona is layered on top.
- · Routine documentation updates only need a fresh Knowledge Files upload when page content has changed. Prompt edits and other Assistant config tweaks happen in Platform without rebuilding the docs.
ePublisher customers upgrading their workflow.
Existing ePublisher customers who already publish Reverb 2.0 help and are evaluating whether to enable the AI Assistant. Not adopting a new tool stack — extending the one you already operate.
- · Enabling Reverb AI chat is a configuration change in your existing pipeline, not a new platform to deploy. Reverb 2.0 already produces the Knowledge Files; Platform hosts them.
- · The Assistant inherits your publishing cadence. Whatever schedule you already use for Reverb 2.0 republishes is the schedule on which the Assistant's Knowledge Base updates.
- · Source format does not change. Whatever you author in today — Markdown++, Word, FrameMaker, DITA — keeps flowing through ePublisher. Markdown++ source produces a higher-quality Knowledge Base, but no source migration is required.
- · The customer prompt and other Assistant config live in Platform; the rest of the publishing config stays in ePublisher. AI-specific behavior is configured where the Assistant runs, not in the publishing engine.
Ready to configure your first Assistant?
Sign in to WebWorks Platform to create Assistants, upload Knowledge Bases, and wire AI-assisted chat into your Reverb 2.0 published help.
Sign In to Platform