This page is for the person running the business, not the person teaching. If you operate a school, sell a course, or are building an ed-tech company, your inbound is parents or customers, partner institutions, instructors, vendors, accreditation bodies and a team that asks questions in Slack. It arrives in waves around enrollment.
Waveloom reads that inbound and surfaces what needs you. It is not a learning platform, does not message students, and does not grade anything.
What your inbound looks like
A partner institution asking to renew a licensing agreement with new terms. A parent or customer escalating a refund request that support already declined. An instructor saying they cannot cover next month's cohort. An accreditation body sending a deadline in a long PDF. A vendor for your LMS announcing a price change. A Slack mention in #enrollment asking whether to extend the early-bird window.
And the flood: platform digests, marketplace notifications, ed-tech newsletters, receipts.
Sources you would connect
Gmail for partners, vendors, instructors and escalations. Slack for the enrollment, ops and instructor channels. See Slack mentions. Notion for the curriculum and planning docs. Linear if your ed-tech team tracks product work there. HubSpot if you sell to institutions. Google Calendar so term dates and meeting changes show up in the feed and the brief.
Web watches for a competitor's course catalog, a regulator's or accreditation body's announcements page, or a question like "changes to student data privacy rules in my region."
Example cards
Invented examples, alongside the one above.
The digests, receipts and notices are dropped. See inbox triage. The morning brief is a calm place to start.
It executes two background actions, reply by email and reply in Slack, both only after you approve the exact text. If student data lives in an account, think before connecting it. Disconnecting a source stops the reading and clears the raw data pulled from it. Cards already in your feed stay.