Channels
Email support
hello@getsly.ai — integration questions, account issues, anything with a request ID.Docs GitHub
Open an issue for docs errors, typos, or missing content.
Dashboard chat
Intercom chat inside the dashboard, bottom-right. Fastest for account-specific issues.
Status
Platform status + incident history. Public status page coming soon.
What to include in a support ticket
We resolve tickets ~10x faster when they include the full context upfront. Include:request_idfrom the failing response (every error carries one)- Environment —
testorlive - Endpoint and method —
POST /v1/transfersetc. - Exact time range of the issue (UTC, ISO 8601 preferred)
- Your tenant ID — from
GET /v1/context - Reproduction steps — ideally a curl command that fails
- What you expected vs. what happened
Severity and response times
| Severity | Definition | First response | Resolution target |
|---|---|---|---|
| 1 | Production down, money at risk | <30 min | <4 hours |
| 2 | Production degraded, some flows failing | <2 hours | <1 business day |
| 3 | Non-blocking bug, workaround exists | <1 business day | <1 week |
| 4 | Feature request, general question | <3 business days | — |
Paid support plans
Enterprise plans include:- Dedicated Slack Connect channel
- Named customer success engineer
- 24/7 on-call phone escalation
- Custom SLA on top of the table above
Agentic support (Intercom Fin)
The dashboard includes an AI support agent that can answer common integration questions, fetch recent errors for your tenant, and escalate to humans when it’s stumped. For quick “where do I find X?” questions, try it first — it’s faster than a ticket.Security disclosures
Found a security issue? Do not open a public GitHub issue. Emailsecurity@getsly.ai with details. We respond within 24 hours and follow a coordinated disclosure process.
Bug bounty
Sly runs a private bug bounty program. Once you report a valid issue via security@, you’ll receive an invitation with scope and reward tiers.Feedback
If this documentation is missing something, unclear, or wrong, open a GitHub issue or Slack us in#docs-feedback. Documentation debt is real debt; we treat doc bugs as P2.