Informational perimeter
We discuss curricula logistics, facilitation kits, SLA expectations—not individualized fluid prescriptions.
Human-routed inbox
Share procurement codes, facilitation constraints, multilingual needs, accessibility riders, district counsel CC lists—anything that helps coordinators triage thoughtfully.
Acknowledgements strive to arrive within five contiguous U.S. business days excluding California holidays in Terms of Use. Vendor reviews may lengthen timelines—we say so plainly.
These guardrails rarely surprise partners who already read policy PDFs—they simply restate escalation etiquette on the contact lane.
We discuss curricula logistics, facilitation kits, SLA expectations—not individualized fluid prescriptions.
Assume TLS end-to-end; if your gateway strips TLS introspection succeeds only after forwarding headers prove authenticity.
Mention dialect preferences early—we route translation pods before rehearsals rather than scrambling mid-flight.
When timelines slip we disclose blockers—even if blockers originate from upstream hosting partners.
Signals desk
Walk-in visits stay rare—schedule through this form first so coordinators can reserve quiet debrief suites.
Validation runs inline; submission routes to gratitude screen without exposing medical detail fields we never collect.
Operational notes
After you send
Spam filters scrutinize unsolicited attachments—link to repositories instead of embedding massive archives.
Escalations route to whichever specialist owns the SLA described in operational dashboards; you see names, not hidden aliases.
If travel brings you near Berkeley, mention it—we occasionally host micro meetups for partners already mid-handshake.
Review the layered system first