The most useful messages are specific. Include the page you were using, what you expected, and what happened instead.
Good reasons to get in touch
- A factual or cultural correction in a guide or generated result.
- A reproducible problem with a generator, tool, or saved list.
- An accessibility or usability issue.
- A privacy question or request.
- A relevant editorial or product collaboration.
What to include in a bug report
Share the page URL, the approximate time of the issue, your browser and device type, and the steps that produced the problem. A screenshot is helpful when it does not contain private information.
Keep sensitive details out of public messages
X posts and replies may be public. Do not publish API keys, passwords, payment details, private family information, or other confidential material. Start with a brief description and wait for an appropriate private channel when the subject requires one.