31Events OEM Starter Kit


At 31events.com we develop messaging technology that enables the RSVP calendar interface within email clients to track the responses of the individual event. The technology can be used for all kinds of use cases for time-based events across vertical markets.   

This gives every marketer the ability to communicate directly with a customer’s calendar. When a calendar invite is sent, it is correctly displayed in the message body to be read in the correct client format for webinars, promotions and attachments such as coupons. 




The Calendar Snack package has been designed for marketing agencies and software OEM’s that want to add value through the ability to send and track calendar invites in an easy way by integrating them into call to action campaigns with a managed service.  The web service supports calendar message building, message sending and RSVP’s return receipt reporting.

The calendar invites can be emdedded into web pages and popular email packages like Mail Chimp using the code generator. The calendar invite data is available in a reporting interface for all RSVP’s providing granular details for your marketing campaigns.

Example of the Event Summary.




The components of the messaging solution are using Amazon Web Services S3, SES, Dynamo DB, SNS and API gateway to process the calendar invites with our custom developed proprietary Lambda functions.   The solution design is “Headless”.  This means you have no Create, Read, Update, and Delete or (CRUD) for the Calendar Invites. The customer sends you an calendar invite off their native calendar client to your branded domain email address. That message is sent to us and we re – generate a packaged calendar invite complete with instructions on how to use and test the calendar event with details of the code embed for web pages and email call to action embeds.  Once that process is complete – which just takes a few seconds to complete, we sent a confirmation email to the event organizer from the Calendar Invitation with all the details.  

Example of the event confirmation email once the customer sent us a Calendar Invite below.



The calendar event payload includes Snack Summary, Invitee Details, Get Code and Send a Test that are auto generated each time by our web service by sending an email to your domain address mail box setup to process the Calendar Snacks.




We generate code for each calendar event which is packaged into the Calendar Snack payload.  

Example of the GET CODE feature for calendar invite web page embed. 



Example of the GET CODE feature for Mail Chimp embed.


Send a Test feature is included into each CalenderSnack email for a quick review.  If you don’t like it after testing the calendar invite, then you can adjust your event on your native calendar client and send another request to get a Calendar Snack.  Simple and easy for the marketeer and software OEM to integrate as a service. 
 



The entire solution delivery can be rolled out in less than 1 week under your AWS account with your branded domain. We can also manage the solution for you if you don’t have the resources. 

For details on how easy solution can be packaged see CalendarSnack.com and check out the detailed documentation here.  If you have any questions or need a quote please contact us on Drift @ 31events.com. 

Calendar Snack Documentation

CalendarSnack Mail Chimp CTA released


We just released the Support for MailChimp Integration. You take the code from our Calendar Snack page by clicking the code button and embed that into your Call to action for one click Calendar Invite signup from your email campaign and we track that for you in the Calendar snack report.   This is designed to be free for you to use for any promotion.  1 Click Calendar Invitations in Web and Email embeds in less than 3 minutes!

Calendar Snack Per Event Reporting in 30 Seconds




Arnie has updated the front end now to include an auto generated report URL landing page for the Calendar Snack that is sent with the introduction email when you invite us to your event off your Google Calendar.  Its simple.  Step One – Invite us off your Google Calendar. Step Two – You will receive an auto generated email from our AutoBot (Named Cooper), and the email will have your Calendar Reporting URL in it. Follow the directions and you will be monitoring your event in 30 seconds,   PDF Calendar Snacks.




CalendarSnack.com DIY Web Form Video’s Released

( Thanks Arnie for the Cool Banner – BTW ) .


We launched just a few days ago and are receiving good feedback.  We are working on the the various embedded Modals for Web page insertion to be auto generated.   We have to figure out the hard stuff first and have been busting down the Calendar Clients into smaller pieces using ERE’s and Lambda’s to help accomplish the complicated tasks of the various clients to use calendar create and calendar consumption persona’s for the various devices.  

In addition we did a recap this weekend of our beta release with some You Tube Video’s that can be found on the CalendarSnack.com site here.   This series is focused on how to build out your own Web Form in Word Press and insert the CalendarSnack Event code into a Calendar invitation form for self enabled invitations off any web property to amp up your attendance.  The form allows a customer to send a calendar invite directly to their calendar and we track that for each one off event for the marketeer providing rich detailed big data of the event. 

Check out the Videos here: 


Calendar Snack Videos

Live 31events reporting review on Calendar Snacks

Hello.  We just published this preview today. Shows a quick view of our technology and how our Calendar reporting engine works on a per event basis.  See here on You tube. 

Calendar Snack Preview Details

Hello – I thought I would get out a quick post and give you and update as of July 15.  We completed numerous hurdles this weekend. We have cemented some repeatable install approaches that take less then 5 minutes to get rich reporting working for your calendar invite.  See here to download the preview calendarsnack.com debrief. We will be be launching soon!


