Contact · Schedule.software
One address, and a person on the other end of it.
[email protected] is the whole contact surface. There is no form on this page and no lead-capture behind it: this marketing site stores nothing about you, which is easiest to guarantee by not asking.
What to say, so the first reply is useful
Four things, and you can skip any of them.
✓What you are scheduling
Picture day, parent-teacher conferences, admissions tours, the master schedule, volunteer or student-helper shifts, staff and substitutes, a photo crew, or rooms and equipment. Naming the surface lets us answer about the thing that exists rather than about the platform in general.
✓Roughly how much of it
Slots per cycle, sites, crews, rooms. Order of magnitude is enough. It changes which correctness guarantee matters most to you — concurrency behaviour is a different conversation at fifty bookings than at fifty thousand.
✓What breaks today
Double-books, a spreadsheet nobody trusts, a roster that leaks names into a calendar app, a dispatch day rebuilt by hand every time the weather turns. The specific failure is more useful to us than a feature list.
✓Whether privacy or procurement is the gate
If a consent posture, a data-handling question, or a district review is what stands between you and a pilot, say so in the first email and we will lead with it. The privacy and data page is the short version.
Which conversation
Education, Professional, Enterprise — or none of the above.
Education. The eight K-12 booking surfaces, the correctness guarantees, the consent posture, and what a school or district rollout looks like.
Professional. The dispatch and routing engine, multi-resource booking, and the hard-constraint eligibility gate.
Enterprise and white-label. Licensing, the module toggle layer, and self-hosted or managed deployment.
Press, privacy, or something else entirely. Same address. Put the word in the subject line and it gets routed rather than queued behind sales.
Before you write
Two things worth knowing first.
There is no live checkout on this site, and getting in touch does not start a billing relationship. Early access is a conversation and a scoped pilot — no card, no charge, no contract signed on a web page. The getting-started page sets out the four steps.
Some of what you may have read about is still in development: self-serve onboarding, two-way calendar sync, the CalDAV server, public booking pages as a standalone consumer surface, and the full workforce layer. The engines underneath — dispatch, routing, the constraint gate, the self-heal proposer, the eligibility gate — are built and run in production. Ask us which side of that line your requirement falls on; we will tell you straight.