It would also be useful if other auxiliary data could be added about staff members without having to create them also as a contact.

I recently was developing an extension to help determine and display the calendars of the staff within the closest physical proximity to a contact for booking an appointment (as we run in home solar sales as well as virtual but prefer in home and wanted to make the booking process a bit easier for agents and administrators).

Unfortunately, there is nowhere natively to store a field like "zip code" for a user. We use an external server to do a lat/lon lookup for both the staff and customer zip codes and perform haversine formula for rough calculations of distance and it works great, but we are also then having to store external references to users with associated zip codes, which isn't ideal if we wanted to expand upon the idea at all.

I thought about trying to stuff the value in the extension field or even the email signing field for users, but both of those solutions are obviously problematic.

I would like to create a more general tool for inside of GHL (through a browser extension) which can be quickly used to get satellite images, associated data about a property and recommend the closest staff calendars to a location. I have this currently for an internal company use, and one thing that is preventing me from making it more widely usable is this inability to attach auxiliary data to a staff member without the use of an external database (which still then relies on the staff member having the same phone number in both systems, for auto-detection or being mapped via the ID when they are created).

If I am able to skip that step and maybe even store lat/lon for the staff (ideally, which can be queried), or approximate with a Zip code that is internal to GHL staff contact, then I would be able to offer a more generalized plugin for various use without the overhead of some CRUD and db/table transactions on external servers, which is currently making the feature only work in a very specific use case and proprietary scope.

Thanks in advance for reading me ramble. :)