Using Calendar Update to communicate changes to Calendar Snack Invitees
We do all the hard work in the background and send out the updated Calendar Invite information to your customers who have said Yes or Maybe.
Using the original calendar invitation in your calendar client, you can now update any of the information in your calendar snack event, and your customers will receive the updated data automatically in their Calendar Clients.
We support Subject, Date, Time, Google Meeting, Zoom Meeting, and Description fields for UPDATE.
When you save the changed information in the calendar client, we send out the updated calendar invite to any attendees in the Y or M category.
We mimic how it works with the calendar client, bypassing the need to log in. We keep the service Headless.
In this example, we will show you how Calendar UPDATE makes the process transparent to your end users who have said Yes or Maybe to the event.
So we start the story with a Calendar Snack Lander that was shared already. Two people put emails into the modal, got the Calendar Invites, and responded back.
Greg shares the URL to the Calendar Invite Landing page, and a couple of people get calendar invites and respond to the event in their calendar clients.
In this example, the organizer Greg sees in this report that two people have opted into the shared Calendar Landing Page and have been sent a calendar invitation by confirming the detailed reporting page.
In the detailed dashboard, Greg sees the names of the people who have said they are coming to the event and requests the detailed report to his organizer’s email address.
Greg, the organizer, realizes the event is now changed, and he must notify his current customers that the information has changed.
How does he do this if they have responded to the event?
Easy, he goes back to the original Calendar Event on his calendar, edits, and saves the calendar invite, which starts the UPDATE workflow in the background.
In this workflow, the customers receive updates in their email boxes with the new information in the calendar invitation, which asks them to respond since it involves time and location changes.
In his calendar client, Greg has changed the time to 5:15 and the location to the Colorado School of Mines. The Calendar Landing page is updated each time there is a change pushed.
So if someone were to get the new calendar landing page, they would get the correct calendar invitation.
But wait!
What happens to those who already responded to the original calendar invite for 3:30 PM at the Golden Hotel for Buffalo Bill? What happens to them?
See below what it looks like to your customers.
In this case, Mandy@techvader.com gets the updated calendar invite, asking her what her status is now, knowing the time and location have changed. (Orange A in UPPER Right is for Amanda).
Mandy sees a big time difference. She indicates Maybe instead of Yes for the 3:30 request.
Zack below is in a different place. He was a MAYBE before, but now sees this as an advantage and says YES to the Invite.
So what’s going on in the back reporting engine? Can Calendarsnack dynamically deal with all the changes? Absolutely!
What? Does that sound crazy?
Well, not really. We follow the calendar specification for sending, updating, and communicating with the calendar clients. CHANGES and UPDATES happen automatically across any of your active events.
So let’s see what’s going on with the detailed reporting below with Updates.
All updating is working as indicated by the detailed reporting.
It includes details like below.
So in wrapping up this TL: DR.
How else can I use the UPDATE to help promote my event?
We see it as a way to send out UPDATES in the description area, Dates, Time, Location, or the Google or Zoom Webinar Info if there is a change.
Also, another excellent use case is sending out the UPDATE with the Final AGENDA, or QR code for Coupons for attending, or other trade tricks to ensure people show up.