01
Choosing the right contact route
Use the team contact details for questions about this squad's activities, website information, kit coordination or family access. For official registration, broader club programs or club policies, ask for the relevant club contact or consult the club's published resources. Naming the subject at the start of your message helps it reach the right person. A schedule question should include the event date; a kit question should identify the item; an account question should describe the page and action that failed.
Only include information that is needed to answer the question. A general inquiry does not require a child's address, birth details, medical history or a copy of a private document. If further information is necessary, ask how it should be provided securely. Do not assume that an email address shown for sponsorship is the correct place for every confidential matter. The Contact page is an introduction to the team, not a guarantee of immediate availability. For time-sensitive changes, use the communication channel the organizer has specified and confirm that your message has reached the appropriate person.
02
Getting useful help without sharing secrets
When something does not work, describe what you were trying to do and what happened instead. Include the page name, whether you were signed in and the exact error message if one appears. Say whether the problem occurs on a phone or computer and whether it can be repeated. That information is usually more useful than a general message saying the portal is broken. For a child-link problem, explain whether the child is absent entirely or visible but unavailable for the action.
Before sending a screenshot, remove passwords, recovery links, financial information and details belonging to another family. Crop to the relevant error while keeping enough context to identify the screen. Do not post private support material to a public gallery or social media account. A website inquiry is not an emergency channel, and this page does not promise a fixed response time. If the question concerns a session starting soon, use the team communication route identified for that event. Keep follow-up messages together where possible so the person helping can see what has already been tried.
03
Using a parent account correctly
The parent portal is for information connected to your household and the team activities your account is allowed to access. Sign in with your own account and check that the linked player is correct before completing attendance, forms or other child-specific tasks. A missing child link is a relationship issue, not a reason to create another roster entry. Use the available linking request or contact the manager with the minimum information needed to identify the player and resolve the account relationship.
Keep your password private and do not share a manager account to gain access to a parent feature. Different roles have different responsibilities, and management tools require additional protection. If sign-in fails, use the site's recovery flow and check the link's destination before entering a new password. A reset link can expire or be replaced by a newer request. Never send a password, verification code or recovery link in a support message. Once you finish on a shared device, sign out and check that another person cannot continue using your private team session.
04
Suggesting a clear website improvement
Useful feedback starts with a task. Tell the team what you needed to find, which page you used and where the information became confusing. For example, an arrival time may be difficult to distinguish from a start time, or a button may be hard to reach on a phone. Include the device type and any relevant display setting, such as larger text. You do not need technical knowledge to describe a problem clearly or suggest a better label.
Separate incorrect information from a design preference. If a date or venue is wrong, give the current source so the team can check it. If a layout is difficult to use, explain the obstacle rather than requesting more content everywhere. Changes should help families complete a real task and preserve private information. Avoid including another child's details in a public suggestion. The team can consider improvements without promising a specific release date. If a workaround is needed in the meantime, ask for the information or assistance directly instead of repeatedly attempting an action that might create duplicate requests or submissions.
Back to page overview ↑