Company-wide meeting attendance tends to plateau well below full headcount, and it has almost nothing to do with whether people care about the content. It’s usually a delivery problem hiding behind what looks like an engagement problem: one calendar invite, sent from one inbox, expected to land with the same urgency across every department, function, and time zone in the company.
one sender doesn’t fit an entire company
A briefing from IT reads differently than one from HR, and both read differently from a leadership all-hands — but if every company-wide send comes from the same generic "events" mailbox, none of them carry the weight of who’s actually speaking. People triage their inbox partly by sender. A briefing that looks like it came from the right desk gets opened faster than one that looks like broadcast spam, even when the content is identical.
connect a sending identity per department, not per event
The fix isn’t a better subject line — it’s routing sends through the actual owning team’s identity. IT sends under its own domain. HR sends under its own. Same platform, same nudge sequence structure underneath, but a different, recognizable sender for each. That single change — who it’s from, not what it says — tends to move attendance more than any amount of editing the invite copy itself. Full detail on the enterprise use case.
four time zones is a scheduling problem, not a headcount problem
The other half of that ceiling is time zones. A briefing that lands as a 6am calendar block for one office and a 4pm block for another isn’t a fair comparison of who "cares more" — it’s a scheduling artifact. Nudges timed against each invitee’s own lead time (not a single blanket send time) at least ensure everyone gets reminded on a schedule that makes sense for their own day, rather than everyone getting the same nudge at a moment that’s convenient for exactly one office.
the same scoping problem, at conference scale
This is the same underlying discipline behind scoping reminders per session at a multi-track conference — don’t send one broadcast to everyone and hope it’s relevant to each person; scope the send to the actual audience and sender it should come from.
what changes when it’s not a spreadsheet
None of this requires anyone manually tracking who got which reminder in a spreadsheet, or IT and HR coordinating send times by hand every quarter. It’s the same underlying mechanic across the company — a calendar invite, then nudges over email and SMS on their own lead times — just configured once per department, then left alone.
Workspaces are how this stays organized without extra seats or a second account: each department gets its own segment, its own connected sending identity, while seats, credits, and campaigns stay pooled at the account level. It’s the same separation-of-identity idea that matters even more for public-sector notices, where the sending identity isn’t just a nice touch but a requirement. See how workspaces fit into pricing, or head straight to early access.