iCal Delivery with a Proper Interface on Top
Raw iCal feeds are 1998 infrastructure. Subscribers deserve better in 2026.
A raw webcal:// URL gets events to calendars, but it's UX-less: no branded subscribe page, no per-event opt-out, no unsubscribe path, no analytics. A broadcast channel uses the same underlying iCal pipe and wraps it in everything an audience actually needs.
The Challenge
- ✕A webcal:// link is hostile to non-technical subscribers — most don't know what to do with it
- ✕No branded subscribe page means it looks unprofessional next to your other channels
- ✕Subscribers can't mute individual events — it's all or nothing
- ✕No way to see how many subscribers you have, let alone per-event opt-out signal
- ✕Changing calendar hosting means every subscriber has to re-add the feed
How WhenToMeet Helps
A proper subscribe page
Replaces a webcal:// URL with a branded page that detects the viewer's device and opens the right calendar.
Per-event opt-out
Subscribers can mute individual events — something raw iCal can't do.
Clean unsubscribe path
One-tap unsubscribe. Raw iCal feeds require the subscriber to find the feed in their calendar settings.
Subscriber analytics
See aggregate subscriber count and per-event opt-out. Raw iCal tells you nothing.
Branded experience
Your cover image and description greet new subscribers. A raw iCal URL is naked text.
Key Features
iCal under the hood
The delivery mechanism is the same iCal standard every calendar supports. The wrapper is better.
Recurring events with proper editing
Edit a single recurring instance without breaking the series — a common pain point with hand-maintained iCal.
Subscriber anonymity
Raw iCal feeds have anonymous subscribers too, but no way to count them. Broadcast gives you counts without identities.
Stable subscribe URL
If you move hosting, the broadcast URL stays. Subscribers keep receiving events without re-subscribing.
Branding, not raw URL
Your channel has a name and image. A raw iCal feed is, by definition, invisible.
Get Started in 3 Steps
Replace your webcal:// URL
Create a broadcast channel and share the new subscribe link. Existing subscribers re-subscribe via the branded page.
Import or recreate your events
Add your events. They're stored in WhenToMeet's database, exposed as iCal to subscriber calendars.
Enjoy the analytics and opt-out
Watch subscriber count rise. See which events get muted and use that as signal.
Frequently Asked Questions
Is this still iCal under the hood?+−
Yes. Subscriber calendars fetch iCal data; broadcast wraps the feed in a friendlier UX. No proprietary format.
Can existing iCal subscribers migrate?+−
Share the broadcast subscribe link in your next communication. Subscribers re-add via the branded page in seconds, then remove the old feed.
Does it work with every calendar?+−
Yes. Google, Apple, Outlook, and any iCal-compatible calendar.
Can I still expose a raw iCal URL?+−
Under the hood, yes — that's how subscriber calendars fetch. But you share the branded subscribe URL publicly, not the raw feed URL.
What about self-hosted calendars (CalDAV)?+−
CalDAV servers can also subscribe to the broadcast iCal feed. The model is compatible.
How does per-event opt-out work over iCal?+−
Each event contains a description with a tap-to-mute link. Tapping removes that specific event from the subscriber's feed.
Is it free?+−
Yes, the core functionality is free.