Navigation

Prerequisites

Shared Desks and SDR Rotations

Four arrangements that work, and what to set for each.

The settings on a group calendar are few, but they combine into arrangements that feel quite different to a team. A sales development rotation — a pool of people whose job is first conversations — wants even distribution. A managed desk wants an owner who never appears in it. A specialist arrangement wants a preferred person with cover behind them.

Each of the four below is a complete recipe. Pick the one closest to your situation.

Steps

A sales development rotation

The arrangement: several people whose job is to take first conversations, sharing the load evenly. Nobody is more entitled to a lead than anyone else.

What to set: every rep as a member; the owner deselected if they manage rather than sell; Round robin as the strategy.

Why round robin and not random: over a month random will drift, and a drift in first conversations is a drift in pipeline. Round robin corrects itself, because the member with fewest upcoming bookings is preferred.

The trade-off: no single booking is predictable. If someone asks who they will be speaking to, the answer is genuinely not known until they book.

Expect a rep returning from leave to take several in a row. That is the balancing working, not a fault.

A managed desk

The arrangement: a calendar that exists as a function rather than a person — Support, Onboarding, New Enquiries — administered by a manager who does not take the meetings.

What to set: the manager as the calendar's owner, deselected from the member list; the people who do the work as members; Round robin.

Why it works: ownership and availability are separate. The manager keeps configuration rights and full visibility of everything booked, and never appears in the rotation.

The trap: the owner is selected by default. If you create this calendar and do not deselect the owner, the manager starts receiving bookings immediately and it may be a week before anyone notices.

Deselecting the owner leaves them the owner. You are removing them from the rotation, not from the calendar.

Specialist first, team as cover

The arrangement: one person should take these meetings whenever they can, with colleagues covering the rest.

What to set: the specialist as the calendar's owner, in the rotation; the cover as additional members; Sequential as the strategy.

Why sequential: it takes the first free member in list order, and the list starts with the owner. So the specialist gets everything they are free for, and overflow falls to the others in order.

The trade-off: this concentrates work deliberately. It is the right shape for genuine expertise and the wrong shape for fairness — the specialist will be busier than anyone else, which is the point.

Order matters here in a way it does not for the other patterns, because sequential walks the list from the top.

Split by meeting type instead of by person

The arrangement: the same team offering different kinds of meeting — a 15-minute triage and a 60-minute deep dive — without the two interfering.

What to set: one group calendar with the same members, and two booking schedules on it, each with its own length, availability and form.

Why one calendar: every schedule on a calendar reads the same calendar, so a triage booking removes that time from the deep-dive page automatically. Two separate calendars would double-book the team.

The trade-off: two links to share. That is usually an advantage — each can be sent in the context it suits.

This is the pattern to reach for before adding a second group calendar. Two calendars mean two independent availability pools and real double-booking risk.

Result

Your group calendar now matches an actual working arrangement rather than a default, and the behaviour your team experiences is the behaviour you chose.

All of it is reversible. Changing the strategy affects future bookings only; existing meetings stay with whoever has them.

The four patterns at a glance

Pattern Owner in rotation? Strategy What you get
Sales development rotation Usually no Round robin Even distribution across the pool
Managed desk No Round robin An administered function nobody owns personally
Specialist with cover Yes, first Sequential A preferred person with automatic fallback
Split by meeting type Either Round robin Two offerings, one shared availability pool

Tip: Whichever pattern you choose, availability quality decides whether it works. Allocation is only as good as what Zyntro can see of each member's week. A team where some members keep their real commitments elsewhere will produce bookings people cannot take, and no strategy fixes that — connecting those calendars does.

Continue Reading

Was this article helpful?

NotebookLM Overviews