How Nordic Semiconductor deploys Kapa across docs, support form and MCP server
“Kapa connects every source we have -
PDFs, codebase, versioned documentation -
and keeps it all in sync as we ship.”
Diedre Casey
AI Integration Manager
Challenge
Answers live across versioned docs, datasheets, SDK code, and years of DevZone history, and the support queue carries a high share of questions the knowledge base already answers.
Solution
Run Kapa on the docs, the DevZone support form, and a hosted MCP server, with every source connected to one corpus and kept in sync as SDKs and silicon evolve.
Results
Thousands of customer queries addressed daily across four surfaces
Over 82% of users found answers helpful
Over 100,000 queries inside coding agents
Over 45% of queries answered in non-English languages
Over 150,000+ hours saved in support hours
Documentation Agent
One cited answer instead of five tabs
A chat agent embedded on your docs site that answers natural-language questions with citations back to source. On docs.nordicsemi.com it draws on user guides, SDK references, and datasheets, staying accurate as silicon and the nRF Connect SDK evolve.
Play video
Support Form Agent
Repeat questions caught before the DevZone queue
An agent that sits in your existing support form and suggests an answer before the ticket is filed, escalating with full context when it can't help. At the DevZone intake it deflects the repeat questions the knowledge base already covers, so remaining tickets resolve faster.
Play video
MCP Server
nRF Connect SDK context for coding agents
A hosted MCP server connected to your knowledge base, added to Cursor, Claude Code, or ChatGPT in one click. Nordic uses it to ground coding agents in the nRF Connect SDK, APIs, and hardware specifics as developers build.
Play video
Why Kapa
Every deployment runs on the same corpus and answer engine, so an answer in the docs, at the support form, inside a Nordic-built experience, through the Retrieval API, or in a coding agent stays consistent and traceable to source.
Nordic adds a surface without rebuilding its knowledge base, and updates reach every agent at once as SDKs and silicon evolve, which is how a focused documentation and support organization keeps pace with a global engineering community.
