The goal of this article is to explain the differences found in the Enterprise Edition when compared to the team products currently active in Chime. Be aware that most features are the same at the Enterprise Edition level as they are in the team products so it would be advisable to review the following articles to understand how the logic works for these features at the team level.
- Lead Organization with Pipeline Stages
- Lead Organization with Groups
- Lead Organization with Tags
- Lead Organization with Filters
- Lead Privacy: Team Leads vs. Private Leads
- Lead Privacy
- View by Group
- Pipeline Stages
- Saved Filters
- Lead Pond
- Lead Collaboration
- Duplicate Leads
The logic here is similar to the logic that is live on team editions of Chime (see HERE). The only difference is that instead of "Team Leads" and "Private Leads," the following two are the only options: (1) Company Leads and (2) Private Leads.
Based on our current permissions structure, the visibility of leads is controlled by the organizational hierarchy.
Here is the detailed logic:
- The Company Owner/Admins can see all Company Leads and their own Private Leads
- The Group Owner/Admins. . .
- can see all Company Leads belonging to their group and its subgroups. They can also see their own Private Leads.
- cannot see the leads belonging to parent groups or other groups at the same tier.
- Standard users can only see the Company Leads assigned to them and their own Private Leads.
- Under Permissions, the switch to enable/disable "Access All Company Lead" is used to give the users access to all Company Leads. This is intended to be a special permission and is not limited by the organizational hierarchy.
View by Group
Company Owners/Admins have access to view all Company Leads within the organization. Those with certain levels of admin access can see leads within their group and any subgroups.
The pipeline within the New Enterprise product is maintained at the account level. This means that each individual group (see New Enterprise (Beta) - New Enterprise (Beta) - Organization and Hierarchy Overview) cannot have their own pipeline stages at the present time. This logic was designed to allow for reporting to feed up to the top level and this is only possible if all the pipeline stages are the same at all levels.
Similar to pipelines, groups are maintained at the account level and cannot be different for each individual group.
There are now two types of tags: (1) Private Tags and (2) Company Tags. Private Tags are created and maintained by each individual user and cannot be shared. A Company Tag is created/managed only by those with admin access (see New Enterprise (Beta) - Permissions) but can by used by anyone within the entire organization.
When saving a filter, currently the only option is to either (a) keep it saved as a private filter only for your individual use or (b) share it with the company. At present, there is no option to share a filter at a group level.
When setting up lead ponds, you can now choose whether you would like the lead pond to be accessible by using two options: (1) by group or (2) by agent. If you choose either one of these options, you cannot mix it with the other. In other words, you cannot select an entire group to have access to a lead pond but then only a few agents from another group. If you would like to get specific on which agents have access you will need to do it agent by agent for all the groups.
Because the pipeline stages are shared throughout the entire account (within all groups), you can actually share a lead between groups. This means that in the Assigned To section of a lead profile you can choose any of the available drop-down options for the custom roles (see Creating Custom Roles) and perform a search, by name, for anyone else within the account regardless of whether they belong to a separate group or not.
If you have any questions regarding this topic or any others, please reach out to our Support Team via email at <firstname.lastname@example.org> or by phone at 1 (855) 981-7557.