Workflows support sub-folders. Forms support folders. But Email Templates — the area with arguably the most clutter in any active GHL account — only supports a single level of folders with no nesting.

As soon as you start building out real email systems (newsletters, onboarding sequences, rebooking campaigns, review requests, seasonal promos), that flat folder list becomes unmanageable fast. You end up with dozens of templates dumped into a single folder, and finding the right one means scrolling and scanning names instead of navigating a clean folder tree.

Here's a real example. Say you run a monthly newsletter with 3 segments and 4 emails per month. That's 144 templates per year. Right now you'd have to put all of January's templates, February's templates, March's templates, etc. into one "Newsletter" folder with no way to organize inside it. With sub-folders you could do:

Newsletter

└── Maintenance

└── January (4 templates)

└── February (4 templates)

└── ...

└── VIP

└── January (4 templates)

└── ...

└── Welcome Sequence (4 templates)

That's just one use case. Agencies managing multiple campaign types, seasonal content, A/B test variants, client-specific templates — all of these need more than a flat folder list.

The sub-folder pattern already exists in GHL (workflows use it). Bringing it to Email Templates would be a consistency improvement that makes the platform significantly easier to navigate, especially for users who are building at scale.

This is one of those small organizational features that has a big impact on daily usability.