https://bunnycal.io/blog/tags/product/Recent content in Product on BunnyCal BlogHugoen-usMon, 27 Jul 2026 16:03:00 +0530https://bunnycal.io/blog/changelog-july-2026/Sat, 25 Jul 2026 00:00:00 +0000https://bunnycal.io/blog/changelog-july-2026/<p>A month of work that mostly amounts to removing steps from things you already do more than once a day.</p> <h2 id="multi-account-calendars">Multi-account calendars</h2> <p>You can now connect more than one calendar account per provider — two Google accounts, or a Google and a Microsoft account side by side. Every connected calendar can be marked as a conflict source, while exactly one stays the write target for new bookings.</p> <p>This also fixes a long-standing sharp edge: connecting a second account used to overwrite the first. Each connection is now independent, with its own disconnect.</p>https://bunnycal.io/blog/round-robin-that-actually-balances/Wed, 22 Jul 2026 00:00:00 +0000https://bunnycal.io/blog/round-robin-that-actually-balances/<p>Every scheduling tool with a team plan claims to do round-robin. Most of them implement the same thing: keep a pointer, hand the next booking to whoever is next in the list, advance the pointer. It demos beautifully. It falls apart in the second week.</p> <h2 id="why-a-rotating-pointer-drifts">Why a rotating pointer drifts</h2> <p>A pointer only counts <em>offers</em>, not outcomes. Consider a three-person team where everyone is nominally equal:</p> <ul> <li>Priya works Tuesdays through Fridays.</li> <li>Marco is on Pacific time; the team&rsquo;s booking page is mostly booked by European prospects in the morning.</li> <li>Dana has back-to-back internal meetings every Monday.</li> </ul> <p>The pointer doesn&rsquo;t know any of that. It offers Marco the 9am CET slot, finds he has no availability, and skips to the next person. Skipping <em>doesn&rsquo;t cost Marco his turn</em> — so he stays at the head of the queue and gets skipped again. By Friday, Priya has taken sixteen calls and Marco has taken three, and nobody touched a setting.</p>https://bunnycal.io/blog/multiple-calendars-one-availability/Sat, 27 Jun 2026 00:00:00 +0000https://bunnycal.io/blog/multiple-calendars-one-availability/<p>Most people don&rsquo;t have <em>a</em> calendar. They have a work Google account, a personal one, maybe an Outlook calendar from a client engagement — and meetings booked against any of them are equally real when someone asks if you&rsquo;re free at two.</p> <h2 id="read-from-everything-write-to-one">Read from everything, write to one</h2> <p>BunnyCal separates the two operations, because they want opposite defaults.</p> <p><strong>Conflict checking should be greedy.</strong> Every connected calendar you mark as a conflict source is queried when computing availability. A dentist appointment on your personal calendar blocks a work booking, and nobody outside sees why — the slot is simply gone.</p>