Help center Knowledge base and KCS Find and use the right knowledge article Updated Thursday, November 5, 2026 · A useful knowledge search should lead to an answer that fits the customer’s actual problem. The Knowledge Base workspace lets you search, browse topics, and narrow the article list. Check the article’s scope and audience before relying on it or sharing a link. At a glanceFor: agents, specialists, and knowledge contributors. Applies to: Supportbench Core.Start here: Knowledge base in the agent navigation Search and narrow the list · Find knowledge from a Case · Check that the answer fits · Verify a customer can use the article · When knowledge is missing or unclear · Build a useful search habit · Work a search from the customer’s words to a usable answer · Share instructions the customer can actually follow · Arrange content in Core Search and narrow the list Open Knowledge base and check the Division selector. Your access and selected scope affect the available articles.Enter a title, product name, phrase, or the customer’s error wording in Search the knowledge base. If needed, try the customer’s wording and the product’s formal term separately.Browse Topics when the category is clearer than the title. Use Filters and inspect the active filters before concluding that an article is missing.Use a saved view for a repeatable working list. Choose useful metadata with Columns, and use Export when an authorized offline list is needed.Open a candidate article and read the applicable version, prerequisites, steps, and expected result. Confirm the article’s publication state and audience. Choose article source and permitted Division scope before adding conditions. Apply filters changes the list; Save view is separate. This is the empty dialog before applying or saving. Find knowledge while working a Case Use the Case knowledge panel when you want to investigate an issue and compare possible answers without leaving the customer conversation. It is a focused search and preview panel, separate from the full Knowledge Base workspace. You need access to the Case and its available articles. Linking also requires permission to change the Case; being able to read a result does not necessarily let you change its relationships. Open the relevant Case and select Activities. Select Articles in the activity toolbar to open Knowledge. Confirm that you started from the intended Case.Review the Case suggestions, or enter a distinctive problem term in Search knowledge Articles and select Search. Enter at least two characters. Start with the product operation or error, rather than a customer name or a long conversational request.Select a result to read its preview. Use Previous Article and Next Article to compare candidates, or Open article for the full reader. Check applicability, prerequisites and the expected outcome before using the answer.Interpret Best, Strong and Related as relative ranking within the results. These labels are not confidence percentages or confirmation that the procedure will resolve this customer’s issue.Check the audience marker. The globe identifies an External article; the lock identifies an Internal article. External is portal eligibility, not proof that this customer can open the article. Verify the intended customer’s access separately before sharing. Keep internal diagnostics out of customer replies.When the article genuinely applies and you want to record its relationship to the Case, select Link to case. Check for the Article linked to Case. confirmation. Linking records reuse; it does not insert instructions into an activity, copy attachments, send a message or establish that the issue is resolved.Close the panel when you have finished reviewing. Compose and review the customer’s next steps through the normal activity workflow. Record what you tested and the result; an article association is not a substitute for that customer-specific evidence. Worked example: a password reset link has expired A contact cannot use a reset email while a colleague at the same organization can still sign in. Search password to identify the relevant family of guidance, then try reset link expired to focus on the observed error. Compare the forgotten-password article with the expired-link procedure. The first result may describe starting a reset rather than recovering from an expired link. Choose the article that fits the actual symptom and the customer’s portal, check its access, and explain the next action and expected result in your reply. Link the article only after confirming that it is useful to this Case. Recover when the first search is not useful No confident suggestions: this is not proof that no article exists. Search manually using a short, distinctive symptom or the product’s formal name. The demo returned no confident Case suggestions but did find relevant articles after a manual search.A manual search took you away from the Case suggestions: clear the search field to return to the current ticket suggestions. Recently viewed articles are a separate list, not evidence that they match the current problem.A promising result has the wrong audience or instructions: do not copy it into an unrestricted reply. Find an approved customer procedure, or ask its owner for an appropriate companion article.The article needs a correction: use Flag for update when available. Describe the exact step, missing prerequisite or scenario and the expected correction. A suggestion enters the review workflow; it does not immediately rewrite the article.Linking is unavailable or fails: confirm the Case is editable and that you still have access to both records. Ask an authorized owner to resolve the restriction. Do not interpret a failed link as a sent reply or retry an uncertain result without checking what was saved. Check that the answer fits CheckWhy it mattersProduct and versionSimilar symptoms can have different procedures in different releases or environments.Customer relationship and assetThe organization may use a different supported item or configuration from the example.Prerequisites and permissionsA customer cannot follow a step that requires an agent or administrator capability they do not have.Expected resultA documented verification step helps distinguish a successful resolution from a temporary symptom change.Audience and publicationAn internal or restricted article should not be copied into a public reply merely because the agent can open it.Example: recurring equipment faultSearch the symptom and equipment family, then compare the article’s prerequisites with the affected asset. If the article applies, use its verification step to confirm the result. If the customer’s situation exposes a missing exception, flag that specific gap rather than creating a near-duplicate article. Verify a customer can use the article External means portal-eligible; it does not alone prove public access. Workflow publication, portal and topic rules, customer roles, and article restrictions must also permit the intended reader. Topic placement and search visibility do not override those controls.Use the current canonical article link when sharing approved customer guidance.Check the intended customer context when an article is restricted by role, asset, or other configured scope.Keep internal diagnostics in the internal case workflow; share the customer-safe procedure instead.If access fails, ask the article owner or administrator to review its publication and audience rather than copying restricted material into an unrestricted location. When knowledge is missing or unclear Clear unintended filters and confirm the division. Try another useful phrase, then browse the relevant topic.Check whether the answer exists under a different product term or title.Use Flag for update when available to identify a wrong step, missing scenario, or unclear outcome. Include the exact issue and safe supporting evidence.For a genuinely new, verified resolution, follow the case-to-article and authoring workflow. Search before creating another article. Build a useful search habit Search early in the investigation, then search again when the cause is clearer. Reusing verified knowledge gives the next agent a common starting point. Report recurring search terms to the article owner so titles, summaries, and Search keywords reflect how customers actually describe the problem. Work a search from the customer’s words to a usable answer Suppose the customer says “the nightly order export stopped.” You do not yet know whether the cause is a connection, permissions or the export settings. Search early for guidance, then refine as evidence develops. The examples below are suggested search phrases, not guaranteed exact-match operators.What you knowTry this phraseWhat to do with the resultOnly the customer symptomnightly order export stoppedLook for the relevant feature and identify the prerequisites it asks you to check.The product operationorder export connection failureCompare the product/environment with the case; discard procedures for a different connection type.A verified errorThe exact error text plus the product nameCheck whether the article covers that error and the customer’s version, rather than a superficially similar symptom.Open Knowledge base, confirm Division, and enter the first useful phrase. Inspect active Filters if the result is empty or surprisingly narrow.Open a promising article. Read its purpose, applicability, access requirements and expected result before trying a change. A matching title is a candidate, not a diagnosis.If it does not fit, return to the result list and adjust one part of the search. Try the formal feature name, the customer’s wording, or a shorter distinctive error. Browse Topics when you know the feature family.After the cause is clearer, search again. The correct solution may use a different term from the original symptom.If the article resolves the issue, record the customer-specific test and result on the case. If a step is missing, flag the precise gap so the next reader does not need to rediscover it. Share instructions the customer can actually follow Before sending an article about portal access, check whether the steps are meant for a customer, an agent or an administrator. A technically correct administrator procedure is not a useful self-service answer for a contact who cannot open Settings. Explain the customer’s next action and link the appropriate guide; keep the administrative dependency with its owner.Use the canonical link and confirm intended access. If you can open the article but the customer cannot, check its publication, portal/topic rules and restrictions rather than assuming the URL is broken. Do not copy internal diagnostics into the customer reply to bypass the restriction. When the article is too technical, ask for a companion customer procedure instead of repeatedly writing private, unmaintained versions in email. Arrange content in Core Topic administrators can choose Arrange content, select a topic, enable Custom order for Subtopics or Articles, move items, and Save order. Pinned articles stay above Other articles. Top and Bottom act on the whole group, including later pages. Find in this list locates a distant entry without replacing the full arrangement. Standard Core browsing follows that saved sequence; search relevance, AI retrieval, latest/popular lists and explicit grid column sorts keep their own ordering. Clear an explicit grid sort before comparing it with the organizer. Legacy views keep their existing order.These controls require a Core release with Arrange content and its optional storage available. For permissions, complete procedures, keyboard and touch controls, examples, reset, conflicts and restoring Existing order, follow Arrange topics and articles without changing their legacy priority. Continue learning Create, review, and publish an articleFlag an article for updatePractice KCSConfigure knowledge-base topics Track your drafts and review submissions — upcoming, not deployedRelease status: This enhancement has been implemented and validated locally but is not deployed yet. The following steps describe the upcoming release and may not be available in your workspace.Knowledge Base → Action Items → My drafts & submissions brings your saved draft articles and proposed updates together. Use it to follow your own contribution after work is assigned to another agent. My assigned articles instead follows the current owner. Neither list grants additional article or Division access. You need existing Knowledge Base access. The list contains work identifiable as your saved draft revision or review submission, including revisions you last edited and articles you published directly. Unsaved editor text is not included. Deleted revisions and Trash are excluded; accessible archived articles remain available as history. Open Knowledge Base and expand Action Items. Select My drafts & submissions.Check the Division selector and active filters. The default list includes all personal work statuses without a date cutoff and sorts by Last activity, newest first. The badge counts distinct articles, not review rounds.Read Revision and My work status alongside Article status. There is one row per article, showing your latest qualifying work. A newer unsubmitted draft takes precedence over an older submission, even when a decision on that older submission arrived later.To narrow the list, choose Filters → Add condition → My work status, choose is and the required status, then select Apply filters. Use Title, Last activity or Submitted conditions when needed. Search matches your revision title, article ID and the article's title/summary; it is not a search through every historical revision body.Open the article by its title or ID. Use its authorized Review history to read feedback and earlier decisions. The list's Reviewer identifies the recorded decision author and can remain blank while work awaits review.Use Columns to select metadata, Save view for repeatable criteria, or Export for the complete authorized filtered list across all pages. A personal saved view resolves to its signed-in reader's own work, not the view creator's identity. Personal work statuses describe your selected revision and review roundMy work statusMeaning and next step DraftYour saved revision has not been submitted for review. Open it and continue drafting or use the permitted submission action. Pending reviewYour latest review round is awaiting a recorded decision. Check Submitted and the article's Review history before submitting again. Changes requestedThe reviewer returned the submission for edits. Read the feedback, revise the draft and submit the correction through the existing workflow. RejectedThe review round was rejected. Read the explanation and any authorized duplicate-article reference before deciding whether to revise or reuse existing knowledge. ApprovedThe reviewer approved the work; this does not establish that the revision is already published. Check its publication schedule and current reader content. PublishedThe selected contribution has a publication decision or direct revision publication evidence. The article's current lifecycle and customer visibility remain separate checks. Review history unavailableThe available storage/history cannot establish the decision. This does not mean rejected or approved. Ask an administrator to check the review-history setup; do not create a duplicate to bypass it. Worked example: an existing article is Published. You submit revision 4 to correct its refund instructions. Your row shows My work status: Pending review and Article status: Published; readers continue using the existing published revision. If revision 4 is Approved for a later publication date, its personal status remains Approved until publication is recorded. A rejection of revision 4 does not mean that the existing published article was removed. Reporting versus your working list: open Reporting → Knowledge Base Reports → Report Type → Contribution outcomes for completed outcomes when that report is available in your release. Its deployment to Jackrabbittech has not yet been verified. It separates flagged articles marked Completed/Rejected from submitted drafts marked Published/Rejected. Credit belongs to the submitting agent and date filters apply to the outcome date, not the submission date. It does not replace this personal list of drafts and pending/approved work. If work is missing: save the draft first, check Division and active filters, and verify that you created or last edited that revision or submitted its review. One article can have several revisions but only one personal-list row. Ownership alone does not establish authorship; reassignment does not itself remove a recorded submission, although a change in permissions can make the article unavailable. Older imported records may lack durable authorship/review history. Open the article through its normal authorized controls to check earlier work. Flag a passage for an internal update review Release status. Coming soon — not deployed yet. These passage actions and markers will become available after the matching release and verification for your account. Use passage feedback when an instruction needs correcting and a reviewer needs to know exactly which wording you mean. This feature is available in the internal article reader and Ticket Knowledge drawer only. You must have article and Division access, Knowledge Base availability and the Flag articles for review permission. Configured reasons are required when starting a new suggestion. Customer-facing portals never show passage flags, request counts or feedback. An agent with the required permission can flag an article in the internal application even when that article is also published publicly. Feedback details, restricted draft history and originating ticket links retain their separate access checks. Open the article inside the agent application, either directly or from the Ticket Knowledge drawer. Select the exact wording, or use the flag beside a paragraph, list item or section heading. The action becomes visible on hover or keyboard focus and is available on touch screens. A heading action captures its section up to the next heading of equal or higher level. Check the Selected passage quote and section name. Expand a long quote with Show more. Remove an unwanted passage before selecting another. Sections longer than 4,000 characters require a shorter selection. Your explanation remains in the form. Keep or remove the originating ticket badge. Choose a reason for a new suggestion, explain the correction and select Flag for update. If a suggestion already exists, read it and explicitly add your information to that thread. After a confirmed save, look for the passage flag marked Update requested. Open Update requests to navigate passage feedback, whole-article requests and contributions whose wording cannot be located. Example and expected result An article tells agents to choose Account settings to configure a payment gateway. Select that sentence and explain that the current menu is Integrations. The reviewer sees the saved quote beside your explanation, with an authorized ticket link when included. The original quote remains in the discussion after the article changes. The marker stays attached only while the wording and section can be located unambiguously. Review and recovery All contributions belong to the existing article-level suggestion. New and In progress suggestions keep their markers. Completing or rejecting that suggestion clears its active markers while preserving history. Flags inside overlapping passages share a marker. Ordinary whole-article feedback has no passage location. Passage could not be located means the wording was changed, removed, repeated ambiguously or is unavailable in the displayed locale. Open the authorized feedback history to inspect its original snapshot. Do not assume the marker has moved to equivalent wording. If a save is unconfirmed, use Retry previous save to resolve the same submission. If content changed before submission, keep your explanation, remove the stale quote and select current wording. If controls disappear, ask an administrator to verify the flagging permission, article access and account capability. Existing review-history access is separate from permission to submit new flags. Find an answer when the ticket is brief or the wording is unusualUse the knowledge lightbulb to open the ticket article panel even when no automatic results are available. A number appears only for current suggestions; no number means you can still search. Suggestions are possible answers for an agent to review, not proof of the customer's cause, product or payment state.Open the ticket and select the knowledge lightbulb. Leave the search field empty to review suggestions from the conversation. Loading, no matches and a failed lookup are separate states; use Retry for a failed lookup.Read the title, audience and status. For a blocked action such as “won't let me delete a fee,” review troubleshooting before using a generic how-to. Check whether the article's conditions apply; the wording alone does not prove a payment was refunded.For a difficult request, choose Improve suggestions. Account AI availability and the AI article search and Improve suggestions role permission are required. The button is disabled during its request. Opening the panel, clearing the search and Retry do not invoke this AI step.For a broad topic such as “quick question about the waitlist,” review the relevant guides and ask what the customer needs to do. A request such as “can someone call me” can suggest a support-call booking guide when one is available to you.If the customer's wording is ambiguous, use a suggested article as a possibility. For example, “on the list” may refer to a waitlist or an enrollment list. Confirm the intended list before giving its procedure.Type a more specific phrase to search manually. Clear the field to return to ticket suggestions. Select Open article to inspect the full authorized article before inserting approved content or a public link.Related drafts can help prevent duplicate authoring. They appear only when their permitted title or summary provides relevant evidence. A draft or review result opens a metadata preview with its workflow status; it does not become an approved answer, customer link or auto-reply source. Use Open article to inspect the work if your permissions allow it.The list can contain up to ten suggestions, including useful answers to separate questions in the same ticket. A shared general word is insufficient by itself. A shorter list can be appropriate, but manual search remains available. If an expected article is missing, record the ticket ID, exact wording, article title/ID, whether you used Improve suggestions, and its observed position. Report missing access or a failed lookup separately from poor relevance. Understand search matches and ranking Supported Core plain-English manual searches preserve configured multiword AI Terms before reducing grammatical filler. Hyphenated compounds such as drop-in and their plurals are treated as one configured concept; joined spellings such as dropin must be configured as aliases. Actions, numbers and negative intent remain useful evidence. A question about offering drop-in classes may rank differently from a question about scheduling one. ExperienceWhat affects the orderPopularity and datesTyped Knowledge Base, Help Center, agent and public chat-widget manual searchesConcept coverage, reliable wording, complete title/keyword phrase, intent, weighted title/keyword evidence, title specificity, spelling/equivalence quality, indexed rank and stable article ID.Views, links and article recency do not boost this relevance order. An explicit date or popularity sort changes the selected sort.Automatic Case suggestions and Improve suggestionsConversation context, candidate retrieval, topical/action/problem qualification and focused relevance. Improve is an explicit agent action.Existing candidate popularity remains a tie-breaker after focused relevance; the newest article does not automatically win.Case AI auto-replies and Help Center answersFocused source queries followed by current publication, access and answer-qualification checks. A source match is not a promise that an answer can be generated.These answer paths are not a popularity recommendation list; their query plans and eligibility can produce fewer sources than manual search. The chat widget uses the shared relevance rules for supported English manual searches and questions answered from knowledge articles. Results follow the widget’s configured public topics and visitor access. Before using an article in an AI answer, Supportbench checks that it is still published, accessible, usable and permitted for AI. An AI answer can therefore use fewer sources than manual search, and a focused follow-up query can change their order. Turning off the manual Knowledge Base panel does not turn off the separately configured AI responder. If a configured Division cannot be resolved, Supportbench does not widen the search to other Divisions. Independently configured Intercom sources remain available if Supportbench article retrieval fails. The existing AI source-language contract remains English; the answer-language setting does not change which article language is searched. Basic search syntax, exact IDs and unsupported-language fallbacks retain their existing rules. Equivalent queries should be compared against the same accessible content and the same relevance sort. Different visitor roles, divisions, topics, languages or article states can change which records are eligible. For an administrator's top-20 test and a read-only keyword-priority comparison, see Configure preferred terminology for AI and search. Core Help Center typeahead and Premiere search-result titles and summaries highlight literal occurrences of accepted search equivalents, including configured drop-in spellings. Highlighting does not change ordering or article content. Older custom templates without the Premiere result structure may need template work before they display those marks. Full article bodies and an AI provider's generated answer are not highlighted by this search-result control. Objective and Solution headings are useful ways to write an answer, but are not required for search eligibility. A passage containing related words together can be useful supporting evidence; it does not prove the procedure applies. No new passage-based ranking rule has been activated. Continue writing clear, focused sections with the actual action, conditions and limitations, using whichever headings fit the article. Was this article helpful? Yes No Thank you for your feedback.