# Human support > When a developer hits something AI can't fix, a human can step in and answer the question. Every answer becomes part of the context, and makes the next question easier! Source: https://www.restless.ai/human-support ## Features - A human support inbox that any of your developers can escalate to if they're not getting the answers they need. - You have access to the user's API, MCP, and support history to help debug with them. - All answers are added to the product's context, so future similar questions can be answered easily. ## When AI isn't sure, a human takes over APIs fail in ways a chatbot can't always untangle. When a developer hits one, Restless hands the full thread, with their context attached, to someone on your team who can. 1. **AI answers most tickets** — Restless resolves the majority of questions on its own, from your docs, your API, and past answers. 2. **Escalate to a human** — When it can't, the developer reaches your team in one click, with the full thread and their context attached. 3. **Answers compound** — The key parts of every human answer become reusable context, which powers your docs, AI agent, MCP server and more. What you can see: Docs, Agent, MCP. ## One inbox for every conversation AI and human replies, the developer's live logs, and full context all live in the same thread. ## Keep your developers moving forward Restless does its best to answer questions without any human intervention. When users have a question we don't have answers to, though, we make it easy for them to escalate to you. ### See what they see Their live API calls, MCP activity, and past tickets load with the thread, so you debug from the same view they have. ### Reply from Slack Answer developer questions without leaving Slack. Threads sync back to Restless automatically. ### Realtime logs at your side See the developer's actual requests, responses, and errors while you help, so there's nothing to reproduce. ### Draft replies with AI Restless drafts an answer from the user's context and past support history. Review, tweak, and send. ### Every answer becomes context Resolved answers feed the product's context, so the next time someone asks the same thing, it's already answered. ## Related features - [MCP Server](https://www.restless.ai/mcp-server) — Give agents native access to your API, no docs required. - [Agent Recovery](https://www.restless.ai/agent-recovery) — When an agent hits an error, the response tells it how to fix it. - [Workbench](https://www.restless.ai/workbench) — Filter your logs and replay any request to see exactly what failed. ## Setup Setup is a breeze. Restless is tightly integrated with your API, so we install a small SDK. Don't worry, we walk you through every step of the way. Run this in your API's repo: ```sh npx restless init ``` Or hand the setup to your coding agent with this prompt: ```text Set up Restless in this repo by running `npx restless init` and following the steps. ``` To try it on a demo API instead: ```sh git clone git@github.com:restlesshq/demo.git && cd demo && npx restless init ``` Nothing is uploaded without your permission. The CLI runs four steps: 1. **Map out APIs.** Locate your APIs, generate an OpenAPI (OAS) file, and write it to `.restless/`. An OAS file is the shape of your API: every endpoint, parameter, and response. Later steps use it to install the right adapter and wire up the middleware exactly. The scan points Claude Code, running locally on your machine, at your codebase to find your routes. Commit the `.restless/` folder along with your code; it's meant to live there. 2. **Install SDK.** The CLI detects the project runtime, selects its adapter, installs the Restless SDK and wires the request middleware. 3. **Test your setup.** Local traffic capture starts, and the CLI confirms requests are reaching Restless. 4. **Set up account.** Log in to claim your project on Restless. Privacy: scanning runs entirely on your machine via your own Claude Code install. We don't see a single line of your code, and nothing gets sent to our servers at that step. ## More from Restless - [Restless](https://www.restless.ai/index.md): Restless makes your API self-improving. Every API call, support question, and error leaves it better for the next request. - [Features](https://www.restless.ai/features.md): A new surface for your API: a public, LLM-first hub that gets every caller started and keeps them moving. - [Documentation](https://www.restless.ai/documentation.md): Restless generates your API documentation from your endpoints and the tools your team already uses, and keeps it current every time your API changes. - [Getting Started](https://www.restless.ai/getting-started.md): Onboarding is the most important part of your developer experience. Restless makes it easy for your developers to get their agent set up and ready to build. - [Agentic docs](https://www.restless.ai/agentic-docs.md): Restless isn't just agent-friendly docs. It's the only documentation platform built AI-first. There's a UI for humans, but the docs are shaped to make agents successful. - [Workbench](https://www.restless.ai/workbench.md): The Workbench sits at the bottom of your docs and gives developers a view into everything that's happening: view and filter logs, see what went wrong, and fix issues. - [Agent recovery](https://www.restless.ai/agent-recovery.md): When an agent hits an error on your API, it usually gives up and you never hear about it. Restless catches the failed call and tells the agent how to fix its request and retry. - [API Logs](https://www.restless.ai/logs.md): Your API is now how your users use your product. Restless brings every request into one place, so you can see which endpoints get hit, which calls fail, and where people give up. - [MCP server](https://www.restless.ai/mcp-server.md): Give agents the ability to do more than just write code. Give them access to do everything they need to build on your product, such as reading docs, debugging API calls and updating settings. - [AI Traffic](https://www.restless.ai/ai-traffic.md): Your API and docs get a lot of AI traffic now, and most of it is invisible. Restless shows you what AI is actually looking for, broken down by who is asking. - [Self-updating docs](https://www.restless.ai/self-updating-docs.md): Restless reads resolved support conversations, pulls out the part that applies to everyone, and drops it in an inbox to review. Approve it and it becomes context the next person finds on their own. - [Solicit feedback](https://www.restless.ai/solicit-feedback.md): When an agent hits something confusing in your API, it usually just gives up. Restless adds a send_feedback tool to your MCP server, so the agent can tell you what tripped it up. - [Sign up](https://app.restless.ai/signup)