# Product: one agent, four paths

> Peeve reads your live interface, picks how to resolve each question in ~150ms, and acts: for humans as motion, for their agents as tools.

Canonical: https://peeve.ai/product/

Peeve reads your live interface, decides how to resolve each question, and acts: for humans as motion, for their agents as tools. One capability registry feeds every surface; one measurement loop keeps them true.

Platform: The Brain (self-healing knowledge), Agent channel (typed MCP tools), Voice (spoken narration), Analytics (real intent + stuck-points), Connectors (your backend + helpdesk), Security (what Peeve never sees).


## More questions

### What can Peeve do?

Peeve answers with a source, shows users how by moving through your live interface, does backend actions after confirming the effect (Growth and above), and hands off to a human with the full session. It reads your live interface and picks the lowest rung that resolves the question in about 150 milliseconds.

### What is agentic customer support?

Agentic customer support means the AI plans steps, calls your tools or APIs, and completes the task, rather than just returning text. Peeve is agentic in a specific way: it reads your live interface, picks how to resolve each question in about 150 milliseconds, and acts, showing a human with cursor motion and serving an AI agent the same capability as a typed tool.

### What is the difference between a support copilot and an autonomous AI agent?

A copilot assists a human agent, while an autonomous agent resolves for the customer directly. Peeve is customer-facing and resolves in-product, but with guardrails: it stays read-only until you grant capabilities, confirms every action, and hands off to a human when confidence is low, so autonomy is bounded rather than blind.

### Can AI support handle multi-step or complex requests?

It can when it chains actions across your systems instead of answering one message at a time. Peeve climbs a ladder of four paths (answer, show, do, escalate) and can combine live lookups and confirmed write-actions in one conversation, for example reading an order status and then issuing a refund, each step confirmed and logged.

### Can AI support pull live data from my systems to answer a question?

Yes, if it is connected to your backend rather than a stale snapshot. Peeve calls your read endpoints live during a conversation to answer with current account state, and calls write endpoints, with confirmation, to change something. You connect it by pasting your API docs or an MCP server; the model never sees your credentials.

### How does an AI agent decide whether to answer, show, or take an action?

The good ones route by confidence and by what the question needs. Peeve decides the rung in about 150 milliseconds and never climbs past what is safe: it answers a fact, shows a place, does a backend action after confirming the effect, or escalates. When it is unsure between showing and doing, it shows.