Hello! We are about to start our first round of event cancellations for the 20-21 season using WordFly’s integration. I am curious how others have managed communicating multiple show cancellations using just one Page dedicated to cancellations.
Hi Sarah,
Depending on how many events you're cancelling, and the complexity of the options you're providing, one con I can see would be a Page that's somewhat complex for the customer to navigate.
In a perfect world Pages would support dynamic content and data fields but, since it doesn't at this time, we chose to create a different Page for each of our package types. We ended up with 14 in total! It actually wasn't too bad to build them all though. Because a lot of them were just variations on each other, I was able to make liberal use of the duplicate page functionality and then just make minor adjustments. One of the benefits to this was that we were able to use messaging that was unique to each package type. On the Tessitura side, everything is connected to CSIs so we can fully track all responses as well. One of the cons to our approach, aside from building 14 Pages, is that when we built the emails that went out to our subscribers we had to be very careful when it came to inserting the correct URLs. Testing was somewhat time consuming all around.
I'd be most interested myself in knowing if anyone has done this sort of thing successfully with only a single Page (or just two or three).