Hotline

Pick a time. Run the week. Count the hours.

Civic and public-interest teams keep sensitive things on their calendars. You shouldn't have to hand over the whole thing just to get a meeting on the books — so with Hotline you hand-pick a few times, share one link, and the other person taps one. No account for them, no calendar wall for you, no week of back-and-forth.

That was the wedge. What grew around it is the calendar those teams run the rest of the week from — and, for the organizations among them, the rota too: shifts, coverage, hours and cost, in the same product that books the meetings.

What makes it different

  • Your whole calendar stays private. The host offers a short list of times instead of publishing full availability. For teams whose calendars are a public record — or opposition research — that is the whole point.
  • Works with the calendar you already keep. Google, Outlook, Apple iCloud, or anything that publishes an ICS feed. Hotline connects to each one directly and labels every busy block with where it came from.
  • One link, one tap, no account. The other person picks a time from their phone, in their own timezone. Every link is single-use and re-checked at the moment of booking, so a slot can't go twice.
  • Priced per organization, not per seat. One person is free, with nothing metered. Above that the bill is per organization with unlimited seats — charging by the head is a strange way to bill a team that runs on volunteers, fellows, and people who schedule twice a year.

When the calendar isn't only yours

Campaigns, mutual aid groups and small nonprofits don't only book meetings — they run a rota. Hotline does that in the same place, so the shift schedule isn't a second tool with a second login and a second copy of everyone's name.

  • Build the week as a draft. Shifts stay invisible until you publish them, so next month can be worked out in front of people without landing half-formed on anyone's calendar.
  • The people you schedule don't need accounts. Add a name. Add an email later, if they want their shifts on their own calendar. Bring a roster in from a spreadsheet and take one back out.
  • Read coverage instead of counting it. Who's on, and which days nobody is — as a view of the week rather than a tally you assemble by hand.
  • Hours and cost, straight from the shifts. Worked time is reviewed and signed off before it counts as money, then comes out by week or by month as a printable invoice. Admins see the cost; everyone else sees their own hours.

Why we built this

Civic and public-interest teams' calendars are sensitive — they hold meetings, plans, and people that aren't anyone else's business. Most scheduling tools answer “when are you free?” by publishing the answer, which is exactly the wrong default for this kind of work.

So we built the opposite, and then kept going. The teams using it didn't want a booking link bolted to the side of their week — they wanted the week itself: the meetings, the shifts, and the hours those shifts add up to, without paying by the person for the privilege.

Make the call