A single Help & feedback dialog opens from the left nav on desktop, a header button on mobile, and a floating button that sits above every modal. It takes a description (typed or dictated), screenshots (pasted, uploaded or annotated), and files the report with the context already attached. Reports land in the platform's Bug Reviews inbox and email the platform owners immediately.
Also called: report a problem · bug report · feature request · contact support · something is broken
- 1Any surface can open the dialog by dispatching one window event
- 2At open time it captures the active view label, the exact URL, the open dialog's heading and the canonical module id
- 3Screenshots arrive as data URLs (paste, upload, camera roll) or hosted links; data URLs are uploaded to a storage bucket so the row stores only URLs, capped at five images
- 4Submit stamps org and user server-side — the client cannot spoof identity
- 5The reporter's ticket gets a short code, and the platform owners are emailed straight away
'It's broken' is what a builder types with one hand from a jobsite, and it is not enough for anyone to fix anything — no screen, no record, no idea which of the day's forty numbers was wrong. Asking him to write a proper report instead means the report never gets filed. One button anywhere in the app opens one form that takes a sentence, a screenshot and a voice note, and captures the rest by itself. It is deliberately one door for three things — something broken, something missing, or needing a person — because whoever just hit a wall does not know or care which category his problem belongs in.
- Reports arrive without enough context to reproduce anything
- Users abandon a report rather than describe it in writing
- Bugs, feature requests and support questions get lost in three different channels
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →