This is a great idea. Some additional points to consider:It is worth mentioning too that keeping the .ics file download is also worthwhile as this provides greater compatibility and flexibility for more attendees, with different email systems/applications. I have seen other organisations send both in their event confirmation emails before e.g. Asana.Importantly, the attendance tracking features should remain e.g. auto check-in when users click their unique join link. These details should ideally be embedded into the email body.The other feature that would compliment this is to send calendar updates when event fields like the title, dates or other critical information changes. Similar to how the Outlook meeting invite function works now. Again, configuration should control if this is automated and if not, give the end-users the ability to craft journeys to explain the change, so it is done in a controlled/deliberate way.Another configuration that should be available, is to select which email address the invite comes from, so that shared mailboxes can be managed by more than one staff member if required and to present a more professional face to attendees. In some instances, you don't want an individual mailbox email and details to be visible to attendees for an array of reasons e.g. privacy, security etc.It would be a good feature to make configurable, so users/organisations can control which events have this enabled and which don't need it.