[ use case · help center ]

A help center that explains your product the way you'd explain it.

Most help centers are written from imagination. Someone remembers roughly how the feature works, writes it down, ships it. Six months later, no one knows it's lying. Quill records the actual UI doing the actual thing — then watches for drift.

[ what a quill article looks like ]

Real screenshots. Real recordings. Tied to real code.

help.your-product.com/getting-started
Getting Started · 4 min read

Create your first workspace and invite your team

1

Click "New workspace" in the sidebar.

The button lives at the bottom-left of the navigation. If you've never created a workspace before, you'll see a highlighted hint pointing at it.

2

Name your workspace and pick a region.

Region is set once and can't be changed — pick the one closest to where your team actually works. The name shows up in your team's URL so keep it short.

3

Invite teammates by email.

Up to 12 free seats per workspace. Invites expire after 14 days but you can reissue them with one click from the Team Settings page.

[ how it's different ]

Four things only a code-aware help center can do.

Screenshots that match production

Quill drives your real app in a real browser. Captures the UI as it exists on main, today. When the UI changes, the screenshots refresh. No more "this used to be in the sidebar" tickets.

Narrated walkthroughs included

Every article ships with a short narrated video — the same flow the screenshots show, played back at human pace with a clear voice over. Customers who skim get the GIF; customers who watch get the explainer.

Drift alerts before customers find out

Every article tracks which routes, components, and feature flags it cites. When you change one of those, the article shows up in your review queue with a diff. Re-record or rewrite before the support ticket arrives.

Search that understands the product

Indexed by feature, not just by word. Search for "billing" and get the article that covers the billing surface — even if it's titled "Set up your subscription." Quill knows what the page is actually about.

[ the support team's view ]

Our deflection rate jumped 31% the month after we switched. The articles were saying what customers actually saw on screen — for the first time in three years.

— head of CX, B2B SaaS
[ for the support team ]

Less writing. Less updating. More resolving.

Hours back per week

Most support leads spend a quarter of their week chasing engineering to update one help article. Quill makes the article update itself — your support team can focus on the tickets that need a human.

Inline feedback loop

Customers can flag an article as "this didn't help" with one click. Comments come straight to the support team's inbox — with a link back to the exact section they were stuck on.

Ticket-driven backfill

Hook Quill to your support tool. When five tickets in a week ask about the same feature with no article, Quill suggests writing one. The pipeline drafts it; you publish it.

Ship a help center customers trust.

Connect a repo, watch Quill record the first walkthrough. If it's not the article you'd write yourself, don't publish it. Most of the time, you will.