1.1 Invitation or registration is failing
Error "Email address already taken": usually an invitation is still pending. Ask the user to search their inbox (including spam) for the invitation link and accept it. If the link (typically valid for 30 days) has expired, an admin can delete the pending invite and send a fresh one.
Invitation email not received: messages often end up in spam. Mark the sender (for example [email protected]) as trusted. Admins can resend the invite or export an individual invitation code and share it manually.
1.2 Email verification issues
Verification code or link not arriving: check the spam folder and make sure the sender domain is not blocked. Request another verification email or ask support to resend it.
Account remains inactive: without a verified email the profile is hidden from the user directory and settings cannot be changed. Solution: open the verification message, follow the link, and activate the account.
1.3 Registration loop caused by unverified email
If the email address was never verified, the user cannot request a password reset and also cannot register again because the address already exists. An administrator must delete the account so the user can start over.
2.1 Incorrect or forgotten password
Mistyped passwords are the most common reason for sign-in failures. Use the "Forgot password?" flow to request a reset link (often valid for only 1 hour) and set a new password. A password manager helps reduce errors.
2.2 Two-factor authentication (2FA) problems
Codes may not arrive or the user might have switched devices. Confirm the phone has reception, ensure the authenticator app is installed, or rely on backup codes. If SMS verification fails, switch to email or another factor.
2.3 Account locked or unusual activity detected
Identity providers lock accounts when logins appear suspicious. Use the recovery page to confirm your identity, wait 24–48 hours, and try again. Contact support if the lockout persists.
2.4 Browser or device issues during login
Outdated browsers, corrupted cookies, or extensions can block the sign-in page. Clear cache and cookies, update the browser, disable pop-up or tracker blockers, or try a different browser. On mobile devices reinstall the app and restart the device.
2.5 Sign-in loop because activation is missing
Unverified accounts cannot trigger password resets and cannot re-register. An admin must remove the account so the registration can restart.
3.1 Password reset email not received
Reset links are sent immediately but often land in spam. Check the spam folder and whitelist the sender. If the email still does not arrive, contact support for a manual reset.
3.2 Reset link expired or invalid
Links expire quickly for security reasons. Simply run the "Forgot password?" flow again to generate a fresh link.
3.3 Too many failed reset attempts
Multiple wrong codes can trigger a temporary lockout. Wait a few hours or reach out to support. In high-risk cases an identity check may be required.
4.1 Google or social login: account disabled or suspended
If the Google account is suspended, all third-party sign-ins will fail. Try signing in directly with Google, review the status, and complete the recovery steps. If the third-party account itself is suspended, contact that provider's support team.
4.2 Social login with a deleted account
Deleting a Google account removes its social login links. Sign in with email/password or create a new account. If only the third-party profile was removed, register again or contact support.
4.3 Existing account does not allow Google login
Some platforms do not allow enabling social login after a traditional account already exists. Continue with the email/password combination or ask support whether they can connect the account manually.
4.4 Common Google login error codes
Examples: 400 access_not_configured (app misconfigured), 400 admin_policy_enforced (organisation blocks the app), 400 invalid_request (invalid request), 400 invalid_user (inactive account), and 400 origin_mismatch or redirect_uri_mismatch (callback misconfigured). Most issues require the app developer to fix the configuration—inform support with the exact error.
5.1 Website does not load
If you see "site cannot be reached", test the internet connection, reboot the router, clear cache and cookies, disable extensions, try another browser, flush the DNS cache, and check if the service is up for everyone. In corporate networks request that the firewall or proxy allow the domain.
5.2 Cookies disabled or pop-up blocker active
Social logins and persistent chat sessions need cookies. Allow third-party cookies or add the domain to the exception list, and permit pop-ups for the site.
6.1 AI responses are inaccurate or off-topic
Language models are probabilistic and may hallucinate. Phrase the question more precisely, provide additional context, and submit feedback to the developer team. Use integrated web search for up-to-date information.
6.2 No answer or very long response times
Possible causes include server load, connectivity issues, or browser errors. Reload the page, resubmit the prompt, clear cache and cookies, and contact support if the issue persists.
6.3 File uploads or large attachments failing
Review the upload dialog, adjust file size and format, compress large files, or convert them to supported formats such as PDF or JPG. Follow the privacy policy when sharing sensitive documents.
7. Billing and subscription issues
Declined payment method: verify card validity and available funds, try another method (for example PayPal), or contact the bank. If a subscription fails to renew, check whether the stored payment method has expired. Missing invoices: verify the billing email address and review the spam folder.
8.1 Data processing and privacy
Explain in the privacy notice how chat transcripts are stored and processed. Offer options to delete conversations or close the account, and outline GDPR rights such as access, deletion, and objection.
8.2 Suspicion of unauthorised access
If you notice unexpected sessions, change the password immediately and enable 2FA. Review security logs or login alerts, and inform support or request an account lockdown if anything looks suspicious.
8.3 Requesting account deletion
Provide an account deletion option within the profile settings. Once removed, data is erased according to policy. Remove social login links—for example from the Google security console—if applicable.
9.1 Geographic restrictions
Some AI services only operate in specific countries and will display a notice when access is blocked. VPNs might work but are often prohibited by the terms of service. Contact the provider to confirm regional availability.
9.2 Age restrictions
Many services have a minimum age requirement and may request ID verification. Parents or guardians can approve registrations. Contact support if the verification workflow fails.
9.3 Terms of service and community guidelines
Violations such as hate speech or spam may trigger suspensions. Review the policies carefully and, if a suspension was accidental, file an appeal and provide supporting evidence.
10. Accessibility and assistive technologies
Ensure screenreader support with proper ARIA labels and keyboard navigation. All actions—sign-in, sending messages, uploading files—should be keyboard accessible. Offer dark mode and adjustable font sizes.
11. Getting further help
Self-service checklist: inspect the spam folder, clear cache, reset the password, try alternate login methods, and resend verification emails. If the issue persists, reach out via contact form, chat widget, or email and include error messages, timestamps, device/browser details, and screenshots.