Hol tlhIngan Hol

tlh ngoQ: In-product support requests

tlh ngoQ: Use signed-in support requests for account help, content review, workflow bugs, privacy questions, and follow-up conversations that need replies from support inside the product.

tlh ngoQ: This is the best path when you want to track the status of a report or keep all of the replies in one place.

tlh ngoQ: Report buttons on public pages

tlh ngoQ: The flag button on public pages and image galleries opens a prefilled support path for page issues, inappropriate content, feature requests, and misleading or unsafe links.

tlh ngoQ: If you are not signed in, this support page still gives you the official email and phone contact points so you are not dropped straight into a login wall without context.

tlh ngoQ: What to include

tlh ngoQ: Include the exact page URL or path, any related code or image id, what you expected to happen, and whether the issue involved a public page, private workflow, image, or external link.

tlh ngoQ: Do not send passwords, one-time secret reveal screenshots, or private QR values unless support explicitly asks for them.

tlh ngoQ: Link and image review

tlh ngoQ: If an external website looks misleading, unsafe, broken, or no longer appropriate, use this support page or a public-page flag to send the link for review.

tlh ngoQ: If an uploaded image exposes a secret code, child-identifying detail, private address, or other content that should not stay public, report the image from the page where it appears or contact support directly.

tlh ngoQ: Use the right path for the issue

tlh ngoQ: Use documentation pages when you are trying to understand how a workflow is supposed to behave. Use support requests when you need human follow-up, account help, or content review. Use the public report flag when the issue is tied to one specific page, image, or shared item.

tlh ngoQ: That keeps feature questions, privacy concerns, content reports, and workflow bugs from getting mixed together in a single vague message.