It lands in Outlook, not in an inbox.
An email can go unopened. A meeting has to be actively declined, and that is the entire difference.
Two ICS invites, correct organizer
- Copy A
- To
- System owner and contacts
- Organiser
- The coordinator
Responses route to the coordinator, and the owner sees a normal accept button.
- Copy B
- To
- The coordinator only
- Organiser
- The system mailbox
A distinct UID, so the coordinator can accept it into their own calendar.
The problem
You cannot accept a meeting you organise.
If the coordinator is the organiser, they cannot get the meeting into their own calendar — Outlook does not offer them the button. If a system mailbox is the organiser, every owner's response lands in a mailbox nobody reads.
- 01
The owner's copy
The organiser is the coordinator, so responses route back to them. The display name and the sending address match, so Outlook does not add the "on behalf of" line that confuses recipients.
- 02
The coordinator's copy
A second invite with its own UID and a technical organiser, which the coordinator can accept into their own calendar like any other meeting.
- 03
Updates
Editing the event resends both copies with the same UIDs and a bumped sequence number, so the meeting updates rather than duplicating.
- 04
Cancellation
Cancelling sends a CANCEL for both copies. That is why permanent deletion requires cancelling first — otherwise the meeting stays in everyone's calendar with nothing left able to withdraw it.
SMTP and the ICS standard. No add-in and no application permission.
- Microsoft Exchange
- Outlook
- ICS
- SMTP
A meeting in a calendar
With the hosts, the owner, the operator, the ticket number and a full description — rendered from one template that also drives the email and the ticket.
Show us your worst window.
Bring the one that keeps slipping. Thirty minutes, your estate, no slides.