Verification-first automation
Bloomod automatically filters out unverified attendees. They remain saved in the event, but only verified attendees can receive an automated calendar invite.
Collect attendees for each event, verify participation by email, and send calendar invites automatically only to verified attendees. Every event keeps its own list.
No card required. Sender verification applies. Nothing sends without your approval.
Product launch
148 event attendees · 119 verified
Pipeline: attendees registered, verified and queued. Currently sending. Delivered and accepted still pending.
This event’s automation sends only to verified attendees. Turn it off in the event settings to stop all Bloomod calendar invites for this event.
Invites land in
No SMTP configuration required to begin.
A simple starting point for new businesses, and infrastructure underneath it for verified accounts that outgrow the free allowance.
50
Free invites, every month
1,000
Attendees in one event
10,000
Recipients per send
100,000+
Campaign audience
Each stage is a milestone, not a guaranteed pricing allowance. A single campaign can exceed 100,000 recipients on eligible plans.
Bloomod automatically filters out unverified attendees. They remain saved in the event, but only verified attendees can receive an automated calendar invite.
Malformed addresses, duplicates and unroutable records are caught before send, not after a failed campaign.
A single suppression list applies across every campaign, permanently.
Large audiences are batched into managed queues you can inspect mid-flight.
Sends are paced to protect sender reputation with each calendar provider.
Failed invites are classified and retried under a policy, and hard failures are suppressed so the same dead address is not paid for twice.
Each event owns its attendee list. Collect a name and email from the event’s public form or landing page, import a CSV/XLSX list, or add someone directly.
Product launch / Attendees
148 records for this event
| Attendee | Source | Verification | Invite | Last activity |
|---|---|---|---|---|
| Maya Patel | Public form | Verified | Sent | Verified 2h ago |
| Arun Mehta | CSV import | Verified | Sent | Imported yesterday |
| Neha Shah | Landing page | Unverified | Manual only | Registered 3d ago |
Event automation
Product launch
Set up the event, collect or import attendees, and let the event setting decide whether verified attendees receive their calendar invite automatically.
Collect attendees
Use a public form, event landing page, CSV/XLSX import or direct entry.
Set event details
Title, time, duration, location or meeting link, time-zone handling.
Verify participation
Public-form attendees verify through a magic link sent to their email.
Set automation
Enable or disable calendar-invite automation for this event.
Invite verified attendees
When enabled, Bloomod sends only to attendees marked Verified.
Quarterly filing webinar
Approval requiredAster & Co.
Your quarterly filing update
Thursday, 10:30–11:15 · Add to your calendar automatically
Hello Maya — here is the filing checklist we will walk through together. This invite blocks the time on your calendar; decline it if the slot no longer works.
Review your checklistManaged credits cover initial sending. Higher volumes may require a paid allowance.
Follow each approved invitation from preparation through delivery and RSVP, with the problem states visible rather than buried.
Invite lifecycle
Campaign closed100,482
Invite audience
98,710
Delivered
42,508
Accepted
8,421
Tentative
RSVP tracking depends on the recipient's calendar client and provider settings. Delivery does not guarantee inbox placement or calendar acceptance. Figures shown are illustrative.
Bloomod does one thing. Permission-based event, meeting, webinar and recurring-event invites, delivered to the calendar your customer already uses.
Calendar invitations
AvailableGoogle Calendar, Outlook, Microsoft 365 and Apple Calendar. Invites land in the inbox and block the time — no app for the recipient to install.
Planned after year one
Not implemented and not sold today. Listed so you know where the platform is going, not what it does now.
Requirements and pricing will differ by channel when introduced.
Collect attendees for a chosen event, run event workflows programmatically, and keep clear operational control. Every attendee remains scoped to that event.
API
AvailableCreate attendees for a selected event and run event workflows programmatically.
Public event form
AvailableAdd an event-specific registration form to a public web page.
CSV / XLSX import
AvailableAdd attendees in bulk to one event, with Verified or Unverified status.
Direct entry
AvailableAdd one attendee directly to the selected event.
curl https://api.bloomod.com/v1/invites \
-H "Authorization: Bearer $BLOOMOD_KEY" \
-H "Content-Type: application/json" \
-d '{
"attendee_id": "att_0182",
"event": "quarterly_filing_webinar",
"starts_at": "2026-08-13T10:30:00+05:30",
"duration_minutes": 45,
"requires_approval": true
}'
# 202 Accepted — queued, pending human approval
Names and email addresses are encrypted in transit and at rest. They are readable only by the event owner; Bloomod cannot view attendee email data.
Sensitive attendee data is encrypted in transit and at rest.
Only the event owner can view attendee names and emails.
An attendee record is kept with its event, not a global database.
A responsible starting point for calendar invitations, with managed infrastructure available as usage increases.
No card required. Upgrade only when usage grows.
Included
Responsible limits
No. The invite arrives in their inbox and blocks the time on whichever calendar they already use — Google, Outlook, Microsoft 365 or Apple. There is nothing for them to install or sign up for.
Not today. Calendar invitations are the only channel available. Marketing email, transactional email, SMS, WhatsApp and RCS are on the roadmap for year two, and none of them are sold or usable now.
No. The invite API and the embeddable capture form are launch features, available on every plan including the free one, with fair-use rate limits. Most competing tools gate API access behind a paid tier.
A prepared campaign sits in the queue until a person with the right role approves it. Consent, suppression and sender-verification checks are shown at that moment, so approval is an informed decision rather than a formality.
It depends on the recipient's calendar client and their provider's settings. Accepted, tentative and declined states come back reliably from the major providers, but some clients report partially or not at all. Delivery never guarantees inbox placement or acceptance.
Paid allowances are set with you as your verified audience grows, so there is no published price list yet. The free plan is a real starting point rather than a trial: 50 managed invite credits every month, no card required.
Set up an event, collect attendees, verify participation, and keep calendar automation under the event owner’s control.
No SMTP setup required to begin. Sender verification and responsible-use rules apply.