One-time event
A single date and time sent to a permissioned audience — a launch, a filing deadline, an open house.
A calendar invite is not an email about a meeting. It is the meeting — written straight into the calendar your customer already keeps, with an RSVP that comes back to you.
No card required. Sender verification applies.
What the recipient does
Nothing to installReceives the invite
It arrives as a calendar invitation, not a newsletter.
Time is already held
Most clients place it on the calendar before any action.
Accepts or declines
One tap. The state comes back to your customer record.
Gets the update
Move or cancel it later and their calendar follows.
Bloomod speaks the calendar standard rather than a provider's private API, so the same invite behaves correctly across all four.
| Provider | Invite delivery | Auto-block | RSVP returned | Series updates |
|---|---|---|---|---|
| Google Calendar | Inbox + calendar | Yes | Full | Yes |
| Outlook | Inbox + calendar | Yes | Full | Yes |
| Microsoft 365 | Inbox + calendar | Yes | Full | Yes |
| Apple Calendar | Inbox + calendar | Yes | Client-dependent | Yes |
Behaviour depends on the recipient's client and their provider's settings. Some clients report RSVP state partially or not at all. Delivery does not guarantee inbox placement or calendar acceptance.
A single date and time sent to a permissioned audience — a launch, a filing deadline, an open house.
A series on a daily, weekly, monthly or custom pattern, updated as one object rather than fifty separate invites.
Recurrence patternsOne-to-one or small group, with a location or meeting link.
MeetingsOne-to-many at volume, where the audience comes from a segment and the send is paced through a queue.
Bulk sendingEvery campaign stops for a person. The checks are shown at the moment of approval, so signing off is an informed decision rather than a habit.
Approval gate
Awaiting sign-offIllustrative only — this template has no live account behind it.