Glossary
Help center glossary
The terms support and documentation teams use for help centers, self-service and the screenshots in them, each explained in a sentence or two.
Help centers
- Help center
- A public site where a software company publishes how-to articles for its customers, grouped into collections or categories and searchable. Intercom, Zendesk Guide and HubSpot's Knowledge Base are common platforms for one.
- See alsoKnowledge baseHelp center platforms
- Knowledge base
- A collection of articles that answer questions about a product, written for customers, for the support team, or both. A help center is the public side of a knowledge base, and the two terms are often used interchangeably.
- See alsoHelp centerKnowledge-Centered Service
- Help article
- A single page in a help center that explains one task or answers one question, usually in numbered steps with screenshots of the product. It's the unit customers search for and land on.
- See alsoOutdated screenshotScreenshot annotation
- Collections and categories
- The way a help center groups its articles. Intercom calls the groups collections; Zendesk Guide uses categories that hold sections, which hold articles. The grouping drives the help center's navigation and often its addresses.
- See alsoSnapflow for IntercomSnapflow for Zendesk
- Product documentation
- Everything written to explain how a product works: help articles, developer docs, release notes and in-app guides. Help center articles are the part written for customers doing everyday tasks.
- See alsoDocs-as-codeRelease notes
- Release notes
- A short account of what changed in a product release, written for the people who use it. A release that changes the interface is also the moment help center screenshots start to fall behind.
- See alsoChangelogHow to automate help center screenshots
- Changelog
- A running, dated list of a product's changes, newest first. Where release notes explain a release, a changelog records every change, often in a line each.
- See alsoRelease notes
- Help center localization
- Translating a help center into other languages. Each translated article usually has its own screenshots, taken in that language's interface, so every change to the product multiplies the screenshots to retake.
- See alsoOutdated screenshot
- Docs-as-code
- Writing and maintaining documentation with the same tools as software: plain-text files in a code repository, reviewed in pull requests and published by a build. Common for developer documentation, less so for customer help centers.
- See alsoProduct documentation
- Content audit
- A review of every article in a help center to find what's out of date, duplicated, missing or unused. Checking how old the screenshots are is one part of it, and the part that can be done automatically.
- See alsoFree help center auditContent debt
- Content debt
- The build-up of documentation that no longer matches the product, the way technical debt builds up in code. It grows with every release the docs aren't updated for, and shows up as confused customers and extra tickets.
- See alsoContent auditSavings calculator
- Knowledge-Centered Service (KCS)
- A support method in which agents write and improve knowledge base articles as part of solving tickets, so the knowledge base grows from real questions. It's maintained by the Consortium for Service Innovation.
- See alsoKnowledge base
Support and self-service
- Self-service support
- Customers finding answers on their own, in a help center, an in-app guide or a chatbot, instead of contacting the support team.
- See alsoTicket deflectionSelf-service rate
- Ticket deflection
- A support question answered by self-service before it becomes a ticket. A help center only deflects tickets while its articles match the product: a screenshot that no longer matches sends the customer to support anyway.
- See alsoSavings calculatorOutdated screenshot
- Self-service rate
- The share of customers who solve a problem through self-service, usually worked out by comparing how many people use the help center with how many open a ticket. Tools measure it differently, so it's most useful compared with your own past numbers.
- See alsoSelf-service support
- In-app help
- Help shown inside the product where it's needed: tooltips, a help widget, or an article opened from the screen it describes. It often reuses help center articles, screenshots included.
- See alsoHelp article
Screenshots
- Outdated screenshot
- A screenshot in a help article that no longer matches the product: a renamed button, a moved menu, a new layout. Across 487 Intercom help centers Snapflow audited in October and November 2026, 57% of screenshots were more than a year old.
- See alsoThe Intercom numbersFind yours with the free audit
- Screenshot age
- How long ago a screenshot was taken or uploaded. Help centers don't show it, but most platforms record when each image was uploaded, which is how an audit can date every screenshot in one go.
- See alsoFree help center audit
- Screenshot annotation
- Arrows, boxes, numbers or labels added to a screenshot to show where to click or look. They have to be redone every time the screenshot is retaken, unless the tool that retakes it adds them again.
- See alsoScreenshot style guideFree screenshot frame generator
- Redaction
- Hiding sensitive details in a screenshot, such as names, email addresses or account numbers, by blurring or covering them. Taking screenshots in a demo account filled with sample data avoids most of it.
- See alsoDemo accountSample data
- Screenshot style guide
- The rules that keep a help center's screenshots consistent: size, crop, frame, annotation colour and what to hide. It's what makes screenshots taken months apart look like one set.
- See alsoScreenshot annotationBrowser and device framesFree screenshot frame generator
- Browser and device frames
- The outline of a browser window, laptop or phone drawn around a screenshot to show where it was taken. Help centers tend to use a light browser frame or none, to keep attention on the interface.
- See alsoScreenshot style guide
- High-resolution (2x) screenshot
- A screenshot taken at twice the screen's pixel density, so it stays sharp on high-resolution displays. Shown at half its pixel width, it looks crisp without looking bigger.
- Alt text
- A short written description of an image, read out by screen readers and shown if the image doesn't load. For a help center screenshot it says what the screen shows, such as "Notification settings with Slack alerts turned on".
- Permanent image address
- An image address that stays the same while the picture behind it changes. Embed it in an article once, and an updated screenshot appears without anyone editing the article. Snapflow serves every screenshot this way.
- See alsoHow embedding works
Automating screenshots
- Screenshot automation
- Taking or retaking product screenshots with software instead of by hand, either from a script that clicks through fixed steps or from an agent that works out the steps from the article.
- See alsoHow to automate help center screenshotsBrowser automation
- Browser automation
- Software controlling a web browser the way a person would: opening pages, clicking, typing. Playwright and Puppeteer are common libraries for it, used for testing and for screenshots.
- See alsoHeadless browserScripts vs an AI agent
- Headless browser
- A web browser that runs without a visible window, controlled by code. It renders pages the way a normal browser does, which is what lets a server take screenshots.
- See alsoBrowser automation
- AI browser agent
- An AI model that operates a browser to complete a task described in plain language, choosing each click from what's on screen instead of following a fixed script.
- See alsoHow Snapflow's agent worksWhat it will and won't click
- Demo account
- A login to your own product set up for screenshots and demos, with tidy sample data instead of real customers. Snapflow signs in as one to retake screenshots, and you can add one for each role your articles cover.
- See alsoSample dataHow Snapflow handles demo accounts
- Sample data
- Realistic but made-up records, such as customers, projects and invoices, that fill a demo account so screenshots look like real use without showing anyone's real data. Also called seed data.
- See alsoDemo accountRedaction
- Visual regression testing
- Comparing screenshots of an app before and after a code change to catch differences nobody intended. It uses the same tools as automated documentation screenshots, but checks the product rather than the help center.
- See alsoBrowser automation