G2

Iryna S.

Project Coordinator

Computer Software

Mid-Market (51-1000 emp.)

10/1/2026

"Less scheduling back-and-forth before every project meeting"

4.5/5

What do you like best about Calendly?

Event Types, custom availability, and multiple calendar connections let us share realistic time slots without exposing the rest of our schedules. On Standard, we can create unlimited event types, connect multiple calendars, and automate reminders and follow-ups, which has cut down a surprising amount of back-and-forth email for simple thirty-minute meetings. For team workflows, we rely on Round Robin, team scheduling, and Routing Forms to route people to the right owner without having to manually review every booking. On implementation projects, technical questions can go straight to the appropriate specialist, while scope reviews stay with me. Workflows have also been useful for more than just reminders: we include the document to review or the information the client should have ready, so the meeting starts with more context instead of spending the first ten minutes getting everyone aligned. Review collected by and hosted on G2.com.

What do you dislike about Calendly?

The biggest mess usually starts when the team creates too many event types without a shared structure. We ended up with similar names, different durations for essentially the same thing, and old booking links still circulating. That becomes confusing fast for both the team and the client. I’d like stronger admin tools to help spot duplicate event types, near-duplicates, or ones that are barely used. For now, we’ve mostly addressed it with naming rules, clear ownership, and regular cleanup of links that shouldn’t be active anymore. Review collected by and hosted on G2.com.

What problems is Calendly solving and how is that benefiting you?

Before Calendly, scheduling project follow-ups with the client, design, and development often turned into long email threads and internal messages because everyone’s availability was different. I also kept a separate list just to track which meetings still needed confirmation or had to be rescheduled. Once we switched, we created Event Types for our main session formats, connected the team calendars, and used Round Robin when either of two specialists could take a meeting. We also set up Workflows to send reminders and the relevant prep materials automatically. Our first setup wasn’t perfect. We initially left meetings too close together, so days started filling up with back-to-back calls and there was no time to reset between them. After that, we added buffers, tightened the booking windows, and later introduced Routing Forms so technical requests went straight to the right specialist, while coordination meetings still came to me. The practical change was straightforward: we stopped rebuilding availability every time a meeting came up. I spent far less time chasing confirmations and much more time focused on the actual agenda, dependencies, and next steps. Review collected by and hosted on G2.com.