event•hapily

A deal workflow action that would run when a contact is associated to a deal. If the associated contact is associated to a hapily event object, the workflow will automate the association of the deal to the event. The workflow action ideally would be able to have behaviors set that dictate which event to associate the deal to based on the contact. The options could be first event attended, latest event attended, all events, or some combination of those options. There would also be an option to choose how far back events took place that would allow them to be associated.

A paid add on to event hapily ($150/m) that allows you to create an "Event Lead Forms" from the Event level record, that helps you associate Contacts to events as "Event Leads". Functionality is similar to creating registrations except it does not utilize the registration object, it simply associates contacts to the event object with the label "Event Lead". Would pair very well with the automatic deal attribution workflows. When the Leads Object API create endpoint becomes available, we Could have an option on the workflow action to Create a Lead Object for the Contact as well with the name of the Event in it so reps can follow up w/ the Prospecting Tool. We could add in a Lead Object property called Event Name and Event ID and populate then when the lead object is made. Most people I show event hapily to keep bringing up the usecase of ATTENDING events vs HOSTING events. This could use the existing architecture built in event hapily, and take advantage of deal attribution. Allowing us to have a lower tier offering for folks who JUST attend events that need easy deal/event attribution but wont ever create registrants. This would be INCLUDED if someone buys a paid version of event hapily but would allow us to monetize it for an EASY use case at a reasonable price for folks who will never HOST events. We're leaving money on the table if we don't do it.

People want to check registrants in at events