Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Support

Contact support

Five ways to reach us. Pick the one that fits the kind of issue you have. All paths land in the same triage queue, so you don't need to use multiple at once.

From the dashboard

Open any workspace and click the floating support tile in the bottom-right (paper-airplane icon). The form pre-fills your org slug, the page you're currently on, and a screenshot slot you can paste into directly with Cmd+V. Tickets here carry full attribution (who, which workspace, current state) so we can debug without back-and-forth.

Email

For non-urgent questions or anything you'd rather not type into a web form:

  • support@trydock.ai — any kind of issue
  • security@trydock.ai — vulnerability reports (PGP key on Security)
  • billing@trydock.ai — invoices, plan changes, payment failures

GitHub

Every dashboard ticket mirrors into our public support repo at github.com/try-dock-ai/support. You can also open issues there directly. Public issues are visible to everyone; flag confidential ones with the privatelabel and we'll handle them out-of-band.

From an agent (REST)

Agents and scripts can file tickets directly via POST /api/support. Authenticated with a Bearer key (API auth). Rate-limited to 10 tickets per hour per org so a runaway agent can't flood the queue.

curl -X POST https://trydock.ai/api/support \
  -H "Authorization: Bearer dk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "bug",
    "title": "Table cell loses focus on paste",
    "body": "Repro: open any table. Paste a multi-line string into a cell. Cell loses focus before paste completes.",
    "url": "https://trydock.ai/vector/launch-plan"
  }'

Five kinds: bug, feature, billing, question, other. Pick the closest one; we don't penalize wrong picks.

From an agent (MCP)

Agents speaking MCP can call the create_support_ticket tool. Same payload, same rate limit, same outcome. Lets your agent file a ticket the moment something breaks without a round-trip through your orchestrator.

{
  "tool": "create_support_ticket",
  "input": {
    "kind": "bug",
    "title": "MCP tool call returned 500",
    "body": "create_row failed for ws_01J... with no message body."
  }
}

Response times

We aim to acknowledge every ticket within one business day. Real fix or workaround timing depends on severity:

  • Site down or data loss: actively triaged 24/7. We'll page on it.
  • Bug blocking your work: same-week fix or a documented workaround.
  • Feature request: read by a human, queued publicly so other users can up-vote.
  • Question: usually answered within a day.
  • System status — check before filing a "Dock is broken" ticket.
  • FAQ — common questions answered.
  • Security — for vulnerability disclosures.