Posted: November 27, 2021 at 9:13 am
|
Hey guys, I messaged directly about this a few months before Covid hit. A company whose name I won’t post here because this is not about promoting one specific company; approached us about offering “ticket refund insurance” to all of our attendees. For a fee of a couple of dollars per ticket they would offer insurance to every single attendee where if they decided to cancel their ticket for any reason they would receive a full refund, not from us but from the insurance company. The only hurdle to us providing this insurance to our attendees is the insurance company’s API needs to integrate with EE. In today’s Covid world, THIS HAS TO BE THE SINGLE BIGGEST FEATURE YOU COULD OFFER US AS EVENT ESPRESSO USERS. Having now cancelled or postponed 5 different events over the last two years and the very real possibility that it could happen to any event we hold at any moment for the foreseeable future being able to provide this ticket insurance would be a huge benefit to our business and our customers. It would allow attendees to register for an event taking place months or even a year later with confidence in knowing if the event were canceled or postponed due to Covid they would get their money back. I am sure most of your customers you have has had a similar experience and has had to cancel at least one event due to Covid. I am happy to post the name of this particular service here if you like or email directly, but please please please research how to do this with someone to help our events. Thanks for listening. |
|
|
Hi there, First, thank you for posting this, which I have noted as a feature request. Whilst you haven’t asked for my own personal opinion on this we’ve had a few discussions previously and I think you are open to them. So I’ll add my thoughts but prefix it with the fact that these are my own personal opinions on this and should not be considered an official EE response (afaik a discussion on this feature hasn’t happened, so we don’t have an official response here). Whilst I fully understand the desire/need for a feature like this for some EE users, I think above you are basically asking the wrong people to create it. Event Espresso is essentially the ‘wrong side of the fence’ for a feature like this as the company that will benefit the most from pretty much all of the work put in is the insurance company. EE as a team, are relatively small and put a lot of work we put into Event Espresso’s features, there’s a LOT of planning, development, testing and discussions that the majority of users will never get to see. So pulling the team off some of the most requested features to work on a feature in which another company sees the lions share of the benefits seems a little backwards to how it should be (to me). Taking into consideration that integrations like this often require a fair amount of support and maintenance to make sure it keeps in line with any changes made by the 3rd party and it starts to become less of a ‘nice’ feature to implement from this side. Now, having said all that, there is nothing stopping the/a insurance company from building their own integration for Event Espresso or this could also be a good project for a 3rd party developer to create. EE has a huge number of hooks within the code so pretty much anything they would need to do can likely be done without the need for EE developing their own solution. I’m sure some will disagree with me on the above but it is always a balancing act for current features, new features, support requirements for both and demand for specific features. Features that sound great on paper can pull the team from another and or cause complications further down the road and that’s all taken into consideration with each possible new feature. |
|
|
Hi Tony, Thank you for the reply. In fact I already have an insurance company ready to build this integration. They have already built it with several other registration platforms. They just need someone from your side to coordinate with. They will do all the work. Again, I am not posting their name because I am not trying to promote someone else’s business here. My goal is to help my own business and I think most of your other event organizer customers. I completely understand you guys have a ton of components to EE and need to focus on the features that benefit the majority of your users and make the biggest impact. I think this is one of those things and as I understand it would not take that much effort from your side. I am happy to make introductions as soon as anyone on your team says go. Thank you! |
|
If that’s the case then all they really need is the Github repo for Event Espresso: https://github.com/eventespresso/event-espresso-core But then that repo isn’t hard to find, a quick search would have gotten them to it so I’m not sure what other info they would need from our end if they are looking to build the integration?
You’re welcome to post the name here, if they created an add-on for this we would likely link to it when users asked about this feature anyway.
I understand what you are trying to do, but ‘most’ of our other event organizers have not requested this feature so I’m not sure the demand is that high. I checked and there have been less than 10 requests for ticket/registration insurance options since the beginning of EE4.
If the developer of this add-on creates an issue on the Github page of what it is they are looking for from us we can get a better idea of what this project requires. Without this coming across the wrong way if they are committed to building this add-on then I’m not sure why haven’t checked the GitHub repo and started this already? For example, if I were making a custom add-on for another plugin I’d be checking the code to see if it could do what I wanted it to do and then creating an issue on that plugins repo for whatever I couldn’t find myself or requesting an additional hook if it didn’t have one for what I need. So if this company is wanting to build the add-on themselves I guess I’m confused as to what it is they need to coordinate with us. Note that I’m not saying we wont open a discussion with them but I’m not really sure why, if they are willing to build the integration themselves, they are apparently waiting on collaborating on us to do so? |
|
The support post ‘Integrating with a ticket refund service. BEST FEATURE YOU CAN OFFER US.’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
