Channels
Choose the right contact route
Each inbox is watched by a specific team — picking the right one skips a routing step and gets a faster first reply. If you are unsure which applies, use hello@campusos.app and we will forward internally.
Questions about the product, company, or campus fit. Routed to the right team within one business day.
Login issues, billing questions, AI Copilot problems, marketplace disputes — anything tied to an individual account.
Universities, clubs, and student bodies planning a campus rollout, custom dashboards, or bulk accounts for a cohort.
Interview requests, press kits, embargoed pitches, and speaker bookings for campus tech coverage and student-platform stories.
Responsible-disclosure channel for vulnerabilities. We respond within 72 hours and coordinate a fix timeline with the reporter.
Open roles, team introductions, and speculative applications — we read every thoughtful note that comes through.
Expectations
What happens after you reach out
Response times vary by channel because the people behind each inbox do. Here is what you can typically expect, and what signals a faster path when urgency matters.
| Channel | Typical window | Notes |
|---|---|---|
| Student support | Within 1 business day | Priority escalation for Pro subscribers. |
| Institutional partnerships | Within 2 business days | Discovery call scheduled for rollouts serving more than 500 students. |
| Press & media | Within 2 business days | Time-sensitive pitches flagged in the subject get same-day review. |
| Security disclosures | Within 72 hours | Critical issues are triaged immediately, even on weekends. |
Operational questions
General product and company messages are reviewed quickly and routed to the relevant team based on context and urgency. We prefer short, specific emails over long explanations.
Support issues
If your request is technical, include concrete detail — steps taken, error messages, screenshots — so the first reply can move directly toward resolution rather than asking clarifying questions.
Preparation
What to include in your message
The fastest-resolved conversations all look similar: they start with enough context to answer without a back-and-forth. If any of the following apply, include them up front.
- The campus, institution, or account context involved in your request.
- A short description of the issue, question, or partnership goal — one paragraph is plenty.
- Any deadline or timing constraint (exam week, event date, rollout target) that affects the request.
- Screenshots, links, or the exact error text when reporting a technical problem.
- For partnerships: rough student count, target start date, and which CampusOS modules you are evaluating.
- For press: publication, angle, and deadline in the subject line — speeds routing to the right spokesperson.
Also available
Other ways to reach or follow CampusOS
Outside of direct email, CampusOS publishes product updates, student-platform guides, and launch notes across the following:
Self-serve answers to the most common student and campus-team questions, organized by topic.
Long-form writing on student productivity, active recall, campus tooling, and launches.
Overview of CampusOS for universities, student bodies, clubs, and faculty partners.
Team, mission, and the thinking behind a single operating system for students.