The GHL needs teams now — or risks being replaced by platforms that offer them.
M
Mira leads
Objective: Improve metric tracking, lead distribution, and internal communication among user groups within the platform.
Current Problem:
Currently, GHL only allows the addition of individual users without the ability to organize them into teams. This limitation impacts:
Group Metrics: It’s impossible to analyze conversion rates, performance, or productivity by team (e.g., sales team vs. support team).
Uneven Lead Distribution: Leads are assigned to individuals, not teams, which can overload some users while leaving others underutilized.
Fragmented Communication: There’s no way to send targeted notifications to specific groups (e.g., alerts to the sales team about hot leads).
Proposed Solution:
Introduce a "Teams" feature within GHL, with the following functionalities:
- Team Creation
Hierarchical Organization: Allow admins to create teams (e.g., "Sales SP", "24/7 Support") and assign users to multiple teams if needed.
Customizable Permissions: Define access levels by team (e.g., sales team can edit pipelines, marketing team can only view reports).
- Team Metrics
Custom Dashboard:
View total conversion by team (e.g., how many leads from Team X became customers).
Compare performance between teams (close rates, response times, etc.).
Filter reports by team for strategic analysis.
Automatic KPIs: Generate metrics like "Team Conversion Rate" or "Leads Assigned per Team" in charts and tables.
- Lead Distribution to Teams
Automated Rules:
Distribute leads evenly among team members (e.g., round-robin).
Prioritize teams with lighter workloads or higher conversion rates.
Assign leads based on tags or specific criteria (e.g., SP leads → SP sales team).
Workload Balancing: Prevent overload by monitoring how many leads each team is handling.
- Internal Notifications by Team
Targeted Alerts:
Send real-time notifications to entire teams (e.g., "New urgent lead for the sales team").
Integrate with channels like Slack, email, or push notifications within GHL.
Automated Reminders: Notify teams about pending tasks (e.g., follow-ups for unattended leads).
Strategic Importance for GHL:
Scalability: Larger businesses need to manage multiple teams without losing the big-picture view.
Decision-Making: Team metrics help leaders identify gaps and reallocate resources effectively.
Customer Experience: Evenly distributed leads are attended to faster, boosting satisfaction.
Competitiveness: Platforms like HubSpot and Salesforce already offer this feature – GHL needs to keep up.
Example Use Case:
A marketing agency with 3 teams (Sales, Onboarding, Support) would use GHL to:
Measure which team converts the most leads into meetings.
Distribute 100 leads/day evenly among 10 sales reps.
Send an automatic alert to the support team when a client opens a critical ticket.
Technical Implementation Suggestion:
Simple UI: Add a "Teams" section in the settings menu, with drag-and-drop user assignment.
APIs for Automation: Allow teams to be used in workflows (e.g., "Send lead to Team X if tag is Y").
Integration with Existing Features: Link teams to pipelines, calendars, and campaigns.
Why This is Urgent:
Businesses are migrating to GHL for its flexibility, but the lack of team management limits its use for medium/large organizations. This feature would transform GHL into a truly competitive all-in-one platform.
Log In
D
Daniel Ndaya
I agree with you. But before we get teams we have to get "Roles".
Here's why:
Right now we are facing a major issue; when we have to let go of a team member, we need to find every workflow that that team member was put it when a contact was assigned and removed them. We have to do the same for every person we onboard; find the workflows and add them in. This is a job and a half...
What is needed is Roles:
Roles are a title that is given to a user, and that title has certain. Permissions. Instead of assigning a contact to a user. We assign it to a role. And anyone with that role gets assigned the contact. We can choose to distribute it evenly or unevenly
Example of roles:
"Sales Agent"
Permissions:
- Access to Opportunity Pipeline
- Access to assigned contacts
- Access to Calendars
In a workflow, we can assign a contact to anyone with Role: "SALES AGENT"....
And it will automatically assign it to the user that carries that role.
This is way-way more scalable than our current: "assign to user" workflow we have right now
A
Andrew Ferreria
this really is urgent. Here we're having to create workflows to be able to work, but clients aren't happy with the lack of that. It opens a lot of doors for us to lose to competitors
D
Daniel Ndaya
Andrew Ferreria I agree , I experience the same thing. But before we get teams don't you think we have to get "Roles".
S
Shane Veldhuizen
I can confirm that I have a potentially large client that is perfect for GHL but this issue has been one of the primary hangups. Makes organization, SOPs and ongoing management significantly more complex/unmanageable.
D
Daniel Ndaya
Shane Veldhuizen I agree with you I'm in the he exact same position. But before we get teams don't you think we have to get "Roles".
S
Shane Veldhuizen
Daniel Ndaya would be nice. But you can essentially create 'roles' based on specific users settings. While not a 'feature' per say, it gets the job done. And If I had to pick between the two I would opt for having teams as there no viable workaround
N
Nic Verdino
It also needs a hierarchy so the team manager can see everything from their team, but the individuals can only seat their own data.
For example, you have 3 sales managers, they should be able to see the activities of their individual team, not activity across the whole business.
In addition the individuals in the team can only see their own data, or what has been allowed for them to see.
D
Daniel Ndaya
Nic Verdino I see what you mean. Don't you think we have to get "Roles".
A
Admin Admin
It's a very necessary idea to be able to create teams.
In my case, I need people on the team to be able to access the contacts and data of certain workers, but not all of them.
Right now this option is very limited because either you can only see your own data or you can see the data of all the contacts...
Thus, in the “Data Visibility Scope” there would be 3 options:
- Only Assigned Data
- All Records
- Teams (and here choose the group)
In groups or teams, you could create Team A (with users a, b, c), Team B with users (c, d, and not assigned to anyone), for example.
D
Daniel Ndaya
Admin Admin I see what you mean, but don't you think we should first get "Roles".
C
Cwa HUB
Boaaaa!!
N
Nicholas Rustad
I think you can use the communities feature to have "teams" setup in the system.
M
Mira leads
Nicholas Rustad doesn't work like that, this is for online courses/ digital product sales.