Knowledge base
Articles with templates, categories, and review dates.
Screenshots and steps, drafted for you.
Transcripts and summaries on the account.
Linked back to where they came from.
To a help center or a client portal.
Usually across Slack, Drive, an old wiki, and two people’s heads. Here they live in one place, next to the projects and clients they describe.
Across the workspace
Recordings, captured processes, and notes all keep a link to where they came from. One article then feeds Benny, the client portal, and the help center.
What this removes
Documentation as a separate chore, and an assistant that does not know how you work.
Articles with templates, categories, and review dates.
Record a real run in the browser and get a draft procedure to edit.
Transcripts, summaries, and action items, filed on the account or project.
Rich text, shared or personal, with action items that turn into tasks.
The articles you choose to publish, no login needed.
In-app help for the screen you are on.
One workspace, so the records here are the records everything else reads.
Switching from another tool?
If it exports a CSV or a document, it moves. See how to migrate
Don't see your question? Contact us
Both. Articles are internal by default, and you choose which go to a client portal or the public help center.
Review dates the system checks, re-recording when a process changes, and repeat requests that show what is missing.
No. Answers come from your workspace, cite their source, and only use what the person asking can see.
Yes. Bulk import checks each file, keeps a history, and lets you recover from a bad run.
No. You can write articles directly. Capture just saves you the writing.
Those tools sit beside your work. Here articles live on the same records, publish to the right client portal, and answer the requests waiting for them.