Contact
Route tryout, team, registration, payment, and training questions to the right club role.
Route tryout, team, registration, payment, and training questions to the right club role.
Conversation history
Authorized staff can see the player and workflow context associated with the question.
How RootSoccer handles it
The contact experience demonstrates intake, routing, and accountability—not just a generic email form.
In this private concept, delivery is intentionally disabled. A production pilot would connect routing rules only after the organization approves owners and retention expectations.
Why this is better than a page clone
The public explanation, structured records, permissions, status, and next action are designed as one experience. Magic SC can prove the workflow in a pilot without pretending its incumbent systems vanish overnight.
How RootSoccer improves contact
Source parity is the baseline. This section demonstrates the operating workflow RootSoccer adds for Magic SC.
Route by topic
Program, registration, schedule, referee, billing, and governance questions can reach the correct owner.
Capture useful context
The form asks for the minimum identifiers the operator needs without collecting sensitive child or payment data.
Track the response
Submissions can carry status, ownership, notes, and resolution instead of disappearing into a shared inbox.
Safe demo behavior
Concept submissions remain disabled from external delivery and clearly warn users not to enter sensitive information.
Try the structured contact flow
Stage demo only. Do not enter sensitive child, medical, identity, or payment information. Submissions are not sent to the organization.