Support
Something not behaving? Write to us. We are a small team, we read everything, and we would rather hear about a rough edge than have you work around it.
Where to write
We reply on working days, usually within one business day and always within three. If your whole team is blocked, put BLOCKED in the subject line and we will pick it up first.
What to include
You are all bug reporting professionals here, so you know the drill — but for the record, the fastest tickets to resolve contain:
- The project name, and the email you sign in with.
- What you expected to happen, and what happened instead.
- Roughly when it happened, with a timezone — that is what we search the logs by.
- The destination involved, if it is a publishing problem: which spreadsheet, which channel.
- A screenshot of the board or the error, if there was one on screen.
Common questions
Service interruptions
Reports sent from a build are accepted first and processed after, so a brief interruption does not lose them. If publishing to a destination fails, the report stays on the board and can be published again once the connection is restored. When something larger is wrong we email workspace owners rather than making you guess.
Privacy and data requests
Export, correction and deletion requests are handled by email and answered within 30 days. The full detail of what we store and for how long is on the privacy page.