Contact support

Best use

Use contact for payment, trust, and result issues

The contact page is designed for real support needs, not as a dead-end form page. It is the public route for trust questions, corrections, and payment-credit issues.

• +Missing credit after a verified payment
• +A result that feels misleading or unclear
• +Trust, privacy, methodology, or legal-page corrections
• +General support and product feedback

Safe contact

Send the minimum useful context

Support works best when users share only the specific page, issue, and relevant evidence needed for review rather than forwarding unnecessary personal or financial data.

• +Include the page or scan link when possible
• +Do not send extra identity documents unless absolutely required
• +For payment issues, include only the useful payment reference details

Expectation

The page sets a visible support expectation

Clear response expectations improve trust because users know what channel to use, when the team is available, and what kind of help the product can realistically provide today.

• +Support hours: Mon-Sat, 10:00-18:00 IST
• +Response target: Usually within 1 business day
• +Review owner: OfferGuard AI research and review desk

Missing starter credits after checkout

A user completed payment but wants confirmation that credits were actually applied. Support can inspect the verified payment state more reliably than the client checkout message alone.

Next step: Share the payment reference and plan used, but avoid sending unnecessary personal details.

Question about a high-risk result

A user wants to understand why a verdict moved high-risk. The most useful support request includes the exact suspicious lines, the page used, and the smallest useful context around the evidence.

Next step: Send the relevant lines or screenshot context instead of a full unrelated document bundle.

Trust or content correction request

A user notices an issue on a trust page or wants to challenge a public claim. The site exposes a correction path instead of forcing users to rely on hidden channels.

Next step: Email the exact page and correction request through the public support path.