How we work with calendars
Invitations your guests can accept from inside their own mail app.
Most ticketing platforms attach a calendar file. You open it, it lands in your diary as a note, and that is the end of it. We do something different: an IHGIZ invitation is a real invitation, so your guest's mail app shows Accept and Decline on it — and when they press one, the answer comes back to your roster without anyone opening a browser.
This matters most for the guests you least want to chase: the ones who live in Outlook all day, who will answer an invitation in one click and will not open a link in a marketing email. It also means a change of time or venue updates the entry they already have, rather than adding a second one beside it.
What we implement
| Standard | What it gives you |
|---|---|
| RFC 5545 (iCalendar) | Every event and ticket as a calendar entry, with the right time zone, a reminder, and a status that changes when you cancel. |
| RFC 5546 (iTIP) | Invitations that can be accepted or declined, and cancellations that strike the entry through rather than leaving it. |
| RFC 6047 (iMIP) | The above, delivered by ordinary email — no app, no plugin, nothing for your guest to install. |
| Subscribable feeds | Anyone can subscribe to an organizer's whole programme in the calendar they already use. New nights simply appear. |
Reminders that do not depend on us
Every ticket carries an alarm inside the calendar entry itself. Your guest's own phone reminds them, which keeps working whether or not our messages reach them and whether or not they have signal on the night. It is the one part of a ticket nothing on our side can break.
Following an organizer needs an account; subscribing to their calendar does not. Both are on every organizer's page, and the second is the one to share with people who have never used this platform.