Knowledge Base

Customer Service KB & Best Practice SOP

A paired knowledge base and SOP for e-commerce frontline agents. The KB covers nine customer service scenarios across payments, orders, returns and account security; the SOP is the procedure layer built on top of it.

KB DesignSOPE-Commerce

View the KB ↗View the SOP ↗

Knowledge Base

The two documents

KB — K Store Customer Service Scenarios

Every entry resolves to a sendable script and a decision tree. Features a fixed five-part structure across all scenarios, a decision tree job aid per scenario, zip/unzip to collapse the page to an index, and category filtering with full-text search.

SOP — K Store Agent Best Practice

Covers the step-by-step chat and email workflow, the on-hold subprocess and callback rules, hard-complaint escalation tiers, and general conduct standards — each procedure with its own decision tree.

Creative process

A fixed structure for every entry

Each scenario is written against the same five-part template, so an agent meets information in the same order every time and never has to work out where to look.

KB scenarios	Overview → Description → Backend status → What to execute → Script example
SOP procedures	Overview → Description → Backend status → What to probe / action item → Script example

Consistency is the point. An agent under time pressure should not have to re-learn the shape of the document on every scenario, and the SOP mirrors the KB deliberately so agents carry one mental model across both.

A job aid attached to every entry

Each scenario and procedure closes with its own decision tree, rendering the same flow as a branching diagram rather than a paragraph.

Design rationale

Zip / Unzip — controlling what is on screen. A single control collapses every card down to its title, turning the full document into a short index. An agent scanning for one answer sees a list of headings instead of a wall of text, then expands only the entry they need. Mid-contact, that difference decides whether the documentation is helping or getting in the way.

Decision tree — seeing the whole path at once. Written procedure tells an agent what the next step is, but not where that step sits in the wider process. The decision tree shows every route through the case at a glance — including the escalation branches, where choosing the wrong path carries real consequences.

Built as a generic, self-created illustration — the “K Store” brand is fictional and the content is not affiliated with any employer or client.

← PreviousIntro to Best Practice, Backend and Knowledge Base Next →Customer Service in AI Era