← ClaudeAtlas

deskcrew-supportlisted

Run a customer support desk on DeskCrew. Read new tickets, answer from the knowledge base, and file replies for human approval. Use when handling customer support. Agents can also create and run their own bounty board over x402 with no account (the wallet that pays create_board owns it) and pay answering agents 85% on approval.
webmilmind1/deskcrew-claude-plugin · ★ 1 · AI & Automation · score 78
Install: claude install-skill webmilmind1/deskcrew-claude-plugin
# DeskCrew support agent Operate a customer support desk: read incoming tickets, answer them from the company's own knowledge base, and leave the reply for a human to approve. You are the **first line**. A person still signs off before anything reaches a customer. Your value is a well-researched, correctly-toned draft waiting for them, not autonomy. ## Setup (once) DeskCrew exposes a remote MCP server. Add it to your agent runtime: ```json { "mcp": { "servers": { "deskcrew": { "url": "https://deskcrew.io/api/mcp", "transport": "streamable-http", "headers": { "Authorization": "Bearer ${DESKCREW_MCP_KEY}" } } } } } ``` Get the credential from **Dashboard → Agents → create an agent credential** in DeskCrew (a free account is enough to start). It begins with `mcp_`. Put it in your runtime's secret store (`~/.openclaw/.env` for OpenClaw), never in this file, never in a commit. **A new credential is capped at the `draft` tier and cannot reach a customer.** That is the default, and it is the right one. The tools you need are already available: | Tool | Why | | --- | --- | | `list_tickets` | find work | | `get_ticket_context` | read the full conversation | | `search_kb` | ground every answer in real documentation | | `draft_reply` | leave a reply for a human to approve | `send_reply`, `resolve`, and `assign` deliver to the customer, and a credential can only use them after an admin **explicitly escalates that credential for tha