The platform behind our answer-system engagements

Savanto Desk

An assistant that knows what your business knows, and can act on the systems it runs. Your indexed content, your systems of record, and capabilities you define yourself. Reach it as search, as chat, through the API, or as tools for the agents your team already uses.


The index

Most tools stop at what you have published. The questions that matter usually need both halves: the catalog page and the order record, the policy document andthe customer’s entitlement. Desk indexes your content, connects to your systems of record, and answers from both.

“Where’s my order?”ORDER MGMT
“Is this covered?”POLICY ADMIN
“Does this fit my model?”CATALOG · COMPAT MATRIX
“What’s my price?”ERP · CONTRACTS

Five ways in

One system, reached five ways. Bundled assistants give you a single surface, over content the platform already owns.

Search

Pulled

Semantic search over the same index, so a visitor typing “waterproof but breathable” finds what a keyword search would miss.

Assistant

Conversational

Answers in context, on your site or inside your own applications, including the questions that need a lookup rather than a document.

Recommendations

Pushed

The same knowledge offered before it is asked for: the compatible part, the related policy, the next sensible step.

API

In your own applications

A REST API over the same system, so your team can embed search, answers, and capabilities inside the applications your staff and customers already use.

Agents

Model Context Protocol

Desk reachable by Claude, ChatGPT, or your own internal agents, through a hosted MCP server with your authentication. Almost nobody offers this yet.

MCP & API documentation →


Capabilities you define

When the answer isn’t written down anywhere.

Some questions have no document behind them. “Has my order shipped” is answered by your order system, not by a page. “Am I still under warranty” is a record, not an article.

So Desk lets you add custom agents of your own. Describe what one should do in plain English, point it at a system you already run: your own API, or an MCP server you expose. The assistant can then do it, scoped to who is asking, without waiting on a release from us. The systems you connect stay yours: we call them, we do not copy them.

Custom agents, described in English
You write what the capability should do, in your own words: "look up order status and tracking from our store", or "check availability on a departure date". We draft the configuration from that for your review, and each one becomes a domain the assistant can route to.
Internal system access
Order management, policy administration, booking, ERP, or anything else behind your login. Connected over your own APIs or an MCP server you expose, called with your credentials and scoped to who is asking.
Reachable however you need it
Every capability you add is available across all five surfaces at once: the widgets, the REST API, and your MCP clients. You build it once, not three times.
Governed like everything else
Each capability is scoped, tested against real questions, and turned on deliberately. Nothing goes live because it happened to work once.

Why the answers hold up

Real questions rarely have one source. “Does this fit my model, and what would it cost me?” is two questions wearing one coat, and a system that retrieves once returns half an answer confidently.

Desk splits a question into its parts, retrieves against each, and reconciles the results before it answers. Where it can’t support a claim from your sources, it says so rather than inventing one. A confident wrong answer costs more than no answer.


Where it runs
Where it runs today
A managed deployment on our AWS cloud, in your own isolated tenant. Your own cloud account, where an engagement calls for it, is scoped and proven as part of the work.
Your approved providers
OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, or self-hosted open-weight models if nothing may leave your network. Your vendor list decides, not ours.
Your identity
Answers scoped to who is asking, through your existing authentication.
No training on your data
Contractually, in writing, in the DPA.

Security & deployment detail →


Before we ever meet

You’ll see it running on your own content in the first call.

We index your public content before we speak. The first meeting isn’t a demo of someone else’s data. It’s your catalog, your policies, your documentation, answering the questions your customers and staff actually ask.


See it on your content.

Tell us your domain and one question your customers keep asking. That is enough for us to show you something real.

Talk to us