Docs rot
Article freshness
A screenshot or a default changed. The help article is wrong until someone republishes it.
[self-updating help center]
A self-updating help center refreshes articles. Oppulence refreshes the register.
Self-updating help centers watch code and tickets to draft article fixes. Oppulence watches mail, meetings, and CRM so the next owner does not start from folklore.
Free first reportApproval before anything leavesNo invented case studies
[definition]
What “self-updating help center” actually means
A self-updating help center is software that notices when an article went stale and drafts the fix. Ferndesk's agent does that against a product. Oppulence does a different refresh: live notes and a signed-in ledger that pick up new promises, objections, and silence.
Three jobs that are not the same.
Commitments rot
Promise freshness
A date was conceded on a Friday call. The CRM still says healthy. That is the Oppulence problem.
Desktop vault
Live notes
A local Markdown page that can refresh from a schedule or a matching event. Not a public help center.
[for]
This page is for you if
- You already write promises in mail, Slack, and calls, and they disappear.
- You want a register with sources, not another place to type notes.
- Customer-facing sends should wait for a person.
[not for]
This is the wrong page if
- You need a public help center, article CMS, or ticketing inbox. That is a different product.
- You want a bot that sends as you without approval.
- You want a wall of logos and invented time-saved numbers. We will not publish those.
Questions this URL actually answers
The leftover slug is a search path. The answers stay honest about the product.
A help center whose articles are checked against the product and drafted back to you. Nothing should publish without a person.
