A dialog that opens on a clear choice: Report a bug ('Something's broken, wrong, or not doing what it should'), Request a feature ('An idea, an improvement, something you wish it did'), or Contact support ('Talk to a person — a question, a problem, anything. Book a call if you'd like one'). Whichever you pick, the report already carries where you were, what was open and the exact URL, and you can attach up to five screenshots and mark them up.
Also called: report a problem · contact support · feedback button · bug widget · help button
- 1Opening the dialog snapshots the context at that instant — before its own overlay mounts
- 2Describe the problem by typing or by talking; attach screenshots by snapping the screen, pasting, dragging, picking a file or pasting a link
- 3Bugs go to /api/bug-reports and land in the platform Bug Reviews inbox with a ticket code; feature requests land in the feature ledger; support requests notify the team, create a task and can book a call
- 4The reporter never gets a 'you submitted a bug' email — the only mail they get about it is 'it's fixed'
When something goes wrong mid-quote, a builder's options used to be an email to whoever they last spoke to, written from memory an hour later, with no screenshot. One button anywhere in the app opens a clear fork — something is broken, I want something added, or I need to talk to a person — because the first two are different work, and lumping them together buried the good ideas at the bottom of the bug queue. Whichever is picked, the screen they were on, the window that was open and a link straight back to it are already attached.
- Problems reported by phone with no record, no screenshot and no context
- Feature ideas dying in text messages
- Support requests with no way to reproduce the issue
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 →