Self-updating product documentation. Backed by real, human review.
Workover is the only way to responsibly hand your product documentation to agents. And not just any agent: Workover AI, engineered at industry-leading DevTool startups and enterprise companies, with continuous human review.
You recentlyadded a language.
And yet your documentation was last updated three months ago. Workover is here to change that.
Agents that maintain your documentation 24/7. So you can ship faster with confidence.
Connect your tools, and Workover holds every current and future article up against how your product works, fixing what is wrong, and writing the documentation for what’s new.
Connect your tools.
Your codebase, your support inbox, and a login to your product. About ten minutes, and Workover can see what your customers see.
Every article gets checked, and the fix gets written.
Each claim is checked against your product and your tickets. Anything wrong comes back as a change, with the reason it changed.
New releases document themselves.
A pull request merges to staging or production, and Workover prepares the documentation before the release ships to users.
Verified against your actual product.
Not "AI-assisted". Not "human in the loop" as a figure of speech.
A human reviewer uses your product, confirms the help article describes what it does, and fixes the voice against the style guide we build with you.
You set the pace.
Manual Verification
SlowestYou approve every help article before it goes live
Workover writes it and checks it against your product, then it waits for you. Nothing publishes until you say so, and some teams want exactly that.
Workover Verification
Most teamsWe check every help article before it goes live
A human reviewer checks it against your product, then it publishes. You see it afterwards rather than waiting on it.
Workover Retroactive Verification
FastestIt publishes straight away, we review afterwards
Drafts go live as soon as Workover AI finishes, and a human reviewer goes over them retroactively and fixes anything wrong. The least waiting on anybody.
Three things, and about ten minutes.
There is no migration, no rewrite, and nothing for your team to run. This is it.
Connect your systems so Workover can explore your product
Connect your codebase (GitHub, GitLab, or Bitbucket). Workover AI never gets access to your source code. All analysis is run in place on your Git provider of choice.
- GitHub
- GitLab
- Bitbucket
Connect your customer support platform and Workover AI will use both customer questions and your support team’s replies to detect documentation that is missing or needs updating.
- Help Scout
- Plain
- Freshdesk
- Zendesk
- Intercom
Customer details are automatically redacted before any of it is used in AI analysis.
Connect your live product.
Yes, we need a login to your product. The goal is to let Workover see exactly what your customers see. It is the same access we would have if we signed up for your product ourselves, and it is what lets Workover open the screen a help article is describing and capture it.
- Used for two things
- Signing in to capture screenshots, and checking that a draft matches what the product does.
- We tell you if it breaks
- If the login stops working we email and ask for a new one, rather than quietly carrying on without screenshots. Rotate or revoke it whenever you like.
You don't have to migrate to Workover
Most documentation tools want to be where you host your documentation because they benefit from the vendor lock-in. We don’t need to be.
Keep WordPress, keep Webflow, keep the Markdown files in your repo.
If your documentation lives somewhere we do not support yet, tell us.
We will build that integration for you during onboarding and have your assigned human reviewer manually update it until your updated product documentation can be synced from the Workover Editor straight to your platform of choice.
Before you ask
Did we miss something? We’re here to help. Get in touch.
Absolutely. During the first two weeks of your onboarding, someone on our team will work closely with your team to get all systems connected. Until the Workover Editor fully integrates with your platform or setup, we will have your assigned human reviewer update it manually in your system, the same way a human on your team would.
As above, this is not an issue. Just create an account for us as an editor so our human reviewers will have access, and in the meantime, share an API key with us so that we can hook it up directly to the Workover Editor for seamless publishing and updating once the integration is fully tested.
Pull requests are checked as they are merged into your branch of choice. Periodic checks happen behind the scenes based on a mix of customer support themes, and you can always trigger manual verification in your Workover dashboard, or by tagging Workover in Slack to do a manual review or update anything that doesn’t look right (optionally with some quick notes if available).
Depending on the "mode" you select during onboarding, you can opt for slower publication, where nothing is published without manual verification by a human reviewer. Some teams prefer faster publication and retroactive reviews. Though if you ever do spot something out of place and report it onward, this feeds into Workover AI, so it continuously learns your product and writing preferences and style guide.
Workover does not have direct access to your source code. Workover AI reads your repositories directly on your Git provider’s servers (with read-only access, of course), so your code is never sent to our servers.
At this time, we are unable to offer free trials due to the nature of the onboarding process. We spend 20-40 hours working directly with your team in the first month alone to ensure we have a solid foundation and that Workover AI is set to work with your product behind the scenes. This is not something we can sustainably offer to people exploring.
Your documentation is out of date, or you're shipping slower than you could be.
- About ten minutes to connect
- No migration required