≈2
Business days for first human reply mid-week
Contact
Coaching desk
Contact pathways tuned for clarity
Whether you are confirming accessibility needs, asking how duo nights differ from cohort packs, or requesting syllabus excerpts before committing time, the same Auckland crew reads every thread—no opaque ticketing tiers.
- HTTPS intent
- Human triage
- Privacy-aware
Weekday replies prioritised
Before you write
Summarise availability blocks, preferred session format references (with page links if helpful), and whether you need wheelchair-accessible pathways documented ahead of visiting 1A/155 Queen Street. This overview stays informational until you formally enrol through channels our reply describes.
Secure note
Send a structured message
Fields validate in real time so typos surface before redirecting you to the Thank You confirmation page—still not proof of enrolment.
Message composer
After submission
Expect deliberate pacing—not-automation theatre
Messages queue chronologically; escalation occurs only when safety-sensitive keywords appear.
TLS
HTTPS assumed on production hosts
24
Month retention window for routine enquiry archives
“We batch replies when coaching evenings stack tall—silence usually means timing overlap, not disregard.” Desk coordination memo
Browse context before waiting on inbox refresh
Sessions layouts and Programme arcs carry vocabulary that accelerates email exchanges—open those tabs side-by-side while our reply lands.