We are a coaching company which offers coaching classes that are conducted over zoom. As part of our administration, we have a system which assigns coaches to our classes, by creating a zoom meeting and then assigning the coach as the host for the meeting.
The way that we have implemented this is that we use a single account to create a zoom meeting and assign the coach as the host. Most of the time, this system works OK, but on some days, we try to create and assign more than 100 meetings and coaches in a single day, which means we hit on the limitation as described here:
Because the assignment is centralized (that is, our administrators assign the coaches to particular classes based on availability, history teaching similar classes, etc.) the coaches can’t assign themselves so there’s no way to get around using a centralized account like how are are doing it now. We also do sometimes change the data after the fact (for example, to assign a different coach or set another coach as a backup coach using the alternative_host setting).
We can manage around this by (for example) keeping ourselves limited to just 100 classes per one day, and then setting the remainder on the following day, but this method introduces a manual step that isn’t strictly needed and can lead to operational mistakes on our end. So we want to set things up so that the administrators of the system can set more than 100 classes in a day without needing to resort to this.
The only way I could think of to come around this was to have a few administrator accounts (administrator+1, administrator+2, administrator+3, etc.) and then use these accounts round robin, but that feels very hacky.
(Of course, the easiest solution would be to just increase our API limit to a few hundred for the administrator account that we’re using, but I’m not sure if this is possible or not. I already tried contacting our sales representative, he directed us to here.)
Is there a recommended way to do what we want?