The account executive and engineer. Booked together.

The first demo established a promising internal application use case. To move forward, the engineering manager needed to discuss how the application would connect to their systems and how a broader rollout would work.

That next conversation required two people from the sales team: the account executive who understood the evaluation and the solutions engineer who could address the technical questions. Sending either person’s individual calendar could produce a booking the other could not attend.

The account executive checked calendars, proposed times, and waited for the buyer to reply. When a slot disappeared, the coordination started again. The evaluation was ready to advance, but arranging the right meeting had become its own task.

The account executive created a Distro group link with the solutions engineer. The link showed times when both team members were available, so the buyer could choose a slot for a joint session.

The account executive shared that link in the follow-up to the first demo, alongside the proposed agenda. The engineering manager selected a time without comparing two calendars or asking the seller to confirm the engineer’s attendance separately.

For a later session requiring a third internal specialist, the team could create a three-person group link. Each link represented the specific people needed for that conversation; the buyer selected from their shared availability.

The technical evaluation moved into a meeting with both the account executive and solutions engineer present. Commercial priorities and implementation questions could be discussed together, reducing the need to relay answers through another call.

The buyer had one booking decision to make. The sales team spent less time coordinating calendars and more time preparing for the project. Group links made the next step easier precisely when the conversation required more people.