Knowledge base pages

Pages in Tettra hold documented answers, processes, and policies for a team. A Beam agent reads existing pages to answer a teammate question, and where the connector and permissions allow it, drafts or edits a page when a process changes. It applies your rule for which categories it may touch and tags an owner for approval. Straightforward wording fixes go through on their own. New policy pages, or edits that change meaning rather than phrasing, are held for a human owner to review and publish so nothing sensitive ships unchecked.

Team Q&A requests

Tettra lets teammates ask questions that route to a subject owner. A Beam agent picks up an incoming question, searches existing pages, and replies with the documented answer when one clearly exists. It applies your rule for confidence, citing the source page so the asker can verify it. Questions with no good match, or ones touching pay, legal, or security topics, are passed to the assigned human owner instead. The agent can also note recurring questions that have no page yet, so the team knows what to document next.

Content freshness checks

Knowledge goes stale, so Tettra flags pages for periodic verification. A Beam agent reads page age and last-verified dates, applies your staleness rule, and alerts the owner when a page is due for a look. Where a linked process has visibly changed, it can draft a suggested edit for review rather than overwriting the page. Pages it judges current are marked without fuss. Anything that reads as outdated but carries compliance or onboarding weight is escalated to a human owner, who decides whether to archive, rewrite, or keep it.