How does TextExpander Requests fit into a KCS workflow?
TextExpander Requests fits into a KCS workflow by mapping directly to the “Flag It or Fix It” technique in the KCS v6 framework. Agents submit Snippet proposals through a centralized queue, and curators review and approve them, mirroring the KCS capture-and-validate cycle.
What is Knowledge Centered Service (KCS)?
Knowledge Centered Service (KCS), developed by the Consortium for Service Innovation, treats knowledge as a byproduct of solving problems. Agents create and improve knowledge content as part of their daily support work, not as a separate project.
Why does the “Flag It or Fix It” technique matter in Knowledge Centered Service (KCS)?
The “Flag It or Fix It” technique matters because it’s the handoff point where most KCS programs either gain traction or break down. Agents flag problems they find in the knowledge base; curators review and resolve them. When that handoff is frictionless, the knowledge base improves continuously. When it isn’t, feedback piles up and gets lost.
KCS operates in two loops. The Solve Loop is what agents do on every interaction: capture context, reuse existing knowledge, and improve what they touch. The Evolve Loop is what knowledge managers and curators do: monitor content health, track adoption, and keep the knowledge base current. “Flag It or Fix It” (Practice 4, Technique 4.2) is where those two loops connect.
TextExpander Requests in a KCS workflow
TextExpander Requests maps directly to Technique 4.2 (Flag It or Fix It) in KCS Practice 4 (Improve).
Agent encounters a problem → Flag It
An agent is working a ticket and expands a Snippet. The response contains an outdated return policy, a broken link, or missing steps for a new product feature. Instead of switching to Slack or opening a spreadsheet, the agent opens TextExpander and submits a Request. They can propose new Snippet content, suggest edits to existing Snippets, or flag that something needs review. Requests are available in the TextExpander web app, the Mac or Windows desktop app (v8.4+), and the TextExpander Chrome Extension.
Curator reviews and acts → Fix It
The curator receives an in-app notification and an email alert. They open the Request, see the proposed changes alongside the current Snippet in a side-by-side comparison, and approve, refine, or reject it. No context switching. No hunting through Slack threads. This feeds the Evolve Loop: curators spot patterns across Requests and improve Content Health.
Updated content reaches all agents → Reuse
Once approved, the updated Snippet is live for every agent on the team. The next person who encounters the same ticket type gets accurate, current content.
This cycle runs continuously. Every interaction becomes a chance to improve the Snippet library.
What does a KCS workflow with Requests look like?
Consider a 100-person support team using Zendesk and TextExpander. Their knowledge management specialist is the sole curator responsible for maintaining hundreds of shared Snippets.
Before: Agents flag outdated Snippets by posting in a dedicated Slack channel. Messages pile up. The curator checks the channel when she can, but high-traffic days mean requests sit for days. Some get buried entirely. She spends her mornings scrolling through Slack instead of improving content.
After: The team enables TextExpander Requests. When an agent spots a problem mid-ticket, they switch to the TextExpander app and submit a Request with the specific Snippet, the proposed change, and context about what’s wrong. The curator’s review queue replaces the Slack channel. She processes requests in order, with full context, in minutes instead of hours.
The Slack channel goes quiet. Not because agents stopped caring about content quality, but because they have a faster path.
Benefits for knowledge managers
Centralized feedback loop. Every Snippet suggestion and edit request lives in one place. No more cross-referencing Slack, email, and spreadsheets.
Audit trail. You can see who requested what, when it was approved, and what changed. This matters for compliance-heavy teams and for tracking which areas of your knowledge base need the most attention.
Faster content freshness. The time between “agent spots a problem” and “all agents get the fix” shrinks from days to minutes. In KCS terms, your Evolve Loop accelerates.
Reduced noise. Slack channels dedicated to Snippet requests generate interruptions for the whole team. Requests routes feedback only to people with the right permissions to act on it.
Agent engagement. KCS succeeds when agents feel ownership over the knowledge base. Giving them a structured, low-friction way to contribute keeps them invested.
How does AI fit into a KCS workflow?
AI fits into a KCS workflow by accelerating content creation and discovery — but it doesn’t replace the human validation that makes knowledge trustworthy.
AI tools can draft knowledge articles from ticket data, surface relevant content for agents, and flag gaps in a knowledge base automatically. The Consortium for Service Innovation notes that without human validation, agentic AI risks producing speculative or unverified content rather than solutions your team has actually confirmed.
That’s where Requests fits in as the validation layer. Agents flag what’s wrong. Curators confirm what’s right. AI can accelerate the work between those two steps, but the governance loop stays human.
How do you get started with Requests and KCS?
If your team already practices KCS (or wants to), here’s how to bring Requests into the workflow:
- Enable Requests for your organization. Available on Business, Growth, and Enterprise plans. Enterprise admins can control access at the organization or Snippet group level.
- Assign curators. Give “Can Edit” or “Can Manage” permissions to the people who should review incoming Requests. This maps to the KCS “coach” or “knowledge domain expert” role.
- Brief your agents. Agents can submit Requests from the web app or the Mac and Windows desktop app (v8.4+). Show them how during your next team huddle. Frame it as: “When you find something wrong with a Snippet, submit a Request instead of posting in Slack.”
- Retire the Slack channel. Once adoption picks up, archive the old Snippet-request channel. Keeping both paths open creates confusion about where feedback should go.
- Track and report. Use Request volume and approval rates as KCS health metrics. High volume means agents are engaged. Fast approval times mean your Evolve Loop is working.
Frequently asked questions
Do you need to be practicing KCS to use Requests?
No. Requests works for any team that wants a structured way to manage Snippet feedback. KCS teams will recognize the “Flag It or Fix It” pattern immediately, but any organization benefits from centralizing Snippet suggestions.
What permissions do curators need?
Curators need “Can Edit” or “Can Manage” permissions on the relevant Snippet groups. This controls who receives and can act on incoming Requests.
What plans include Requests?
Requests is available on Business, Growth, and Enterprise plans.