How do I set up and manage my Taxonomy?

Last updated: November 20, 2026

Taxonomy organizes your issues into a hierarchy of product areas and subareas (for example, Integrations → Slack and Integrations → Salesforce). Pylon builds the first version from your own issue history. You then refine it, and Pylon files every new issue into it automatically.

Once your taxonomy is set up, you can filter issues and analytics by product area, and you can start triggers when an issue's product area changes.

Taxonomy is in early access. If you don't see it under Settings → Taxonomy, contact your Pylon team to turn it on.

Set up your taxonomy

  1. Go to Settings → Taxonomy.

  2. Click Generate from issue history.

  3. Wait for the run to finish. It usually takes about 15 minutes, and you can leave the page and come back.

During generation, Pylon:

  • Reads the customer questions from your last 90 days of issues, up to the 1,000 most recent.

  • Groups similar issues together and names each group.

  • Organizes the groups into a hierarchy up to three levels deep.

  • Files every issue from that window into the new hierarchy. Issues that don't clearly fit any product area go to Uncategorized.

When the run finishes, the page shows your tree with the number of issues in each product area. Select any product area to see its description, its subareas, and the issues filed under it. Click an issue to preview it.

From then on, Pylon assigns each new issue to a product area automatically, usually shortly after the issue is created.

Things to know before you start

  • You can generate once every 24 hours. If a run finished recently, the page tells you when the next one can start.

  • Generating always starts from scratch. You can't regenerate on top of an existing tree. To start over, you have to delete the whole tree first (see Start over below).

  • You need a generated tree before you can add product areas by hand. After the first run, you can add, rename, move, and delete freely.

  • There's no field for generation instructions. Pylon builds the first tree only from your issues. You shape it afterward by editing names, descriptions, and sorting guidance.

Bringing a taxonomy from another system

You can't import a taxonomy from another tool (such as Zendesk or a spreadsheet) yet. To recreate an existing taxonomy in Pylon:

  1. Click Generate from issue history to create a starting tree.

  2. Click Edit and reshape it to match your existing taxonomy. Rename areas to your categories, add missing product areas and subareas, move areas into your hierarchy, and delete the ones you don't need.

  3. Paste each category's definition into Description. Add any rules about what doesn't belong into Sorting guidance.

  4. Click Save. Pylon re-sorts your issues into the new structure.

Your options after setup

Option

Where to find it

What it does

Edit

Edit button at the top right

Add, rename, describe, move, and delete product areas. Nothing changes until you click Save.

Find new product areas

⋯ menu → Find new product areas

Looks at your newest issues for themes your current tree doesn't cover, then suggests new product areas for you to review. Your existing areas are never changed.

Delete product area tree

⋯ menu → Delete product area tree

Removes every product area so you can generate a new tree.

Edit product areas

Click Edit to enter edit mode. All your changes stay in a draft until you click Save. Click Discard Changes to throw them away. If you try to leave the page with unsaved changes, Pylon asks you before dropping them.

Add a product area or subarea

  • New top-level product area: click + Product Area at the top of the table.

  • New subarea: hover over a product area and click + (Add subarea). You can also open the product area and click + Subarea in the side panel.

A side panel opens for the new product area. Fill in:

  • Name (required): every product area needs a name before you can save.

  • Description: what belongs in this product area, in the words your customers use. For example: Third-party syncs: CRM, Slack, and issue trackers.

  • Sorting guidance: what doesn't belong here and where it goes instead. For example: Questions about tickets a sync created belong in Issues, not here. Add as much detail as you need for borderline issues.

Click Save in the panel to add it to your draft, then Save at the top of the page to apply your changes.

Tip: When filing issues, Pylon treats sorting guidance as more important than the description. If an issue keeps landing in the wrong product area, add sorting guidance rather than rewriting the description.

Rename or update a product area

Click any product area in edit mode to open its side panel. There you can change its name, description, or sorting guidance. Product areas that Pylon generated are labeled Product area created by Pylon AI. You can edit them just like the ones you add yourself.

Move a product area

There are two ways to move product areas:

  • Drag and drop: grab the handle on the left of a row and drop it onto another product area to nest it there. To make it a top-level product area, drop it on Drop here to make a top-level product area at the bottom of the table.

  • Move to: select one or more product areas with their checkboxes, click Move to in the bar at the bottom, and pick a destination (or Top level).

Moving rules:

  • When you move a product area, its subareas move with it.

  • A product area that has subareas can only move to the top level. If you move a selection that includes some areas that can't go to the destination, those areas stay where they were and Pylon tells you how many.

  • The tree can be at most four levels deep, so you can't move a group somewhere it wouldn't fit.

  • Uncategorized can't be moved and can't have subareas.

Merge product areas

Taxonomy doesn't have a merge button. To merge Area A into Area B, you delete Area A and widen Area B so it covers both. Do it all in one editing session:

  1. Click Edit.

  2. Open Area B and update its Description and Sorting guidance to cover everything Area A used to hold. A simple way is to combine the two descriptions into one.

  3. Delete Area A.

  4. Click Save.

