Command for Teams Update : Contacts
Command is getting a big overhaul, which will fundamentally change how teams run their business in Command. Previously, personal leads/contacts and team owned leads/contacts were mixed together, and there was no way to standardize the tags, custom fields, SmartPlans, and other models/systems that a team would use, if they could. Every agent on a team has been working things in their own way, or if they were trying to standardize everything, it was very manual and tedious.
Now, we are separating an agent's personal and team Command accounts. This will be a work-in-progress, so we are starting with Contacts and SmartPlans, with other applets following shortly afterward. When using the team Command account, we will be able to create team Contact Tags, Lead Sources, Custom Fields, and SmartPlans. Using this team standardization, we can ensure that everyone on your team is following all of the standards and processes set by team Rainmakers.
Now, we are separating an agent's personal and team Command accounts. This will be a work-in-progress, so we are starting with Contacts and SmartPlans, with other applets following shortly afterward. When using the team Command account, we will be able to create team Contact Tags, Lead Sources, Custom Fields, and SmartPlans. Using this team standardization, we can ensure that everyone on your team is following all of the standards and processes set by team Rainmakers.
Prepare for Your Team Command Account
Prepare for your Team Command Account Guide
Learn More About Team Permission Levels
You will now be able to set different permission levels, for each team member, which will control what that team member can do in your team Command account. For instance, you can ensure that your team admin has access to help with any lead/contact in the team Command account, in conjunction with the primary agent assignee, or you can restrict an agent to only have access to work with leads/contacts that they own or are assigned to.
Because you have to make a decision about what permission levels you will set for each member of your team, individually, we created a guide to help you make this decision:
There are three permission levels built in to a team's Command account:
Standard - this will be the basic permission level for most agents on your team. This is also the default permission level for all associates on your team.
Because you have to make a decision about what permission levels you will set for each member of your team, individually, we created a guide to help you make this decision:
There are three permission levels built in to a team's Command account:
Standard - this will be the basic permission level for most agents on your team. This is also the default permission level for all associates on your team.
- Contacts Permissions
- Gives the associate access to manage leads/contacts that they own or are assigned to.
- Restricts the associate from being able to export or delete team-owned leads/contacts in the team Command account.
- SmartPlans Permissions
- For team SmartPlans, the associate will only be able to add leads/contacts that they own or are assigned to.
- Restricts the associate from being able to create, edit, or delete team SmartPlans.
- Contacts Permissions
- Gives the associate access to manage any lead/contact, in the team Command account, which allow you to delegate work to them.
- Restricts the associate from being able to export or delete team-owned leads/contacts in the team Command account.
- SmartPlans Permissions
- For team SmartPlans, the associate will be able to add any lead/contact, in the team Command account.
- The associate will be able to create, edit or delete team SmartPlans.
- Team Management
- Associates with this permission level have full access to the Team Management page, in Command settings, where they can change team member permission levels, turn on/off an associate's personal Command (see the section below), add guest user admin accounts, and request changes to the team roster.
- Contacts Permissions
- The associate will be able to access and manage any lead/contact, in the team Command account.
- An associate with this permission level can export team-owned leads/contacts, and can fully delete as well.
- SmartPlans Permissions
- For team SmartPlans, the associate will be able to add any lead/contact, in the team Command account.
- The associate will be able to create, edit or delete team SmartPlans.
Create and Manage Team Custom Lead Sources (Rainmakers)
In your team Command account, Rainmakers have the ability to create, edit, and delete custom team lead sources. These team lead sources allow you to standardize what your team is tracking, with everyone on the team working off of the same list of sources.
Create and Manage Team Custom Fields
(Rainmakers)
In the team Command account, Rainmakers have the ability to create Team Custom Fields that can be used by other members of the team. This allows Rainmakers to standardize the way leads and contacts are organized and labeled. Agents on the team will not be able to create Team Custom Fields, unless they have an Enhanced or Unlimited Team Permission Level.
Create and Manage Team Contact Tags
(Rainmakers)
In the team Command account, Rainmakers have the ability to create Team Contact Tags that can be used by other members of the team. This allows Rainmakers to standardize the way leads and contacts are organized. Agents on the team will not be able to create Team Tags and will have to use what is set up by the Rainmaker unless they have Unlimited or Enhanced permission levels assigned.
Create and Manage Team Opportunity Tags
(Rainmaker)
Everyone organizes their Opportunity pipelines in unique ways. Because of this, Command gives you the ability to create custom Opportunity tags. If there is a label or group that is standard to your business, add it as a custom tag and apply it to any number of Opportunities. This will allow you to organize your Opportunity Pipelines in any way you choose. As you start creating custom tags within Command, you might want to edit the name of the tag, delete a tag, or even color code.