4.3 Knowledge, Portal & Virtual Agent
Key Takeaways
- Service Portal is the modern, mobile-responsive self-service interface built from portals, pages, and reusable widgets, served at /sp by default and separate from the platform UI.
- A Knowledge Base (KB) organizes articles into categories on the kb_knowledge table; access is controlled by user criteria for read (can view) and write (can contribute) permissions.
- Knowledge answers questions and shares information, while the Service Catalog fulfills requests for products and services; an FAQ belongs in knowledge, a laptop request belongs in the catalog.
- Virtual Agent is a conversational chatbot that runs topic-based conversations to resolve issues, search knowledge, and create or check requests without a live agent.
- Self-service deflection is the practice of resolving user needs through knowledge, catalog, and Virtual Agent so fewer issues become agent-handled tickets, lowering cost per interaction.
Why Self-Service Channels Matter for the CSA Exam
Users should be able to help themselves before they ever contact an agent. ServiceNow delivers self-service through three connected capabilities: Service Portal (the interface), Knowledge Management (the answers), and Virtual Agent (the conversational assistant). The CSA exam expects you to know what each does, how knowledge differs from the catalog, and the deflection idea that ties them together.
Service Portal Basics
Service Portal is the modern, mobile-responsive web interface for end users. It is separate from the platform (back-end) UI and is designed for consumers of services rather than administrators. The default portal is reachable at the /sp URL.
Service Portal is assembled from a small set of building blocks:
| Element | Role |
|---|---|
| Portal | The top-level container with a URL suffix, theme, and homepage |
| Page | A screen within the portal, built on a responsive grid |
| Widget | A reusable, self-contained UI component (search, catalog, KB) |
| Theme | Branding: colors, logo, fonts applied across the portal |
Administrators configure portals and pages and place widgets without rebuilding the platform UI. A single instance can host multiple portals — for example, an IT portal and an HR portal — each with its own branding and content.
Knowledge Base Structure
Knowledge Management captures and shares information so users can solve problems themselves. The structure has three levels:
- Knowledge Base (KB) — a top-level container for a subject area (IT, HR, Facilities), stored on
kb_knowledge_base. - Category — a grouping of related articles inside a knowledge base; categories can nest.
- Article — an individual document on the
kb_knowledgetable, moving through Draft, Review (if workflow requires), and Published states, with optional expiration and retirement.
Access is governed by user criteria: can read criteria decide who can view a knowledge base, and can contribute criteria decide who can create or edit articles. User criteria can match users, groups, roles, companies, departments, or locations.
Knowledge vs. Catalog
A recurring exam distinction: knowledge informs, the catalog fulfills.
| Aspect | Knowledge Base | Service Catalog |
|---|---|---|
| Purpose | Share information and answers | Order products and services |
| Typical content | How-to articles, FAQs, policies | Laptop request, software access |
| User outcome | Reads and self-resolves | Submits a request that gets fulfilled |
| Core table | kb_knowledge | sc_cat_item |
If a user asks "how do I connect to the VPN?" that is a knowledge article. If a user needs "a VPN token issued to me" that is a catalog request.
Virtual Agent Overview
Virtual Agent is ServiceNow's conversational chatbot. It runs topics — predefined conversation flows built in Virtual Agent Designer — that gather input, search knowledge, create or check requests, and resolve common issues without a live agent. ServiceNow ships prebuilt topics (password reset, order status, create incident) that administrators can clone and adapt.
Key Virtual Agent concepts for the exam:
- Topic — a guided conversation that accomplishes one goal (reset a password, check a request).
- Natural Language Understanding (NLU) — optional intent matching that routes a user's free-text message to the right topic.
- Live Agent handoff — when Virtual Agent cannot resolve the issue, the conversation can transfer to a human agent.
Virtual Agent is typically surfaced inside Service Portal or a mobile app as a chat widget, making it a first-line self-service channel.
Self-Service Deflection
Deflection is the goal that connects portal, knowledge, and Virtual Agent: resolve a user's need through self-service so it never becomes an agent-handled ticket. Every question answered by a knowledge article, every request completed through the catalog, and every issue closed by Virtual Agent is a deflected interaction.
Deflection matters because self-service resolution is dramatically cheaper and faster than agent handling, and it frees agents for complex work. On the CSA exam, expect deflection to be framed as the business reason knowledge, catalog, and Virtual Agent exist — not as a separate feature, but as the outcome the whole self-service stack is designed to produce.
Putting It Together
A mature self-service experience layers all three: the user opens Service Portal, asks Virtual Agent a question, Virtual Agent surfaces a knowledge article or a catalog item, and the need is resolved without a ticket. When self-service genuinely cannot resolve the issue, the platform creates an incident or request for an agent — the correct fallback, not a failure.
A user wants to read step-by-step instructions for configuring email on a new phone. Which ServiceNow capability is the correct home for this content?
Which Service Portal element is a reusable, self-contained UI component such as a knowledge search or catalog block?
Which mechanism controls who can view or contribute to a knowledge base in ServiceNow?
In self-service terms, what does 'deflection' refer to?