Our biggest update yet
We disappeared for a few weeks and returned with exactly eight too many features. Here's what's new in Ferndesk.
🌿 Fern V2 - she can now build and manage your entire help center, not just write articles
🔌 API docs + REST API - upload an OpenAPI spec, get a full API reference with interactive playground
🧱 New editor blocks - cards, accordions, steps, tabbed code, task lists, columns
🗂️ Sections - organize your help center into top-level tabs
🔍 Customer conversation browser - browse support conversations by coverage gaps and assign them to Fern
⚡ Content actions - readers can copy as markdown, open in ChatGPT/Claude, or ask your AI assistant
🌐 Chrome extension V2 - search past chats, see Fern's full working history, manage parallel conversations
💬 Plain + Pylon - connect your support tools so Fern learns from real conversations
Customer Spotlight: We Are Distributed
We Are Distributed is a career management and employment platform for remote workers. David Oragui shares how Ferndesk gave his team a fully automated help center that stays in sync with their codebase, saving 20+ hours every week.
"Ferndesk easily saves us 20+ hours per week & I can't wait to roll it out across all of our applications."
Fern V2
Fern used to write and edit articles. That was it.
Now she can build out collections, create sections, set up API references, rebuild your help center's structure, and propose every change as a staged update you review before publishing. You see exactly what she wants to add, change, or move. Keep what looks right, discard what doesn't.
API docs + REST API
Upload an OpenAPI spec (or point to a URL) and Ferndesk generates your full API reference: endpoint pages with parameter types, request/response schemas, authentication details, and an interactive playground for live testing.
URL-based specs refresh automatically, so your API docs stay current. They also get the same search, translations, and OG images as the rest of your help center.
We also launched the Ferndesk REST API, so you can manage your help center programmatically.
New editor blocks
Six new content blocks to make your docs richer:
Cards - icon, title, body, and optional CTA button. Vertical or horizontal layout.
Accordions - collapsible sections. Set expanded by default if you want.
Steps - auto-numbered step flows with custom icons. Great for onboarding and setup guides.
Tabbed code blocks - group multiple code files under one block with named, switchable tabs.
Task lists - interactive checklists that persist per reader. Readers check off steps as they go.
Columns - 2, 3, or 4-column grid layouts for side-by-side content.
If your docs have ever felt like walls of text, these help. Especially for developer guides, API tutorials, and anything with sequential steps.
Sections
Your help center now has a top layer above collections: sections.
Each section is a tab (think "Getting Started", "Guides", "API Reference") with its own set of collections, articles, and API references underneath.
If you've been cramming everything into one flat structure, sections let you break it apart properly. Fern can create and manage them too.
Article content actions
Every article and API page now has quick actions for readers:
Ask AI - query your assistant about the page
Copy as Markdown - for pasting into LLMs or internal tools
Open in ChatGPT / Claude - pre-loaded with the article URL
View as Markdown - raw content in a new tab
Toggle each one on or off from your help center settings.
Improved customer conversation browser
Ever wonder what your customers are actually asking about, and whether your docs cover it?
Now you can see every conversation your support team has handled, grouped by whether the answer is already in your help center, partially covered, or completely missing. Filter by theme, escalation, or resolution time to find the biggest gaps. Then select the conversations and ask Fern to write the missing docs.
Chrome extension V2
The Ferndesk Chrome extension got a major upgrade. You can now search through past conversations with Fern, see her full working history inline (every article, collection, and section she's proposing), and manage multiple parallel draft updates from the sidebar.
It's the same Fern workspace experience, but accessible from any tab in your browser.
Plain + Pylon
Ferndesk now integrates with Plain and Pylon.
Plain: widget contact forms route into Plain as threaded conversations with full customer context. We also built customer cards for Plain's dashboard, so your support team sees the full picture without switching tabs.
Pylon: resolved conversations from Slack communities and Discord servers feed into Ferndesk. Fern reads them and spots documentation gaps, the same way she does with your other support tools.
