Troubleshooting and support

Email [email protected] for membership, application, payment or billing help, or if you cannot sign in. You do not need to regain account access before contacting the team.

For a platform problem while signed in, use Report an issue below. Describe what you were trying to do, what happened instead and the affected page. Include the exact error or a screenshot with private information hidden.

Already contacted us? Reply in the same thread with what remains unresolved, its impact and any relevant deadline. Ask for the specific update you need, such as a payment check or an access review.

For arrival or joining details on event day, open the host's card on the event page and use Message the host, or Call the host where the host has added a number. For a partner's billing or redemption decision, use the partner support route in the offer. Never send passwords, OTPs, API keys or full card details.

If you cannot sign in, use the phone number linked to your existing GrowthX account, with the correct country code. Follow the sign-in steps and use the latest OTP, or your existing password. If the code is missing, check the delivery destination shown on that screen.

If sign-in works but you keep getting logged out, save any unfinished work before refreshing or restarting. Note whether it happens on the app, website or both, and whether it follows a particular action.

Email [email protected] with your account email, device, app or browser version, approximate time and time zone, and the exact error. Say whether you never reached your account or reached it and then lost access. If another device is still signed in, you can use Report an issue there.

Do not create a second account to work around the problem. Never include your OTP or password in the report.

Do not pay again to unlock the same purchase. Check that you are signed in to the account used to buy it and compare the locked item with the product named in your purchase confirmation. Membership and a standalone programme can include different access.

For membership access, check Settings → Membership (Subscription on mobile). For a programme or event, open that purchased item's page. Refresh once after confirming the account.

If it is still locked, email [email protected] with:

• Your account email and the product or event purchased.
• The order or payment reference and purchase date.
• The locked page link and exact message or a redacted screenshot.
• Whether you received a purchase confirmation, or only see a bank debit.

If there is a debit but no confirmed purchase, use the payment troubleshooting guidance too. The team needs to match the payment and account before confirming the access correction.

First distinguish a locked lesson from a video that opens but will not play. If the page asks you to buy access you already purchased, use the missing-access steps.

1. Keep the useful details. Copy the lesson link and note the playback position and exact error. Save any unfinished notes before refreshing.
2. Reload the lesson once. Check whether other pages load on your connection, then try another lesson. Note whether one video or all videos fail.
3. Compare the same lesson elsewhere if available. If you are using the app, open it in an up-to-date browser, signed in to the same account. This helps identify where the failure occurs.

If it still fails, use Report an issue with the lesson link, error, playback position, device and app or browser version. Say which comparison worked. If you cannot sign in to report it, email [email protected].

Open the current event page using the account you registered with and check the status shown there. A pending request or waitlist place is not a confirmed registration.

• Registration will not complete: keep the exact error and event link. If money was debited, do not pay again while the result is unclear; follow the payment troubleshooting steps.
• Your place is confirmed but the joining link fails or is missing: check the event page and confirmation for the latest joining instructions. To reach the host, open their card on the event page and use Message the host, or Call the host where the host has added a number, especially if the event is starting soon.

For a platform error, use Report an issue with the event link, registration status, exact error and event start time. If you cannot sign in or reach the host, email [email protected]. Keep private joining links and personal details out of public posts.

If the message is time-sensitive, open the event, lesson or purchase page directly while you check delivery. A missing notification does not by itself tell you whether a registration or purchase succeeded.

• Email: check the inbox associated with your GrowthX account, including spam, promotions and any workplace quarantine. Search for the event or product name.
• Phone notifications: check that your device allows notifications for GrowthX and whether Focus or Do Not Disturb is suppressing alerts.
• Sign-in code: check the delivery destination shown on the sign-in screen and follow the missing-OTP steps.

Still missing? Use Report an issue, or email [email protected] if you cannot sign in. Name the message, expected channel, related page and approximate time with time zone. For duplicate alerts, include both arrival times and a redacted screenshot. Never send the contents of an OTP.

For a platform bug, use Report an issue while signed in. Include the affected page, what you expected, what happened instead and the exact error. Add the shortest steps that reproduce it safely and a screenshot with private information hidden.

The report form attaches technical context, including browser and device information and captured error details. If you report by email, include your device and app or browser version yourself. Keep the report reference for follow-up.

For exposed personal information or abusive behaviour, report it privately through Report an issue. Include the page, profile or content link, when it happened and a short description. If someone misused your phone number, you can also use Report spam or harassment in Contact activity on your community profile. If you cannot sign in, email [email protected].

You do not need to reproduce a privacy exposure or engage further with someone to report their behaviour. Do not repost the material in a public thread. If you cannot sign in, email [email protected] for a bug report too. Never include passwords, OTPs or API keys.