Hi everyone,
I’m positive it has to do with the code and procedures we’re using to pull our renewal data, but I’ve been asked to get a show of hands if anyone has ever had the same problem as us: if a subscriber has a package that straddles price zones (one seat is in zone a, and one seat in zone b), we are getting an incorrect price on our renewal form. I assume if you ever did have the problem, it’s something you fixed with a code re-write/revised renewal form procedures. But, I think it might make my team feel better to know that it’s not a unique problem, or if there’s a magic fix other than revising how we currently do things.
Cheers, Kathleen