Support is email-based. Each workspace has its own support address — workspace owners configure the one used in platform emails in instance settings; the one shown in the mobile app is set per app build.
Finding the support address
- Mobile app — open the Support screen. It shows the support address along with an instance identifier worth quoting in your message.
- Email footers — every email the platform sends (invitations, password resets, notifications) includes the support address in the footer.
If your workspace hasn't configured a support address yet, ask your workspace owner — it's a field in instance settings.
What to include
The more of this you include up front, the more likely the first reply resolves the issue:
- Workspace identifier — shown on the Support screen in the mobile app. It routes your ticket to the right workspace without a back-and-forth.
- What you were doing — the form or record name, and the screen you were on (dashboard or mobile).
- When it happened — a timestamp, as precise as you have. "Around 9:30 AM Tuesday" beats "recently".
- For API issues — the
request_idfrom the failed response (also in theX-Request-Idheader). It joins your request to our logs directly. The endpoint and HTTP status help too. - Screenshots — of the error or the unexpected state, if you can capture one.
Before writing, it's worth a pass through the FAQ and common errors — several frequent issues have a self-serve fix.
What to expect
A reply by email. We don't publish response-time guarantees, and we won't pretend to a queue position we can't see — but tickets with a workspace identifier, a timestamp, and a request_id consistently resolve faster because nobody has to ask for them.
As support grows
Email is the support channel today. This page will grow as more channels come online.