Serva discovers how your company works, who decides what, and why, and keeps it current so people and agents work from the same version.
Agents can read your files. They can't tell what's still valid, who approved it, or what it contradicts.
Questions that keep coming back
What docs and wikis still say
wiki · outdated
Ask Maria how refunds work.
Departments, people and processes as one connected map you can navigate, or read as a list.
Authority by department and impact: the big changes reach you, the rest you can delegate.
Open any step or rule and see where it came from: a conversation, or the person who defined it.
Every change adds a version, with who approved it and why. Go back to any date.
In March it was a no. Today someone proposes a yes. Serva shows both, with who said it and how much authority they have. Saying something ten times doesn't make it true.
Approve a change as a pilot, with an end date. When it ends, you decide whether to keep it or go back.
Conversations, roles, teams, or how you describe the company today, Serva turns that into a first draft of people, departments and processes. You confirm and correct; nothing goes live without you.
Org draft
POST /v1/org/draftReading your sources…
Discoveries, process changes and agent questions land in one place. Serva recommends; a human with authority approves or rejects. Closed items stay on the record.
Inbox
GET /v1/inboxLoading proposals…
Navigate departments, processes, people and rules as one graph, or as lists. Every change adds a version; nothing is silently overwritten. Follow any fact back to the conversation in Audeo when that is where it came from.
Process versions
GET /v1/processes/{id}/historyShorter escalation window for enterprise accounts.
Authority
M. Okonkwo
Suggestion from a call…
Before a task, an agent can check Serva once: allowed and how, human step required, or not allowed and why. The same model is available by API or MCP, no screen required. Your team still does the work; Serva holds the rules and the log.
Agent preflight
GET /v1/policy/checkTask
Refund · order #4821
Question to Serva
Allowed, and how?
Yes, follow process
Checking policy…
Every step of how an order gets done, written from what the team actually says and does.
Whoever takes over an account already knows its history, instead of starting from zero.
The fix that worked last time is written down, not stuck in one person's head.
Someone joining reads how things are done on day one, instead of asking around for weeks.
We also make Audeo, Mitto, Fabra. They all share one credit balance: having another product costs nothing until you use it.
Tell us how your company works today and how you'd want to get started with Serva.