For SaaS
Help that livesinside your product.
Product questions are specific: versions, limits, error codes. Kuvra answers them from the docs your team already writes, in a widget that looks like part of your app.
Product vocabulary
Error codes aren't a vibe
Customers paste error codes, flag names and endpoints. A meaning-only search drifts on those, so Kuvra runs a keyword search alongside it and merges the two.
The question
Sharing gives my client ERR_SHARE_403. What does that mean?
- 1Sharing dashboardsdocs/sharing/dashboards.md0.82
- 2Inviting guestsdocs/sharing/guests.md0.79
- 3Share error codesdocs/errors/sharing.md0.77
- 4Public linksdocs/sharing/public-links.md0.71
- 5Workspace settingsdocs/admin/settings.md0.58
Close in meaning, but the page with the code is buried.
Illustrative scores for a fictional help center.
The full pipeline is on the AI agent page
Docs as code
Your docs ship with your releases
Point Kuvra at the docs folder in your repo and re-sync on a schedule. Each release's doc changes reach the agent, and nothing else is re-processed.
01
You ship v2.4
The release adds scheduled exports. The docs change in the same pull request.
+ docs/exports/scheduled.mdx
~ docs/exports/overview.md
02
Kuvra re-syncs
On your schedule, say every night at 3am, the repo is read again.
orbit/docs · main · docs/
03
Only changes re-embed
Files that didn't change are skipped. The two that did are updated and re-embedded.
2 updated141 skipped04
The agent knows
The next customer who asks about scheduled exports gets the new answer.
Yes: open Exports → Schedule and pick daily or weekly.
Engineering in the loop
Bugs belong in your tracker
When a conversation turns out to be a real defect, create the Linear issue from the conversation itself, with the details filled in. Tell the right Slack channel in the same breath.
- Actions run from the conversation
- Connected once per workspace, by an admin
- The AI hands over when it can't answer
Create Linear issue
Issue created in Linear
Send Slack message
Posted to #eng-escalations
Headless
Or build help into your own UI
A hint under a settings field, answers in your command bar, a help panel in your own design. The Agent API answers from the same knowledge base, with the same handoff to your team.
See it in action// On your server: in-app help for a settings field const res = await fetch(`${KUVRA_API}/api/v1/agent/answer`, { method: 'POST', headers: { Authorization: `Bearer ${process.env.KUVRA_API_KEY}` }, body: JSON.stringify({ question, stream: true }), })
Questions from SaaS teams
Yes. Import the Markdown and MDX from your repo, choose the branch and folders, and re-sync on a schedule so each release's doc changes reach the agent. Private repos work with a read-only token.
Still curious? Email hello@kuvra.dev