If Area A has its own subareas: deleting Area A also deletes everything under it. To keep any of those subareas, move them under Area B before you delete Area A. Select them and choose Move to → Area B, or drag them onto Area B. If Area A has no subareas, skip this.

When issues move: nothing is reclassified while you're editing. Deleting Area A and updating Area B only change your draft. When you click Save, Pylon re-files Area A's issues into your remaining product areas and re-sorts the rest of the tree against Area B's new description. This usually takes a few minutes. Most of Area A's issues should land in Area B, but each issue goes wherever it fits best, so some may end up in another area or in Uncategorized.

Delete a product area

  • One product area: hover over the row and click the trash icon.

  • Several at once: select them with their checkboxes and click Delete in the bottom bar.

Deleting a product area also deletes its subareas. Its issues are re-filed into the product areas that remain, and anything that no longer fits goes to Uncategorized. You can't delete Uncategorized, and you can't delete your last remaining product area.

What happens when you save

Nothing is reclassified while you're editing. After you click Save, Pylon re-sorts your issues against the updated tree. This usually takes a few minutes. Any edit changes the full set of options issues are sorted into, not just the area you edited. So a new or reworded product area can pick up issues from anywhere in the tree, and a narrowed one can send issues elsewhere.

The re-sort covers issues that already have a product area, starting with the 5,000 most recent. Older issues that were never labeled aren't added. See Which issues get a product area below.

Which issues get a product area

  • When you generate: every issue from the last 90 days. If you have very few recent issues, Pylon reaches a little further back so the tree has enough to work with.

  • New issues: labeled automatically as they come in.

  • After you edit: issues that already have a product area are re-sorted, up to the 5,000 most recent.

There's no way to backfill your taxonomy onto older issues. Issues from before the generation window stay unlabeled, and they won't show up when you filter by product area.

Find new product areas

As your product and customers change, new themes show up that your tree doesn't cover. To find them:

  1. Click ⋯ → Find new product areas. This usually takes a few minutes.

  2. When it finishes, the status line shows how many new product areas were found. Finding none is normal. It means your tree already covers your recent issues well.

  3. If Pylon found new product areas, the page switches to Review product areas. New areas are marked New in the tree. Click one to see the issues that would move into it.

  4. Choose what to do:

    • Approve New Product Areas adds them and moves their issues.

    • Edit lets you rename, adjust, move, or remove suggested areas, or reorganize the rest of the tree, before you approve.

    • Cancel dismisses the suggestions without changing anything.

How suggestions work:

  • Suggestions only add product areas. They never rename, move, or delete your existing ones.

  • Pylon only suggests a product area if at least five issues would move into it, and an issue only moves if it fits the new area better than its current one.

  • You can run Find new product areas at any time, even within 24 hours of generating your tree. Running it again replaces any earlier suggestions you haven't acted on.

  • Approving suggestions requires permission to edit issues.

Start over

To rebuild your taxonomy from scratch:

  1. Click ⋯ → Delete product area tree and confirm.

  2. Click Generate from issue history.

Warning: Deleting the tree removes every product area, including the ones you added, renamed, or moved. Issues filed under them become unlabeled. Generating again builds a fresh tree from your recent issues and doesn't restore your earlier edits. Deleting the tree also doesn't reset the 24-hour wait between generations.

Limits

  • Depth: up to four levels when editing by hand. Generated trees are up to three levels deep.

  • Size: up to 254 product areas that hold issues. This counts every subarea plus every top-level area without subareas, and doesn't count Uncategorized. Pylon won't save an edit that goes over this limit.

  • Generation: once every 24 hours. Pylon builds the tree from up to 1,000 of your most recent customer questions and labels every issue from the last 90 days.

  • Re-sorting after edits: up to the 5,000 most recent issues that already have a product area.

FAQ

Why are some issues in Uncategorized?

They didn't clearly match any product area. Common examples are scheduling threads, invoices, and very broad questions. New issues in Uncategorized are re-checked as they're updated, and they move to a real product area once one fits. If you see a pattern there, add a product area for it or run Find new product areas.

An issue is in the wrong product area. How do I fix it?

Add Sorting guidance to the product area it landed in, saying what doesn't belong there and where it should go instead. Then save. Pylon re-sorts issues against the updated guidance.

Will my edits survive if I regenerate?

No. Generating again replaces the whole tree, including your edits. To fill gaps without losing work, use Find new product areas instead.

Can I import my taxonomy from another tool?

Not yet. Generate a tree, then edit it to match your existing categories. See Bringing a taxonomy from another system above.

Can I tell Pylon how to build the taxonomy?

Not when you generate it. There's no instructions field. After it's generated, you guide how issues are sorted through each product area's Description and Sorting guidance.

Can I apply my taxonomy to older issues?

No. Generation labels issues from the last 90 days, and new issues are labeled as they come in. Older issues stay unlabeled.