Use pricing when the customer is still choosing free, paid individual, club, organization, federation, or league posture.
Open pricingGlobeIce/Contact
Contact GlobeIce
GlobeIce is built as a governed hockey platform, so the fastest way to get help is to route your issue into the right workflow. Use the paths below for corrections, onboarding, safety, policy questions, and public data issues.
GlobeIce should make it clear where each kind of request belongs. Dedicated inbox publishing can still expand later, but launch users should already be able to route corrections, onboarding, trust, and policy issues into the right lane.
7 routing lanes3 priority levelsGoverned intakeTrust-aware supportBilling topic activeFederation and League
Billing Route
Plan fit, checkout readiness, or subscription support
Billing contact should move into the same launch-ready commercial model as pricing, account creation, organization onboarding, and admin billing intake. Pick the route that matches the current step.
Federation and League
INFO: sales assistedFrom EUR 399 per month - Govern countries, leagues, clubs, competitions, source coverage, and official operating lanes.
Support routing profile: Federation, league, and enterprise support
Audience: organizationSales-assisted enterprise lanesupport-segment: federationsupport-segment: leaguesupport-segment: enterprise
Use account creation when the plan should follow the customer into HockeyOS or checkout after authentication.
Create accountUse organization onboarding when the buyer is a club, academy, arena, league, federation, or governed hockey operator.
Register organizationRouting Posture
Where requests should go next
Contact on GlobeIce should route people into the correct governed lane fast. These paths help separate policy reading, corrections, onboarding, and trust work.
Contribute and corrections
Open Contribute when the request is really a correction, source improvement, or public data handoff into GlobeIce governance.
Organization onboarding
Open Register Organization when the real request is an official page, a workspace, or a governed organization launch inside GlobeIce.
Billing and checkout support
Open Pricing when the real request is plan fit, paid launch readiness, checkout gating, invoices, or subscription support.
Trust and source questions
Open Sources when the next step is not support, but deciding what should count as official, trusted, or properly anchored in the public graph.
Policy reading first
Open Legal, Privacy, or Terms first when the issue still needs policy context before it can be routed into a live support or governance lane.
How To Reach Us Well
What helps GlobeIce process requests quickly
GlobeIce routes many requests into governance, moderation, intake, and editorial systems. Good context makes the difference between a fast correction and a slow manual chase.
What to include
- Include direct links, ids, screenshots, and source references whenever possible.
- If the issue touches a specific player, club, arena, league, federation, or tournament, include the exact GlobeIce page URL.
- If the issue is urgent because of fraud, impersonation, rights, or harmful misinformation, say so explicitly in the first line.
- Use the most relevant GlobeIce route below so the request lands in the right governance lane instead of a generic inbox.
Response priorities
Critical
Impersonation, rights issues, harmful or fraudulent listings, safety concerns, or clearly damaging public inaccuracies.
High
Incorrect canon for clubs, federations, players, arenas, schedules, standings, or editorial attribution that affects trust.
Standard
Onboarding interest, feature feedback, partnerships, Academy questions, and general GlobeIce navigation or product guidance.
GlobeIce contact model
GlobeIce is not just a brochure site. A correction may need editorial review. A new club may need onboarding. A billing issue may need admin governance. A billing issue may need checkout-readiness context, entitlement review, or subscription support. A suspicious marketplace listing may need moderation. This page is therefore designed as a routing layer, not a dead-end generic contact form.
