Teams, routing forms and polls
Event types hosted by several people: collective (everyone attends) or round robin (one host per booking, fairly). Routing forms that book on submit, and group polls to find a time.
An event type can have more than one host. Pick who hosts it in the event type editor's Hosts section in the Calendar app, or with the API and the MCP tools below.
| Kind | Slots on the booking page | Who gets the booking |
|---|---|---|
Just me (solo) |
your free time | you |
Collective (collective) |
the times every host is free | every host: one invite lists them all |
Round robin (round_robin) |
the times any host is free | one host, picked fairly |
Hosts are members of your organisation. Each needs their own working hours in Calendar (Calendar → Availability). The event type stays yours: its lengths, buffers, notice, limits and questions apply to every host. Each host's own busy time counts, from all their connected calendars, in their own time zone.
Hosts from a team
Instead of picking people, a collective or round-robin event type can take its hosts from an org team: in the Hosts section, set Hosts come from to the team. The hosts are then the team's members (inherited ones included), in the order they joined, and the list follows the team: someone who joins starts hosting with the next booking, and someone who leaves stops. Members who have no working hours in Calendar yet are left out of booking instead of blocking it. Priority, weight, Max a day and the destination calendar stay per person, so you can still give one teammate more bookings than another. Set Hosts come from back to People I pick to return to a hand-picked list.
Collective
A collective meeting is offered only when every host is free. Each host's hours are worked out in their own zone, so when one host's clocks change and another's don't, the shared slots move with them.
The booking puts the meeting in every host's calendar and sends one invite that lists all of them. If two people book the same slot at once, one gets it and the other is shown the next free times. Rescheduling or cancelling moves or cancels it for every host.
Round robin
Each booking goes to one free host, chosen in this order:
- A link pinned to a host (a routing form rule can pin one) books that host.
- Same host (optional): someone who booked before goes back to the host they met last.
- Deal owner (optional): someone with an open deal in Funnel goes to the deal's owner.
- The host with the highest priority (Lowest to Highest).
- The host with the fewest bookings of this event type in the last 30 days, for their weight. A host with weight 200 gets about twice the bookings of a host with 100.
- The host who has waited longest since their last booking.
If the chosen host was booked a moment ago, the next one in that order gets it. The booking records who was picked and
why (assignment.reason: link_host, same_host, deal_owner, priority, fewest_bookings, longest_since_last,
order, only_host or next_free). A host's Max a day caps their bookings of this event type per day.
Routing forms
A Venom Forms form can route people to the right meeting and let them book it straight away. In the form's Connect tab, add Book a meeting:
- Rules: when an answer matches (the same conditions as form logic), book this event type, optionally with one round-robin host, or send them to a URL. The first rule that matches wins.
- Fallback: where everyone else goes. Without one, they see the form's normal thank-you.
- Name and email: the questions that hold them. The booking form is filled in with their answers.
When someone submits, the form shows the booking calendar for the meeting their answers picked, right on the form's page. The link behind it books once and expires after 14 days.
Polls
A poll finds a time with a group. In Calendar → Polls (/calendar/polls), pick a solo event type and propose 2 to 20 times, then send
the link. Each proposed time must be free when you create the poll, and it stays held for the poll (nobody else can
book it) until the poll closes. A poll stays open for 7 days unless you set closes_at (at most 60 days).
Invitees open the link, see the times in their own time zone, and answer Yes, If needed or No for each, with their name and email. They need no account. Everyone sees the names and answers, never the emails. The same browser can change its answers later.
When you pick a time, Venom books it for everyone who said yes or if needed: the first of them is the invitee, the rest are guests on the invite. The other times are released. Close a poll without a time to release them all.
Agents
| Route | Tool |
|---|---|
GET /api/workspace/calendar/event-types/{id}/hosts |
calendar_event_type_hosts_get |
PUT /api/workspace/calendar/event-types/{id}/hosts |
calendar_event_type_hosts_set |
GET /api/workspace/calendar/polls |
calendar_poll_list |
POST /api/workspace/calendar/polls |
calendar_poll_create |
GET /api/workspace/calendar/polls/{id} |
calendar_poll_get |
POST /api/workspace/calendar/polls/{id}/close |
calendar_poll_close |
The public poll page is /meet/poll/<token>; its API is GET /meet/api/poll/<token> and
POST /meet/api/poll/<token>/vote ({name, email, time_zone?, answers: {<option id>: "yes" | "maybe" | "no"}, edit_token?}).
Setting hosts replaces the whole list:
{
"kind": "round_robin",
"team": { "same_host": true, "deal_owner": true },
"hosts": [
{ "email": "ana@example.com", "weight": 200, "priority": 3 },
{ "uid": "user_2abc", "max_per_day": 4 }
]
}To take the hosts from a team, send host_team_id (an org team's id from org_team_list). hosts then only sets
people's weight, priority, daily cap and calendar; leave it out to keep what is saved. "host_team_id": null goes back
to the host list. The answer's host_team names the team, and its hosts are the team's people now:
{ "kind": "round_robin", "host_team_id": "<team id>", "hosts": [{ "uid": "user_2abc", "priority": 4 }] }Creating a poll:
{ "event_type_id": "<id>", "title": "Q1 planning", "times": ["2026-11-16T15:00:00Z", "2026-11-17T09:00:00Z"] }The answer includes the invitees' url. Close it with { "option_id": "<id>" } to book, or {} to just close.
Not yet: seats (several invitees in one slot).