Product Knowledge Card Template

Example — Fictional content for illustration purposes

XR-500 Mesh Router — v3.2 firmware


Product Category
Networking
Status
Active
Review Owner
SPSophie Petit
Support Tier
L1 — Self-service

📦 Product overview

Tri-band Wi-Fi 6E mesh router supporting up to 200 connected devices across 450m² coverage. Designed for mid-size households and small offices. Includes 4× Gigabit Ethernet ports, 1× 2.5G WAN, and USB-C for local storage sharing. Firmware v3.2 introduces WPA3 enterprise mode and improved band steering.

🔧 Common issues

SymptomCauseResolution
Blinking red LED after firmware updateIncomplete OTA write (power interruption)Hold reset 15s → USB recovery mode → reflash v3.2
6 GHz band not visible on clientClient device lacks Wi-Fi 6E supportVerify client spec; enable legacy fallback in admin panel
Mesh node drops connection hourlyDFS channel radar detection (5 GHz)Switch backhaul to channel 36–48 (non-DFS range)

📋 Compatibility

  • ISP compatibility: All major EU providers (PPPoE and DHCP); requires VLAN ID 835 for Orange Livebox bypass
  • Smart home: Thread 1.3 and Matter 1.2 certified; Zigbee via optional USB dongle
  • Known limitation: WPA3 enterprise mode incompatible with iOS 16.x and below — clients must run iOS 17+
This is an example — create yours in Elium

Centralise product knowledge in structured, searchable cards that support agents consult during customer interactions. Each card covers specifications, common issues, resolution steps, and related resources — so agents resolve queries from a single reference rather than searching across systems.

Try now in Elium

What is a product knowledge card?

A product knowledge card is a structured reference document that consolidates everything a support agent needs to know about a specific product — its specifications, common issues, resolution steps, and related resources — in a single, searchable format.

Support teams lose time when product knowledge is scattered across training manuals, email threads, supplier PDFs, and colleagues’ memory. A product knowledge card solves this by giving every agent the same authoritative reference. When a customer calls about a faulty feature or a compatibility question, the agent consults one card rather than searching three systems. The result is faster resolution, consistent answers, and fewer escalations caused by incomplete information.

Who should use this template?

This template is for teams that support products or services:

  • Customer Support Managers — ensure every agent has access to the same accurate, up-to-date product information regardless of experience level
  • Product Specialists — document product details, known issues, and workarounds in a format that frontline agents can use without specialist training
  • Knowledge Managers — maintain a structured product library where each card follows the same format and stays current through scheduled reviews
  • L1 Support Agents — consult a single reference during calls instead of searching across multiple systems or escalating routine queries

What’s included in this template?

The template has two parts: structured metadata fields and the knowledge card body.

Metadata fields classify each card:

  • Product name and model or version number
  • Product category or family
  • Status (active, discontinued, recall)
  • Last updated date and review owner
  • Support tier (L1 self-service, L2 specialist)

Knowledge card body covers the product in full:

  • Product overview — what the product does, key specifications, and target user segment
  • Common issues — frequently reported problems with symptoms and confirmed causes
  • Resolution steps — step-by-step fixes for each common issue, with expected outcomes
  • Compatibility and requirements — supported configurations, dependencies, and known limitations
  • Related resources — links to user guides, warranty terms, and escalation procedures

How to create and customise this template in Elium

  1. Open the Template Builder — Go to your profile menu and select the Template Builder tab, or click “+ Create” and choose “Create a new template”.
  2. Set the scope — Choose an icon, enable the template, and decide whether it applies platform-wide or to specific spaces (e.g. your Product Knowledge or Customer Support space).
  3. Add structured fields — Click “Field” to add metadata: text fields for product name and version, a tag field for product category and status, a date field for last updated, a user field for review owner, and a tag field for support tier. Mark product name and status as mandatory.
  4. Build the card structure — Use the “+” button to add content blocks: a text block for product overview, a table block for common issues and resolutions, a numbered list for resolution steps, a text block for compatibility notes, and a link block for related resources. Add placeholder prompts (e.g. “What are the three most common issues customers report?”).
  5. Preview and save — Review the template layout, then save. Agents can now create product cards using a consistent format, and you can apply it to existing content in bulk.

How AI helps you create and use this template

Capture faster. Feed Elium’s AI a product datasheet, release notes, or support ticket history. It extracts specifications, identifies recurring issues, and drafts a structured knowledge card that the product specialist reviews rather than building from scratch.

Retrieve smarter. During a call, an agent asks Elium’s AI: “What causes the blinking red light on the XR-500 router?” The AI returns the exact cause and resolution steps from the product card — no browsing, no hold time.

Why teams use Elium for product knowledge

Product knowledge has a short shelf life. New versions ship, issues are patched, and compatibility changes with every update. When product cards live in static documents, agents work from outdated information and give customers wrong answers. Elium keeps product knowledge current: structured templates enforce consistent format, tags filter by product family or issue type, and AI search returns answers from a question.

Fnac Darty — 1,800 customer advisors across 11 call centres — manages 2,000+ procedures in Elium. Their agents moved from asking colleagues for answers to finding them instantly through AI-powered search. The result: 80% first-contact resolution and a 10% reduction in call handling time. When agents trust their knowledge base, they resolve issues on the first call.

Frequently asked questions

A product knowledge base is a centralised collection of structured reference cards covering specifications, common issues, and resolution steps for each product. Without one, agents search multiple systems or rely on colleagues, which increases handling time and creates inconsistent answers across the team.
A complete card includes metadata (product name, version, category, status, review owner) and body sections covering product overview, common issues with documented symptoms and causes, resolution steps, compatibility requirements, and links to related resources such as user guides and escalation procedures.
Structured product cards reduce average handling time because agents find answers in one place. They improve first-contact resolution because every agent — regardless of tenure — accesses the same accurate information. They reduce escalations because L1 agents resolve issues that previously required specialist knowledge.
Start with the most common customer issues — the questions agents hear daily. Document the symptoms, confirmed causes, and step-by-step resolutions. Add product specifications and compatibility details. Assign a review owner and set a review date tied to the product update cycle so the card stays current.
A product knowledge card is an internal reference for support agents — detailed, technical, and covering edge cases. A customer FAQ is external-facing — concise, non-technical, and answering the questions customers ask most. The knowledge card feeds the FAQ: when agents document a new resolution, the FAQ is updated to reflect it.

Related reading: Read more on our blog