Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
2022-04-03 11:20 AM - edited 2022-04-03 11:21 AM
Hmmmmm... Can't quite figure out this one. I'm licensed and paid for the ability to host webinars, probably just like a billion other people before me have done. So I'm thinking it's all done and settled and this is just flowing like clockwork. Then I go to my website and program in a test webinar. It's seemingly all set up correctly with godaddy. I input my Zoom account info such that webinars that get signed up for on my website are sent to Zoom automatically. So I basically register myself for one of my own test webinars. I then switch tabs to my Zoom account and see that, instead of a webinar being created, Zoom has instead created me a meeting.
So, basically, what starts out as an attempt to generate a webinar from my website ends up portaling to my Zoom dashboard as a Zoom meeting.
Zoom chat help was no help at all. Zoom chat help says they will create a ticket, and that the engineering team hasn't created a patch or a work-around for this issue yet (which I found was really really odd).
Any ideas?