What do you like best about RegFox?
I discovered Reg Fox while searching for a flexible ticketing platform that could meet my needs as the organizer of a photo interest group. I needed something straightforward to use, since I run two to four events each week, but I also required features that my previous solution no longer provided. My essential requirements included some CRM support so I could manage my own mailings, low fees to keep my events affordable, the ability to richly format event pages with headers and embedded graphics to make invitations more appealing, and support for both virtual and in-person events. Additionally, a waitlist feature was crucial so that if anyone dropped out, I could quickly fill their spot and maintain a fully booked event.
I was able to set up my first event in under 20 minutes, and over the past few weeks, I’ve started creating a variety of additional events. As with any new tool, there’s a learning curve, but I found most features quite intuitive. I was especially impressed by the level of support. The built-in AI chatbot, Finn, is highly effective. Not only can the AI answer specific questions about any screen, but it can also suggest better approaches for particular objectives. If I got stuck, I could even share a screenshot, and Finn would read what was on my screen, interpret my notes, and confirm whether I was in the right place and what to do next. On several occasions, human support staff also stepped in to provide extra help, such as sharing insights about the product’s direction or agreeing to pass along feature requests to the development team.
Overall, I’m very impressed. RegFox is a robust, feature-rich platform with a great deal of versatility, making it suitable for a wide range of clubs, groups, or organizations looking to manage registration and ticketing for their events. Review collected by and hosted on G2.com.
What do you dislike about RegFox?
I use Reg to organize frequent photography workshops, many of which are quite similar. The platform allows me to easily clone events, but I’ve noticed that the details carried over from one event to the next require careful review and adjustment. I often have to update several elements each time I duplicate an event. If there were additional ##keywords such as ##eventdate, ##eventstart-time, and ##event-title, it would make templates like the confirmation email and waitlist notification much more reusable when copying events. Review collected by and hosted on G2.com.