Best way to manage Exhibition/Conference attendees

Question

Hi, 
 I am looking for best practices for managing conference/exhibition attendees. 
 The use case is simple: Our SDRs meet with prospects (who may or may not exist in the CRM) at physical conferences. They may have different types of interaction: simple presentation, demo, quote, etc.). 
 At the end of the day, I want us to be able to quickly see who met with which prospect, who the top performers are, what type of meeting is most represented (demo, quote, etc.). 
 I see one way: SDR creates a Meeting, selects the show from a multi value picklist, then select the type of interaction in a multi value picklist (demo, quote, etc.) records the meeting. 
 Do you have any best practices to share? 
 Thank you! 
 PS :T o give some context, in my previous company we were using Salesforce, the campaign module allowed us to quickly define the exhibitions + the type of interaction on our booth.

Thomas Rei · Accepted Answer

Hi Thomas Rei , 
 we have done it with two custom modules (all by ourself with the Module Builder in Sugar): One is called Touchpoints and contains just like Francesca's module all Events and contact forms etc. The second is called Interactions. It contains the specific visits or, well, interactions of contacts with the Touchpoint. The Interaction is related to contacts, leads and targets, and when leads are converted, we convert the Interactions with it. So on the contact/lead page you have a detailed list of all Interactions of this contact/lead where you can exactly see the timestamp of the visit, the event, if the contact was completely new or already known etc. Also, the cool thing is, that even if you convert a lead, the interaction counts only once. When reporting directly on contacts or leads you would need two separate reports - for us, we can only do one report on Interactions and can exactly see how well the event or other Touchpoint performed. 
 In the description there is a lot of space for all additional info and via the Assigned to field and a status field just like in Tasks we can assign those Interactions after events back to a specific person, if someone else entered them. With the Sugar mobile app, you would also be able to create them right at the event. If you'd like, you could for example define standard values for the desciption with the most important questions, so that your Sales Reps only need to add the answers ... there are a lot of possibilities. 
 So, our construct consists of the two modules and several 1-to-many relationships, where the M-side always is the Interactions module - as I said, to Touchpoints, Contacts, Leads and Targets. 
 Maybe that helps. :)