Who this helps: Visitors and app users
Bring: Page URL, browser/device and a short description without private content.
Follow the workflow
- For a how-to question, check the Help pages first.
- For a correction, include the public page and the claim or broken link.
- For an app problem, describe the action and visible error. Do not email passwords, API keys, database strings or private recordings.
Worked example · illustrative, not a reported result
Useful report: “On the script-duration page in mobile Chrome, changing WPM to 150 did not update the estimate.” Include whether the issue repeats after a fresh page, but never reload a page holding your only recording just to test.
Before you move on
- No secrets included.
- Public URL supplied.
- Expected and actual behavior separated.
Common problem and recovery
Email [email protected]. This opens your email app; the website does not submit a support ticket or promise a response time.
Build Then Post editorial workflow · prepared September 27, 2026. Examples are illustrative unless explicitly identified otherwise.