Troubleshooting
Get Help with Your Account or Event
Choose the right support channel and send the details that help someone understand your problem.
First created Last updated
Choose the right kind of help
There are two useful ways to ask for help:
| What you need | Where to ask |
|---|---|
| A payment reviewed, a booking corrected, an application explained, or an event rule clarified | The event organizer’s contact channel |
| Help involving account details, a receipt, a private booking link, or a QR code | The private support channel the organizer gives you |
| A broken website button, page, or display | Report a Website Problem |
The website reporter creates a public issue on GitHub, a website where the team tracks bugs. It is not a private customer-support inbox. Do not put personal payment or account details there.
Before contacting anyone
Open your event and the related Transactions or Applications record. Read the latest status and any organizer note. If a submission seemed to fail, check whether a record was saved before submitting or paying again.
Keep the relevant receipt or screenshot privately. You do not need to gather every detail to ask for help, but the steps below make your message easier to understand.
Ask for help, step by step
Step 1: Find the organizer’s contact instructions
Open the event page and look for its contact information or support instructions. Use the channel given for that event.
Use that private channel for receipts and account-specific concerns. If no contact method is clear, explain the event name and the kind of help you need through an available support route without posting private details publicly.
Step 2: Explain the task and where it stopped
State what you wanted to finish and the last action you took. Include the event name, the approximate time, your timezone, and whether you used a phone or computer.
For example: “I was submitting payment proof for the event. I selected the receipt and pressed the submit button at about 8 pm Singapore time. The page showed an error, and my transaction still says submitted.”
That is more useful than “It does not work,” because support can identify the step to investigate.
Step 3: Include the exact message and existing record
Copy the error wording if possible. In a private channel, provide the account you used and the relevant booking or order reference when visible.
If two payments may have been taken, keep both receipts and mention both dates and amounts. Do not send another payment just to see whether the website responds differently.
Step 4: Share only the evidence needed
A screenshot can show the missing button, error, or status. Hide unrelated personal details before sharing it. A receipt should be sent only through the approved private channel.
Never send passwords, one-time sign-in codes, authenticator secrets, recovery codes, or complete card details. Keep full private email, gift, enrollment, and confirmation links private.
Step 5: Follow the reply and recheck the record
The organizer may ask for a clearer receipt, a corrected reference, or another action. Follow that instruction, then check the matching record in Regosite.
A support reply and an updated booking are different things. Look for the final status on your transaction or application before assuming a payment, refund, transfer, or approval is complete.
What to keep while waiting
Keep your original receipt, the record reference, and a copy of the support conversation. Avoid repeating the submission while its outcome is being checked. Event teams can have their own review schedules; the website guide cannot promise a response or payment-review deadline.
For immediate self-help, see Common Problems or the walkthrough for the step you were doing.