IntakeAnyone files from Claude or ChatGPT, in a real conversation.The board and DocsEvery request with its brief, size, worth and seat, and the specs and decisions beside it.Smart routingThe best seat and the best model for every request.The recordEstimate against actual, signed. Better with every row.ConnectionsClaude, ChatGPT, Claude Code, Codex, GitHub, Slack and more.
Business teamsSales, success, ops: send the customer's request and hear when it lands.Product teamsSpecs and prototypes that arrive ready to build, and a say in what runs.EngineeringThe right work, on the right seat and model. For engineers and leads.
Docs and helpEvery verb, every surface.Developerscurl -fsSL sleds.ai/install | shTrustWhat we keep, and the exceptions.ManifestoWhat we are doing, and why.Claude connectormcp.sleds.ai/mcpSelf-hostThe record in your cloud, on your keys.ContactTalk to the people building it.
Request an inviteSign in
sleds/Use cases/Support teams
Intake world · support files
support teams · help desk · customer success · on-call

File the bug from the ticket. Tell the customer when it's fixed.

You see the bug first, with the screenshot, the error and the customer's name on it. Now you file it to engineering from the chat you already have open, in one message. Your AI reads the evidence, asks what engineering would, sizes it, and routes it. When it lands, the receipt comes back to your thread, ready to forward.

Request an inviteHow intake works
claude · Marcus, support · sleds connectorno seat needed
MarcusTicket #8841: Acme can't export invoices over 10k rows, times out every time. Third customer this week. Screenshot and the error from their console.
export-timeout.pngconsole.txt
sledsThe error is the 30-second limit in the export job. It touches api › exports and the worker queue; ENG-479 in that area is open and not the same fix. Is anyone blocked today, and does Acme have a date?
Acme's finance close is the 31st. The other two can wait a week.
sledsOn the board as ENG-503 · M · $6–14 · 30–70 min · worth high, three accounts, due the 31st. Routed to Dana on Sonnet 5 for tonight. I'll tell you here when it lands.
sleds · oct 3 · 06:20ENG-503 landed. Large exports run in the background and email a link. Actual $5.80 · 44 min. Receipt is on the row; #8841 can close.
what changes

From "escalated to engineering" to a fix with a receipt.

beforeA ticket copied into a tracker

Retyped by hand, missing the console output, filed under a component nobody owns.

with sledsOne message, evidence attached

The screenshot, the error and the customer's name travel with it. Your AI reads them and asks only what is missing.

before"Is this a known issue?"

You search the tracker, then Slack, then ask. Three customers report the same thing as three tickets.

with sledsIt knows what it touches

Intake reads the product map and says what is already open in that area. The third report joins the first and raises its demand.

before"Any ETA I can give them?"

Nobody knows, because nobody sized it.

with sledsA band you can repeat to the customer

Sized before anyone starts, from how long that kind of fix took here before. Ask "where is ENG-503?" and get the answer in the same chat.

bugs, not only features

Built for the shape of a bug report.

A bug arrives with evidence and a customer, not a spec. Intake treats it that way: it reads the error before asking anything, it asks who is blocked and by when instead of what done looks like, and it marks the worth by the accounts waiting, so a fix for three customers routes ahead of a nice-to-have. Repeat reports join the open item rather than filing a fourth.

ENG-503 · filed from supportready
requestLarge exports time out over 10k rows
evidenceexport-timeout.png console.txt · from #8841
touchesapi › exports · worker queue · ENG-479 nearby, not the same fix
waitingAcme · finance close Oct 31 · 2 more accounts
worthhigh · 3 accounts · Marcus
sizeM · $6–14 · 30–70 min · 78%
what you get

Free for the whole support team, forever.

No seat

A member of the workspace is enough to file, answer and check status. Seats are for the people who build.

From the tool you are in

Claude, ChatGPT or Cowork, and a Slack DM for the questions that come back. Nothing new to open.

One question, not a thread

When the engineer needs something, it lands in your chat. Reply with a word and it goes on the item.

A receipt to forward

What changed, when, what it cost. Close the ticket with it.

invite only

File the next bug from the ticket.

Request an invite. Every support rep can file from day one, with no seat.

We'll only use it to reach you about sleds.
connectorhttps://mcp.sleds.ai/mcp