Customer feedback; The biggest issue I've had with GHL since I first started with GHL 3 years ago is, more than any other factor, GHL's design is not a good fit for multi-location businesses. For example... a call recipient must be logged in to a specific subaccount to receive webapp calls for that subaccount. That is impractical for a business with 10 locations. Managing GBPs and the associated review requests separately by subaccount is an example of another centralized job task that is made impractical. Managing contacts separately, managing communication separately by subaccount, managing social media accounts separately by location, reporting, and everything else all seems to end with the location. LocationId being the central piece is an underlying design flaw, if you believe that businesses centralize tasks across locations to improve quality and drive efficiencies. GHL REALLY needs to create an alternate user experience associated with a CompanyID. Where a login to one account will house the collective of all subaccount contacts, interactions, Google Ad and facebook accounts (likely only one per company... not one per location), phone system, GBP review requests, etc. At a minimum, tie calls back to the user... not the subaccount. A phone system where calls can be forwarded across subaccounts to multiple locations is the norm for phone systems, for a reason. The locationID is still important, but it can operate in the background like a "tag." Otherwise GHL is forcing businesses to be more inefficient by not centralizing. Or worse, GHL simply is not a good option for multi-location businesses, because it is confusing and impractical for a centralized resource to remember to have 5 tabs open at all times for 5 businesses, and then go back and forth between these tabs, and feel like she or he is keeping things straight. Missing just a few customer calls (for example) because one tab was closed, is a non-starter for businesses. What I'm saying becomes even more confusing and more compounding for the mobile app. Which is why I ask that logins change from being location-based to company-based (encompassing all locations set in user permissions). Locations need to be a filter for a company, rather than something that divides a company's CRM, and operation into location-based, and inefficient, silos. There are of course lots of people who will manage multiple companies... and may even want account level interface. It would be a dream to have a login that centralizes permissions across companies as well! Answering phone calls is an easy use case... just like answering services answer calls for dozens of companies. Centralized logins could, and should eventually, happen at three different levels. AccountId --> CompanyId 1 --> LocationId 1 --> CompanyId 2 --> LocationId 1 --> LocationId 2 --> LocationId 3 I know there is an ideas board, and you probably tempted to redirect me there... but this is not an idea... this is fundamental restructuring so that mult-location businesses find GHL more useable. I believe this will drive adoption through the roof.
