How to use Named Accounts and Named Exceptions

When a certain account needs to be assigned to a territory in a way that does not conform to the territory/segmentation rules, the Named Account feature comes into play.

What does naming an account do, in terms of how the Fullcast system works?

Named Account and Named Exception operate the same in Fullcast. That is to say, they allow you to designate (or pin, or name, or mark, or flag) an account so that it is locked in that segment/node. It makes the account immovable to any other segment until the Named Account/Named Exception label is removed.

What is best practice for using Named Accounts and Named Exceptions?

We have found that different organizations use these in different ways. If there were a "textbook definition" of what these terms mean, it might look like this:

Text Book Definition

A Named Account signifies that an account is a strategic account. For example, let's say you have a model where reps are allocated to a geographic territory, but each rep also gets a handful of high-value accounts that aren't within their geo-based territory. You could mark those as Named Accounts in Fullcast.

A Named Exception signifies that an account is an exception to the regular set of rules that exist in a given segment. For example, let's say you have Rep A who has owned XYZ Company for many years. Rep A will keep that account this year, even though the new territory rules wouldn't assign that account to Rep A's territory. You could mark that account as a Named Exception in Fullcast.

However, again, we have found that different organizations use these in different ways.

*The👏 Most👏 Important Consideration*

Practically speaking, the most important thing is: Your whole team should agree on what each Named designation means and use the labels consistently.

Why is this? Because when you re-run rules you can choose to toggle on and off whether to include Named Accounts and Named Exceptions. So, everyone needs to be in agreement about what these designations mean.

One simple and easy-to-maintain approach we have seen is the following:

• Named Accounts: These accounts will be named for a longer period of time, such as for an entire fiscal year.
• Named Exceptions: These accounts will be named for a shorter period of time, such as until your quarterly re-plan.

In some rare situations, accounts having bad data quality can be named Named Accounts. This is not recommended but can be done as an exception until the data can be fixed.

Steps to create Named Accounts and Named Exceptions

1. Access your Fullcast instance and switch plans if applicable.
2. Click Manage Accounts on the Territories tile. 
3. Select the Segments tab to view the GTM hierarchy and corresponding accounts. 
4. In the Grid, select the account(s) that needs to be tagged using the checkbox.
5. Once selected, click the Actions button in the Grid Actions Bar. 
6. Pick Set Named Types from the drop-down menu.
7. In the pop-up window that follows, select the tag either Named Account or Named Exception that needs to be added to the selected account(s).
8. Select Confirm.  

Note that after you designate an account to be named, you will see a pushpin appear in the first column in the grid.

• Red🔴 Pushpin = Named Exception
• Green 🟢Pushpin = Named Account

If you want to clear the named types, you can do so using the same drop-down menu you used to create them.

Moving accounts using drag-and-drop

When you are manually moving accounts, by dragging them from the grid into a Node in your Segmentation Hierarchy, you will be prompted to specify if you want to name them.

Clearing Named Types When Rerunning Rules

When you manually rerun the rules on a node, you will be prompted to indicate whether you want to exclude either Named Accounts or Named Exceptions.

• If you want all your Named Accounts/Exceptions to stay as is, select Both
• If you want to clear one of the Named types, select the one that you want to stay as is.

Article refreshed by Ashley Kim. We're working hard to improve our resources. If you read this far, thank you! Please take one more millisecond to give feedback using the 🙂 or 🙁 below.