Calendar Invites at scale on AWS

So I started off my ISV journey 7 years ago.  Just an innocent attempt to get people to my events by sending them a Calendar Invite.  If they accepted, I knew that they were coming.  Or at least had a better chance of showing up to my events.  Along the way I had a Web based Calendar engine built by a local contractor on an old Cold Fusion stack.  It worked and we were off on many use cases on how I thought it should work.  Some 2200 hours of personal time in testing, UI design, and disastrous blunders on my part as a weekend and after work project I needed break.  If this was going to be bigger idea I needed help.  Enter a friend named Arnie.  Arnie came into the calendar “Thunder Dome” 2.5  years ago.  Or about 1800 hrs ago.  It has been a part time project for him and he caught the bug as indicated that those hours are after work and weekends. 

He helped with so many things –  testing , coding , web site, blogging and overall front end animal.  I voted him to Co-Founder last year.  He is a true inspiration.  Then we decided to blow up the old site and start over -literally scrap all the code some – $80K in custom contract coding down the drain..  Not easy.  We were both at a loss for 60 days.  We knew after talking with several large test customers we needed to get to scale on AWS with SES. 



We then started our Pizza Journey into AWS in August 0f 2017.  About 3 months ago in February of 2018 we were fortunate to recruit Jonn , who is our lead developer and CTO.  We have been iterating using Slack, and brain storming on how to use SES, Python SDK, SNS, Lambda and Arnie’s Vue front end with his run time engine.  We have the prototype running now in AWS.  Pretty exciting to see the Pizza project running!  The test site will be up and running in a few weeks. www.calendarsnack.com. More to come as we attempt to give every marketeer in the world their own calendar server for sending and tracking of Calendar invites!

31Events will be re-launching soon …

May 3, 2018 / Arnie McKinnis  / 

To be completely honest, the last (almost) year has been tough.  We had a working version of 31Events – that accomplished the goal of sending a very well formatted iCal/ICS file, that could be “consumed” by all the major email & calendar clients on the market.  

it worked, but it wasn't scalable ...

So we had a decision to make – Either make the existing platform work or to completely re-invent/code to work within an ecosystem we knew would both (1) scale and (2) be around for a very long time.  

So we decided to burn it down, and start over.

Moving to the largest, serverless computing environment on the Globe

What we’ve learned in the process of moving from a Coldfusion/MSSQL environment, is that AWS Serverless Architecture gives us both flexibility with the ability to scale – without us having to manage any servers, storage, or infrastructure.  It’s been an interesting 9 months of learning for us — first, it’s a complete mindshift from our backgrounds (both Greg and I have spent our professional lives within “infrastructure” and services for large companies) in that we didn’t need to worry about the “backend”, that it would just work – regardless of what we wanted to do.

Second, it forced us to really think through what 31Events does – and start breaking it down into smaller and smaller pieces, because serverless architecture is about “micro” services and functions – no longer did we need to think from an end-to-end standpoint and create functions to handle it.  We now shifted to smaller functions.

Third, it forced us to re-think the front-end (user interface), and what we wanted to accomplish – first as we roll out Version 1, but also what we could do as we proceeded down the enhancement and development path.

It's like lining up dominos

I like to talk in analogies, it helps me put things into some sort of context and understand complex “things”.  To wrap my mind around the direction we had planned to take, I started thinking of our new AWS Serverless backend as setting up a dominos.  Our dominos can start off as a simple line … knock over the first one, and it just knocks over the next.  But as we learn and grown, we can add complex patterns, or create side tracks that go simultaneously. And each “domino” is a fraction of the whole, and if it breaks, we can go back to the specific place and fix it.  It really is a great way to create an application (which is what 31Events is) and have it work right from the beginning.

Right now, we are still working through creating our micro services, and we’ve made some significant progress in doing that.  Although the concepts are “easy” to understand, the implimentation is always going to much harder than originally thought.  

The other problem faced, as you march down this brave new world of serverless, is finding people who really (and I mean really) understand it – and can make it work.  We’ve been through a few people along the way, but hopefully have found the right team to help us going forward. 

When will it be ready?

We all have “day” jobs at the moment – so 31Events is a sideline project.  That doesn’t mean it’s not important (because it is, Greg and I both see examples every day where we could help people), what it means is that we can’t necessarily publish a roadmap with dates.  Our first priority is to ensure we have the same functionality we had a year ago.  After that, we will re-launch.  Because we know, once it works, it will just work regardless of how many  users we have creating and managing events & invitations.

We hope to be back with Version 1 by July – that would market a one-year absence of 31Events – but I’m not putting a timeline on it.  So, stay ready, because once we re-launch, it will just work – and you will then be able to send a calendar invitation to anyone, and will just work.

Because we are here to change the world of “Add to Calendar”.