Contact & support
How to get help, report bugs, and reach a human at Inboard.
We want you live, not stuck. Here's how to get the right kind of help quickly.
Before you reach out
Most issues have a fast self-serve fix:
- Common issues — the problems integrators hit most, with checklists.
- FAQ — short answers to the questions we get most often.
- API reference — exact endpoints, error codes, and rate limits.
If you found the answer there, you're done — no ticket needed.
Getting help
| Channel | Use it for | Where |
|---|---|---|
| Support email | Account questions, billing, "how do I…", bug reports | support@inboard.dev |
| In-dashboard help | The same docs and a contact link, one click from any screen | Help menu, top-right of the dashboard |
| Status page | Checking whether an outage is on our side | status.inboard.dev |
We aim to respond to support email within one business day.
Reporting a bug
The more we can reproduce, the faster we fix. Please include:
- What you expected versus what happened.
- The
requestIdfrom any failing API response (every error returns one — see Errors). - The embed key and, if relevant, the platform and locale in use.
- A minimal HTML snippet or URL where the issue reproduces.
Reporting a security issue
Please don't open a public issue or email general support for vulnerabilities. Email security@inboard.dev with reproduction steps — see our security policy and the Security page for scope, safe-harbour, and acknowledgements.
Feature requests
Tell us what would make Inboard fit your install flow better. Email support with [Feature] in the subject, or raise it from the dashboard Help menu. We read every one and use them to prioritise the roadmap.