際際滷

際際滷Share a Scribd company logo

How do I send a Billion Calendar Invites to a VIP List.pdf

31events.com
31events.com

The document discusses how the Simple Invite Service (SIS) APIs can be used to send calendar invites at scale through AWS services like S3, Lambda, and Simple Email Service (SES). The SIS APIs allow uploading of email lists, creation and storage of calendar invite objects in S3, processing of invites through Lambda, and sending via SES. Metrics on RSVPs and status updates can then be tracked and reported. A sample application called VIPLst is described that utilizes the SIS APIs to send calendar invites to webinar registrations as an alternative to email reminders.

1 of 15
Download to read offline
1 How do you send One Billion Calendar Invites on AWS? The Simple Invite Service (SIS) is a set of APIs that assemble calendar invites in AWS and hand them off to AWS Simple Email Service (SES) for Calendar Invite sending and RSVP tracking. Its a whole new channel category for digital marketing on AWS SES. For this blog post, we review how we built a VIPLST application with the SIS APIs to visualize the calendar invite-sending scenarios on SES. We create a calendar invite, send it to an email address box in AWS, and store it in S3. The calendar invite data is harvested for transport on SES using an automation routine we built on Lambda. We support injecting millions of calendar invites into S3 to store and forward the calendar messages as needed into SES sending. In addition, we can create calendar invite messages inside AWS with our automation process using voice prompting to convert calendar invites for SES workflows. In this demo, the customer logs into a VIP LIST dashboard to select which event they want to send calendar invites to from the customer email list they upload. We track the RSVPs and provide updates to anyone who has received the calendar invite as part of the messaging workflow in the APIs. If you want an API key to send calendar invites from your AWS SES account, email our trusty robot at zack@techvader.com.
2 I wont get into the gory details. Lets just say we can scale in AWS on SES. You check out our stack here as well with our consumer sample platter here https://calendarsnack.com
3 The VIPlst product is built to send a calendar invite instead of a email reminder In this example the use case is for registration emails to a Webinar. Instead of sending an email to remind customers to attend the event, we enable a single calendar invite to be sent, updated, and tracked using the app built with AWS using a email list uploader. Step 1 was trying to figure out how to build a client to get the data into the AWS
4 We eat the calendar data off your calendar invite when sent it to us at create@calendarsnack.com. That starts the automation process. We take that data and display it in the dashboard so you can select which event you want to attach your VIP LIST of names to send a calendar invite. Once the calendar invite is sent to the list by SES, we track the RSVP data and update it each time its changed in the SIS dashboard and to any customers that have received the calendar invite from SES. Use create@calendarsnack.com to get the event to your dashboard The VIP dashboard is your command center for sending calendar invites to your VIP Lists and tracking the RSVP receipts.
5 We provide a messaging layer for update as part of the API stack You can change any created event details in the calendar client you sent to the calendarsnack service. When you save those changes in your calendar client, they will flow to the SIS APIS to the Dashboard and anyone who has received the calendar invite already. The SIS APIs provide a steady state to the service and act as a messaging layer in and out of AWS in this use case.
6 Prep is easy using a TXT File for Uploading VIPlst Prep Save the file as. TXT extension and use commas between the emails. Click the Choose File and Upload. The loader will automatically parse your list for you. You can also use the save as a . CSV option for a more extensive list.
7 Independently, the workflow would accommodate a data feed from SQS and SNS notification from AWS Pin Point to send the calendar invites from your AWS journey maps for current SES automation workflows to send calendar invites. This is the step from the List upload to picking your event All your events in the future will end up on the picker list. Once you upload the list, you can select the one event to send calendar invites to.
8 This example is for 500 calendar invites in a batch file to SIS and onto SES
9 This Dashboard has 60+ Events to send Calendar Invites to a list
10 The List Picker emulates the dashboard to select the event
11 3 steps to getting a VIP List sent This part of the application highlights the power of putting events onto the Dashboard using your Calendar Client, then uploading your list and sending the batch of calendar invites in a few minutes to your webinar registrations. The benefit? Youre not sending 4 Email Reminders to an event. Its on the customers calendar and you are tracking it in the dashboard. You can send updates if you wish along the way directly to your customers calendar. Imagine this in an automation routine in AWS PinPoint to send calendar invites as an alternative channel to millions of email reminders?
12 The Simple Invite Service is built as a group of APIs The SIS APIs use your Email List to create a connection layer for sending and tracking actual calendar invites for RSVPs across your campaigns sent through the AWS Simple Email Service.
13 Workflow for Update or Cancel Think of SIS as steady state messaging system inside AWS as a virtual calendar server, updating and collecting RSVPs for the Simple Email Service.
14 We collect and analyze for the individual user event data and the domain data for all users in that domain Reporting is inside the S3 bucket and is visualized here into detailed workflows using the VUE3.JS application we built. The detailed data is sent when the Invitee Report is requested. We also support reporting views in AWS Quick Sight as an option.
15 Detailed Calendar Invite reporting in each of the provisioned accounts https://youtu.be/Fw-rUICG9JQ?si=vKRP4iPmZ8IuvAhI Please reach out if you have any questions to me at greg@techvader.com or my robot son zack@techvader.com. https://calendarsnack.com

