tlh ngoQ: Support requests work best when they identify the page, the related code or image, and the type of problem without exposing private secrets that should never have been copied into a ticket.
tlh ngoQ: When a request is specific, support can move faster and you do not have to resend the same page path, code, or explanation over and over.
michael.kappel@Geotrackable.com
(630)362-7576
tlh ngoQ: Use the support page first for the official email, phone, address, and guidance on when to use a threaded support request instead of a public report flag.
QaHtlh ngoQ: Use the image and external-link documentation when the question is about how shared media or websites are verified, displayed, or reported.
tlh ngoQ: About External Linkstlh ngoQ: Use the legal pages when the question is about data handling, moderation expectations, export or deletion behavior, or the responsibilities that come with public content.
pegh policytlh ngoQ: Use signed-in support requests when you need back-and-forth replies, status updates, or review history that stays attached to one issue inside Geotrackable.
tlh ngoQ: The report flag on public pages and image galleries can send you into support with the page path, related reference, and suggested subject already filled in.
tlh ngoQ: The owned support page is the best starting point when you are not signed in yet, need the official contact details, or want to decide between docs, legal pages, and support tickets.
tlh ngoQ: Passwords, one-time reveal screenshots, private QR values, and other secret access details should stay out of normal support messages unless support specifically asks for them.
tlh ngoQ: Name the exact page or page section, whether the issue involved a public code, secret code, image, link, team, or location, and the last step that worked before the issue started.
tlh ngoQ: If the issue came from a public report flag, keep the prefilled page path and reference when you open the support request so support can inspect the exact content item faster.
