One default, everywhere: setting your conferencing tool once
You shouldn't have to pick Zoom vs. Meet vs. Teams every time you send an invite. Now you don't — set a default conferencing app once and every meeting you schedule uses it.
Every scheduling flow eventually runs into the same annoying fork: which video tool are we using? For most people, the answer is the same 95% of the time. But the tool asks anyway — on every event, in every calendar, forever. That friction adds up, and worse, it produces meetings with the wrong link, meetings with no link, and the small daily indignity of clicking the same dropdown you clicked yesterday.
So we shipped a default.
What changed
There's now a Conferencing section in your account settings where you pick the video tool you actually use, and we use it. That's the whole feature Manage Conferencing Apps. Once it's set, new meetings you create attach the right conferencing link automatically — no per-event choice, no per-calendar configuration.
We deliberately kept the surface area small. This isn't a routing engine or a per-contact preference system. It's one setting, in one place, that answers one question: what's your default?
Why a default, and not something smarter
We considered heuristics — pick the tool based on the attendees' domain, or the calendar the event lives on, or the last tool you used with this person. All of those are defensible, and all of them are wrong roughly 10% of the time in ways that are hard to debug from the invite.
A plain default is boring, and boring is the point. You know what it will do. If you need something different for a specific meeting, you override it there. The rule in your head matches the rule in the product, which is the property we care about most for something you touch dozens of times a week.
It also means the setting composes cleanly with everything else. Templates, scheduling links, calendar integrations — they all just ask, "what's the default?" and get a straight answer.
What's next
The obvious extensions — per-scheduling-link overrides, team-level defaults, smarter fallbacks when a host doesn't have a given tool connected — are on the table, and we'll get there as the shape of the problem gets clearer from real usage. For now, set it once and move on. That's the win we wanted first.