Back on June 23 I posted about problems I was having with a client's WebEx Event Center webinar. Registered attendees did not receive reminder emails through the WebEx system. I can now report the successful resolution of the issue.
If you encounter a similar problem, have your designated WebEx account administrator log into Site Administration. Look under "Configuration - Common Site Settings - Options" and scroll down to "Default Scheduler Options." There is an On/Off setting for "Meeting email reminders (MC, TC and EC)." Make sure the option is set to "On".
That seems simple enough, but I experienced great frustration in dealing with WebEx technical support representatives in tracking down the root cause. My first rep told me that I had simply forgotten to check the boxes to send reminders in my event setup:
We went back and forth on this contention, and I finally managed to convince them that I had the event reminder boxes checked by creating a new event and taking a snapshot as above. So they asked me to look at the master account administration options. Changing it to ON seemed to work, but then another Senior Support Engineer was assigned to the case and he wrote:
"The Meeting email reminders (MC, TC and EC) setting only affects HOSTS, that is, only hosts will receive the reminder emails for meetings. Attendees reminders can only be configured for Event Center Sessions when scheduling them, this option can be found at the bottom of the page."
So we were right back to square one. It took me additional tests on my account to verify that the account admin option was indeed blocking or permitting the attendee reminders to go out. Having it set to OFF overrode any checked settings in the event itself.
I don't believe this is how it used to work, as I know my client had not changed their master account admin options, and reminders used to go out on our events. The parenthetical text on the admin options also seems to indicate that WebEx expects the setting only to be a default that can be overridden in the event. But I have no way to prove previous vs. current behavior and no interest in playing with it anymore.
I'll just put the solution out there in case it helps someone with similar problems.