Help that stays close to the work.

Start with the outcome.

Tell us what you were trying to do, what happened instead, and where you became stuck. Plain language is welcome. You do not need to diagnose the problem before contacting us.

What to include.

A useful request usually contains:

• The Tooig product or page you were using.
• The approximate time the issue occurred and your time zone.
• The steps that led to the issue and any visible error message.
• Your browser or device type when the issue is visual or interactive.

What not to send.

Never send passwords, one-time codes, private keys, complete payment-card details, or unredacted identity documents by email. We will not ask for them in a support reply.

How requests move.

We acknowledge the request, identify its owner, and ask for only the context needed to investigate. Product incidents and access problems are prioritised by impact. Questions that require engineering or policy review may take longer, but we will keep the next step legible.

Security concerns.

If you believe an account, product, or Tooig system may be at risk, say “security” in the subject line and avoid including exploit details in a public channel. We will move the conversation to an appropriate private path.

Accessibility support.

If a page, interaction, or piece of content is difficult to use with assistive technology, tell us the device, browser, and tool involved. We treat access barriers as product issues, not edge cases.