Skip to main content Join us at TDX in San Francisco or on Salesforce+ on March 5-6 for the Developer Conference for the AI Agent Era. Register now.
If my requirement is to have an automated process for identifying what sales people are reps for what accounts and have that displayed on the account, is there any reason to use territory management or is this simply account teams with processs builder (and remembering to update everytime someone leaves)? I do not need to grant account access necessarily, as we have sharing rules and a private org. Is there any relationship between territory management and account teams? Or is it part of the functionality of TM to identify the users in a territory on the account itself? Thanks!
10 answers
  1. Feb 27, 2017, 9:51 PM
    Hey there Carri, 

     

    Both Territory Management and Account Teams offer the same functionality in different ways - granting access to records that users don't normally have based on Org Wide Defaults. Account Teams do it on a user basis (with the option to add a default Account Teams) and TM does it similarly to the Role Hierarchy. If you simply want to see which reps should be working on accounts without granting them any access, I don't know if either solution will give you what you want and you should look at using a custom Account Team object (though I would hesitate to do so - never a good idea to recreate standard functionality unless ABSOLUTELY necessary).

     

    If you want a visible list of Account Team members for a given account and are ok with granting access to said account, then I would go with teams. TM is more of a Ownership/Access/Forecasting tool than it is to see who is "on" an account. 

     

    One question for you: who owns the Accounts? The reps or someone else? 
  2. Feb 28, 2017, 2:02 PM
    Great, thanks to you both! Bottomline is we want to see who reps what accounts and in what capacity so sounds like AT is the way to go. We still give out access via sharing rules for plenty of other users that wouldnt be on an account team so those would remain in place. We would manage the ATs centrally on our Admin team based on geographical criteria in a process builder. Frequently when someone leaves if we arent notified (another issue) their name remains on the accounts and I think this is what is driving this request. They thought with TM it would be more automated and less to maintain, but so far I'm not finding that to be the case. True?

     

    Nate- currently it makes no sense but the Field VPs own the accounts, although have no accountability to them. The field (account managers basically) is divided up by regions so it's the VP of each region. Which brings up another factor, the Sales team is easily divided by state criteria, the Field team is mostly by state but there are a lot that fall outside of any logical criteria so those would have to be manually maintained anyway, another case for AT not TM right? Thanks!
  3. Feb 27, 2017, 9:47 PM
    For TM, you are basically building a Group based on criteria on the record (which state are they, which industry, which business size are they). The Account team has more to do with a User's role when working with the Account (Sales, BDR, Support, etc). So you could use both together. 
  4. Jan 15, 2021, 7:10 PM
    @Nate I have a silimar use case but I want the users to be a part of different teams. One Account can be in multiple teams and the users can be in more than one team. Will Account Team work for that? 
  5. Feb 28, 2017, 8:42 PM
    And, Account Teams are on the Lightning Roadmap, so there isn't an issue there. 
  6. Feb 28, 2017, 8:41 PM
    Hey there Carri! That doc is super confusing in that regards, its basically saying use Account/Selling Teams to do your territory management instead of Enterprise Territory Management (TM). Sorry for introducing that confusion to you! SO yeah, do the Account Teams and you are golden. 
  7. Feb 28, 2017, 8:31 PM
    I see they listTeam Based as an alternative but I can't find anything else about it. 
  8. Feb 28, 2017, 6:36 PM
    Hmm now I'm a little confused, youre saying this is a better use case for terrotory mgmt, not account teams? I'll add we do not use forecasting and we do plan onmoving to lightning in the next year most likely. 
0/9000