I'm the co-founder of SeatGeek, a website that provides price forecasts for sports and concert tickets sold on the secondary market (sites like StubHub, eBay, etc).
Currently we have one type of alert, a "Price Forecast" alert. Here's the basic idea: If we're forecasting a price decline for a certain event a user would want to wait to buy till the price drops. So they could sign up for a Price Forecast alert, and we then email them at the optimal time to buy (when the forecast changes to an increase). Pretty straightforward.
But now we want to add a second type of alert, a "Price Level" alert. The basic idea of this one: let's say a user wants to go to a certain event, but is only willing to go if he/she can get tickets under $40 in section 200. If there are no tickets currently available that match those specifications, the could sign up for a "Price Level" alert, and we'll then email them if tickets matching their specs become available.
In summary, our current alerts look at meta-trends for an event, and our new alerts look at individual ticket listings. We think that both alerts are useful. But we're concerned that presenting users with two types of alerts will be overly confusing. The difference between the two isn't super-easy to grasp. If people see two buttons, one saying "Price Forecast Alert" and the other saying "Price Level Alert", I don't think they'll know what the hell we're talking about.
How should we package this and present it to users? Should we keep two separate alert types? Should we somehow combine them? Should we just eliminate one?
