--- title: "Build a territory hierarchy with the Fullcast MCP" slug: "build-a-territory-hierarchy-with-the-fullcast-mcp" description: "How do I use Claude and the Fullcast MCP to build territories, segments, and balanced Smart Plan territories for reps?" tags: ["MCP", "skills", "Territory Planning", "Smart Plan", "Geography", "revops admin"] status: "new" updated: 2026-11-19T14:50:30Z published: 2026-11-19T14:50:30Z canonical: "support.fullcast.com/build-a-territory-hierarchy-with-the-fullcast-mcp" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.fullcast.com/llms.txt > Use this file to discover all available pages before exploring further. # Build a territory hierarchy with the Fullcast MCP > [!NOTE] > Early access feature > > This feature is currently available for early access. Contact your CSM for more information. Build a full territory hierarchy by answering design questions in Claude, from super regions down to balanced rep territories. Use it to stand up a new plan fast, with every change left proposed until you commit. ## Before you begin - The Fullcast MCP must be connected to Claude. For steps, refer to [Set up the model context protocol (MCP)](/plan-and-pay/docs/set-up-the-model-context-protocol-mcp). - You need permission to edit territories in the plan you're building. - You must have a plan created. It can be a blank plan. The MCP cannot create a new plan. ## Add the territory planning skill to Claude The skill is a zip file you can request from your Fullcast CSM. You add it to Claude once, and Claude loads it whenever you ask to build territories. 1. Obtain **fullcast-territory-planning.zip**. 2. In Claude, go to **Customize.** 3. In the **Skills** section, click **Add**, then **Upload a skill**. 4. Select the .zip file. Do not unzip it first. 5. Confirm the skill shows in your list and is turned on. ## How the skill builds your hierarchy The skill builds top-down, one level at a time: | Level | What it builds | Rule type | | --- | --- | --- | | Super regions | AMER, EMEA, and APAC, or NAMER, LATAM, EMEA, and APAC | Map | | Countries or segments | Country groups in EMEA and APAC, and segments such as Enterprise, Mid-Market, and SMB in the Americas | Map for countries, Bucket for segments | | Sub-regions | Optional groups of states, such as East, Central, and West, inside a segment | Map | | Rep territories | One balanced territory per rep | Smart Plan | At each level, the skill asks the design questions for that level one at a time, with its recommended option first. It shows you a preview of what it will build, builds it once you confirm, reruns rules so accounts move into the new territories, and reports the proposed account count for each territory and for Unassigned. Then it asks which territory to build next. The skill follows the same guardrails at every level: - It leaves every change proposed. It never commits, and it never asks you to. - It previews every change before it makes it. - It builds anything geographic (countries, states, provinces, postal codes) with the map rule, so you can see it on the **Map** tab. - It uses your territory names exactly. "Enterprise" under NAMER stays "Enterprise," not "NAMER Enterprise." - It reruns rules on its own only for territories it just created. For territories you already had, it asks first. ## Start a territory planning session 1. **Recommended:** Try the skill first on a copy of your plan or in a sandbox. 2. In Claude, start a new chat. 3. Ask for the outcome in your own words, for example: `Build out territories for my FY27 plan.` 4. Confirm the tenant and plan the skill names. To work in a different plan, name it. 5. Answer where to build. If the top of your hierarchy is empty, the skill builds there without asking. If it already has territories, the skill asks whether to build under it, clear it, or pick another territory. > [!CAUTION] > Warning > > - A territory the skill builds a map hierarchy on becomes a map container, and you cannot change it back. > - A map container cannot hold Bucket territories, so each level is either geographic or field-based. The skill reads your account fields and metrics once at the start, so later questions offer your real field names. ## Build super regions Super regions are the top level of a global hierarchy: AMER (the Americas), EMEA (Europe, the Middle East, and Africa), and APAC (Asia-Pacific). Some teams split AMER into NAMER (North America) and LATAM (Latin America). 1. Choose a region model: three regions, or four with NAMER and LATAM. 2. Give each region the name your team uses. The skill renames regions to match. 3. Choose how to place countries: - **Use the template as is** (recommended for a first pass) - **Review the edge countries together**: Mexico, the Middle East and Africa, Israel, Turkey, India, and Russia - **Upload a CSV** (comma-separated values) file that maps each country to a region The skill starts from a saved map template, such as **3 Super Regions** or **4 Super Regions**. In **4 Super Regions**, NAMER is the United States and Canada. If you review countries or upload a file, the skill shows only the countries that differ from the template and moves each one. Countries your file leaves out keep the template placement, and the skill flags any country name it can't match. At this level, child accounts land by their own address, even when their parent company sits in another region. This is the **Don't reassign children to the same segment** account family option. For how each option works, refer to [Treatment of Account Families - Fullcast 102 - Part 5](/plan-and-pay/docs/treatment-of-account-families). A large Unassigned count after this step almost always means missing or incorrect country data, not a rule problem. The skill tells you how many accounts are affected. ## Build segments in the Americas Segments split a region by company size or another field, usually Enterprise, Mid-Market, and SMB (small and midsize business). 1. Choose whether to split anything out first. Canada stays with the United States through segmentation by default. You can also give Canada its own territory, or split out LATAM if your AMER includes it. 2. Choose what to segment on. Employee count is most common. You can also carve out industries first and then band by employee count, or use another field such as annual revenue, tier, or ideal customer profile (ICP) score. > [!NOTE] > Note > > - An industry carve-out ahead of size bands makes a Bucket rule with two fields, which works correctly but may show the wrong label in the Fullcast app. > - Saving that rule from the Fullcast app may overwrite it, so ask Claude to make any later edits. 3. Choose your band thresholds, or enter your own: - Enterprise 5,000+, Mid-Market 500 to 4,999, SMB under 500 - Enterprise 2,000+, Mid-Market 200 to 1,999, SMB under 200 4. Name your segments. The default is Enterprise, Mid-Market, and SMB. 5. Decide where accounts with no employee count go. The skill tells you how many there are, then asks whether SMB should catch them. Otherwise they land in Unassigned. The skill builds segments with a Bucket rule. Order sets precedence, so industry carve-outs come first, then size bands. From the segment level down, the skill recommends the **Assign all children to the same segment** account family option, so child accounts follow their parent. It asks you to confirm, because this choice matters most for companies with large account families. ### Add sub-regions inside a segment For each segment, the skill asks whether to add a geographic layer before building rep territories: - **None, go straight to rep territories** (recommended for smaller segments) - **East, Central, West** - **Split out Canada here**, if you didn't earlier - **Custom state groups** Sub-regions use the map rule. The skill starts from a saved template such as **US 3 Sub-Regions** when one fits, or proposes a state list for each sub-region for you to confirm. The map rule groups the United States by state or postal code, not by county. ## Split EMEA into country groups EMEA is usually split by country first. The skill offers these groups for you to edit: | Group | Countries | | --- | --- | | UKI | United Kingdom and Ireland | | France | France | | DACH | Germany, Austria, Switzerland, and Liechtenstein | | Benelux | Belgium, the Netherlands, and Luxembourg | | Nordics | Sweden, Norway, Denmark, Finland, and Iceland | | Southern Europe | Spain, Portugal, and Italy | | Middle East and Africa | Countries in the Middle East and Africa | | Rest of EMEA | Every other EMEA country, so none fall to Unassigned | After it builds the groups, the skill reports accounts per group, suggests which groups are large enough to segment, and asks. Groups you choose get segmented the same way as the Americas. ## Break out countries in APAC and LATAM APAC is usually one region with a few countries broken out. The skill asks which to break out: - Japan - ANZ (Australia and New Zealand) - India - Greater China (China, Hong Kong, and Taiwan) - None, keep APAC whole The skill also builds a **Rest of APAC** territory that holds every remaining APAC country. LATAM works the same way, with Brazil and Mexico as common breakouts. Large breakouts can be segmented like the Americas. ## Build rep territories with Smart Plan Once you reach a segment or country that reps will own, the skill recommends a Smart Plan: a rule that builds one territory per rep and balances them by the criteria you choose. For how Smart Plan works on its own, refer to [Create a Smart Plan](/plan-and-pay/docs/create-a-smart-plan). 1. Tell the skill which team and role your reps hold. It pulls the reps from that team and builds one territory for each. 2. Choose which accounts stay with their current owner. 3. Choose what to balance. 4. Choose where leftover accounts go. The skill recommends spreading them across the territories so none sit in Unassigned. 5. Review the preview, then confirm. The skill reports each territory with its rep, account count, and balanced values, and calls out any territory more than about 15% off the average. If your reps own a whole country, state, or set of postal codes, tell the skill. It switches to the map rule and builds named areas for each rep, or balanced, connected areas automatically. ### Keep reps with their current accounts The first balancing layer is **Minimize Disruption**, which keeps accounts with the rep who owns them today. The skill always recommends limiting it, because keeping every owned account freezes stale books and throws off the balance. It offers: - **Activity in the last 90 days or an open opportunity** (recommended) - **Open opportunities only** - **Activity in the last 90 days only** - **Keep everything they own** (not recommended) If a field it needs is missing, the skill tells you and offers the options that still work. For more on this criterion, refer to [Smart Plan: minimize disruption](/plan-and-pay/docs/smart-plan-minimize-disruption). ### Choose what to balance The skill reviews your fields and metrics and recommends one or two balancing criteria, with a reason for each: | If your accounts have | The skill suggests balancing | | --- | --- | | A tier or priority field | Tier A accounts, or an even mix of tiers | | Mostly customers | Annual recurring revenue (ARR) | | Mostly prospects | Open pipeline, or a bookings potential, propensity, or total addressable market (TAM) field | | None of these | Number of accounts | When a book mixes customers and prospects, the skill applies each criterion to the right account type. ## Review and commit the proposed changes Everything the skill builds stays proposed. Proposed changes are saved in Fullcast but don't export to your CRM until you commit them. 1. Open the plan in Fullcast and go to **Territories** > **Manage Accounts**. 2. Switch to the **Difference** change state to see what moved. For how the change states work, refer to [Current, Proposed, and Difference views](/plan-and-pay/docs/current-proposed-and-difference-views). 3. To discard a change, undo it before you commit. 4. Commit when you're ready. For steps, refer to [Commit territory changes](/plan-and-pay/docs/commit-territory-changes). Right after a map build, account counts can lag. If a new territory shows zero accounts, ask Claude to refresh and recount. ## Share feedback on the skill The territory planning skill is in beta. If it recommended something you wouldn't build for your team, or built something you didn't expect, tell your Customer Success Manager (CSM) what you asked and what the skill did. ## Related - [Set up the model context protocol (MCP)](/set-up-the-model-context-protocol-mcp.md) - [Set up your AI client for Fullcast](/set-up-your-ai-client-for-fullcast.md) - [Check cutover readiness with the Fullcast MCP](/check-cutover-readiness-with-the-fullcast-mcp.md)