Long-winded lead-in:I am an admin user and my company primarily uses Chilipiper for Concierge purposes. As a best practice, we want to use the credentials of a system/not-actual-people users as the primary means of integrating SaaS services together (e.g. Salesforce <> ChilIPiper). This future-proofs our tools for when people leave the company or go on vacation etc.We have done that for Salesforce, but I also wanted to specify that the Default Booker in our meeting queue as that same system user. However, the email address associated with the system user is a Google Group alias (we generally do not create actual GSuite accounts for System Users as sharing credentials can be a security hazard). After I made this change, meetings were no longer able to be booked – I suppose because the Google Group alias is not able to actually create events.# Ideally1). The Default Booker is not the one that needs to be creating the meeting of other users' calendars are connected2). The default booker is not included on all meetings (related to the last point)33). An error is shown if you try to use a Google Group alias as the Default Booker4). A better (error) message is shown in the scheduling interface itself (currently what happens is that it looks like the reps have no availability, when in actuality the Google Group alias just can't detect it or can't create meetings, etc)