Spread office-hours signups across your hosts
Each office-hours signup books the next available host on a round-robin event type, so nobody balances the rota by hand.
New Submission on your "Office hours signup" form
Create a booking on a team round-robin event type so the next available host is assigned automatically
One-directional. A submission triggers the action — nothing is written back into your form.
Office hours break down when one host quietly takes every session. A round-robin event type hands each new signup to whoever is next in the rotation, and the signup form stays the single thing a student has to find.
Course teams, tutoring services and community programmes work this way because the alternative is a shared inbox and a volunteer who says yes too often. What the student needs help with rides along into the booking, so the assigned host can prepare, or swap with someone who knows the topic better.
Setting it up
- 1
Copy the Tutoring Inquiry Form template and add a slot question listing the office-hours windows you actually run, so students choose from the rota rather than any hour of the week.
- 2
In Cal.com, create a team event type with round-robin assignment and add every host who covers office hours.
- 3
Check each host's connected calendar and their availability inside the team, since round-robin can only skip people Cal.com knows are busy.
- 4
Set the event type to your standard session length and add a buffer, so back-to-back sessions do not run into each other.
- 5
Build the Zap on formformform's New Submission trigger and select the signup form.
- 6
Add the Cal.com booking action, choose the round-robin team event type, and map Student Name and Contact Email into the attendee.
- 7
Send Subject(s) into the booking title and the help and availability answers into the description, so the assigned host knows the topic before opening the response.
- 8
Book two test sessions in a row and confirm they land with different hosts before switching the Zap on.
What maps where
Using the Tutoring Inquiry Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Cal.com |
|---|---|
| Student Name | Attendee name on the office-hours booking |
| Contact Email | Attendee email; Cal.com's confirmation names the assigned host |
| Subject(s) | Booking title, after the event type name |
| What does the student need help with? | Booking description the assigned host reads before the session |
| Availability | Booking description, for arranging any repeat sessions |
| Format | Booking location — in person or online |
Variations worth knowing
Run a Zapier path per value of Subject(s) and point each at its own team event type — maths hosts on one, writing hosts on another. Each still rotates internally, so load spreads inside the right group of people rather than across everyone.
Cal.com's booking limits apply to team event types as well. Set a weekly maximum so the rotation cannot hand a heavy week to one volunteer; once the cap is reached the Zapier run fails, which is your signal to add another host.
If something isn't arriving
Round-robin only distributes among hosts Cal.com considers available. If the others have not connected a calendar, or have no availability set inside the team, they are skipped every time. Check each host's schedule on the team event type before blaming the Zap.
The action is pointed at a personal event type rather than the team one — the two look alike in the Zapier dropdown. Re-select the round-robin event type in the Cal.com step, then re-test with two submissions to confirm the rotation moves on.
Frequently asked questions
Can students see which host they will get before they book?
No. Cal.com assigns the host when the booking is created, and the form has no view of the rota. The confirmation email names the host, so a student finds out straight after submitting rather than while filling the form in.
What about a student who needs the same host every week?
Round-robin always picks whoever is next, so a fixed pairing needs its own route. Add a Zapier path for returning students, matched on their email address, and point it at that host's personal event type instead of the team one.
Do hosts need their own Cal.com accounts?
Yes, if they are to be part of the rotation. Round-robin assigns members of a Cal.com team, each with a connected calendar of their own. The signup form is unaffected, since it only ever talks to the team event type through Zapier.
Related automations
- Book a phone screen the moment a candidate applies
An application books a phone screen on the recruiter's event type, with the candidate as attendee and the role in the booking notes.
- Book a sales demo when someone requests one
Each demo request creates a booking on your sales demo event type, with the prospect as attendee and their chosen slot as the start.
- Book an onboarding kickoff for every new account
A finished onboarding questionnaire books the kickoff call, with the account name and first-30-day goals in the booking description.
- Turn callback requests into on-call bookings
Every callback request becomes a Support call booking, with the issue in the notes and a real slot instead of a queue position.
- Turn qualified consultation requests into discovery calls
Consultation requests that clear your budget threshold book a discovery call, with the challenge and budget already in the notes.
- Add service appointments to the dispatch calendar
A booking arrives and lands on the dispatch calendar with the address as a map pin and the job in the title.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free