More Related Content

How do I send a Billion Calendar Invites to a VIP List.pdf

  • 1. 1 How do you send One Billion Calendar Invites on AWS? The Simple Invite Service (SIS) is a set of APIs that assemble calendar invites in AWS and hand them off to AWS Simple Email Service (SES) for Calendar Invite sending and RSVP tracking. Its a whole new channel category for digital marketing on AWS SES. For this blog post, we review how we built a VIPLST application with the SIS APIs to visualize the calendar invite-sending scenarios on SES. We create a calendar invite, send it to an email address box in AWS, and store it in S3. The calendar invite data is harvested for transport on SES using an automation routine we built on Lambda. We support injecting millions of calendar invites into S3 to store and forward the calendar messages as needed into SES sending. In addition, we can create calendar invite messages inside AWS with our automation process using voice prompting to convert calendar invites for SES workflows. In this demo, the customer logs into a VIP LIST dashboard to select which event they want to send calendar invites to from the customer email list they upload. We track the RSVPs and provide updates to anyone who has received the calendar invite as part of the messaging workflow in the APIs. If you want an API key to send calendar invites from your AWS SES account, email our trusty robot at zack@techvader.com.
  • 2. 2 I wont get into the gory details. Lets just say we can scale in AWS on SES. You check out our stack here as well with our consumer sample platter here https://calendarsnack.com
  • 3. 3 The VIPlst product is built to send a calendar invite instead of a email reminder In this example the use case is for registration emails to a Webinar. Instead of sending an email to remind customers to attend the event, we enable a single calendar invite to be sent, updated, and tracked using the app built with AWS using a email list uploader. Step 1 was trying to figure out how to build a client to get the data into the AWS
  • 4. 4 We eat the calendar data off your calendar invite when sent it to us at create@calendarsnack.com. That starts the automation process. We take that data and display it in the dashboard so you can select which event you want to attach your VIP LIST of names to send a calendar invite. Once the calendar invite is sent to the list by SES, we track the RSVP data and update it each time its changed in the SIS dashboard and to any customers that have received the calendar invite from SES. Use create@calendarsnack.com to get the event to your dashboard The VIP dashboard is your command center for sending calendar invites to your VIP Lists and tracking the RSVP receipts.
  • 5. 5 We provide a messaging layer for update as part of the API stack You can change any created event details in the calendar client you sent to the calendarsnack service. When you save those changes in your calendar client, they will flow to the SIS APIS to the Dashboard and anyone who has received the calendar invite already. The SIS APIs provide a steady state to the service and act as a messaging layer in and out of AWS in this use case.
  • 6. 6 Prep is easy using a TXT File for Uploading VIPlst Prep Save the file as. TXT extension and use commas between the emails. Click the Choose File and Upload. The loader will automatically parse your list for you. You can also use the save as a . CSV option for a more extensive list.
  • 7. 7 Independently, the workflow would accommodate a data feed from SQS and SNS notification from AWS Pin Point to send the calendar invites from your AWS journey maps for current SES automation workflows to send calendar invites. This is the step from the List upload to picking your event All your events in the future will end up on the picker list. Once you upload the list, you can select the one event to send calendar invites to.
  • 8. 8 This example is for 500 calendar invites in a batch file to SIS and onto SES
  • 9. 9 This Dashboard has 60+ Events to send Calendar Invites to a list
  • 10. 10 The List Picker emulates the dashboard to select the event
  • 11. 11 3 steps to getting a VIP List sent This part of the application highlights the power of putting events onto the Dashboard using your Calendar Client, then uploading your list and sending the batch of calendar invites in a few minutes to your webinar registrations. The benefit? Youre not sending 4 Email Reminders to an event. Its on the customers calendar and you are tracking it in the dashboard. You can send updates if you wish along the way directly to your customers calendar. Imagine this in an automation routine in AWS PinPoint to send calendar invites as an alternative channel to millions of email reminders?
  • 12. 12 The Simple Invite Service is built as a group of APIs The SIS APIs use your Email List to create a connection layer for sending and tracking actual calendar invites for RSVPs across your campaigns sent through the AWS Simple Email Service.
  • 13. 13 Workflow for Update or Cancel Think of SIS as steady state messaging system inside AWS as a virtual calendar server, updating and collecting RSVPs for the Simple Email Service.
  • 14. 14 We collect and analyze for the individual user event data and the domain data for all users in that domain Reporting is inside the S3 bucket and is visualized here into detailed workflows using the VUE3.JS application we built. The detailed data is sent when the Invitee Report is requested. We also support reporting views in AWS Quick Sight as an option.
  • 15. 15 Detailed Calendar Invite reporting in each of the provisioned accounts https://youtu.be/Fw-rUICG9JQ?si=vKRP4iPmZ8IuvAhI Please reach out if you have any questions to me at greg@techvader.com or my robot son zack@techvader.com. https://calendarsnack.com