SupportCandy Knowledgebase Integration - WordPress Plugin

How to Set Up SupportCandy Knowledgebase Integration for a WordPress Support Team

SupportCandy Knowledgebase Integration is not just about adding one more button to the admin panel. Its real value shows up when your support team already maintains a knowledge base and wants to use it directly inside tickets: quickly find an article, insert a link or a ready-made instruction snippet into a reply, and surface relevant materials for the agent based on the subject of the request.

In this guide, we will look at when this setup is genuinely useful, what to check before installation, how to enable the integration in WordPress, how to prepare your knowledge base articles, how to use suggestions in replies, and how to validate the result with a test ticket. We will also cover common issues: an empty article list, weak tag matches, permission problems, confusion between FAQ content and full documentation, and cases where an agent pastes too much article content instead of sending a clean link.

This guide is written as a practical reference for sites where SupportCandy is already used as the ticketing system or is being introduced together with a knowledge base. It does not replace the official documentation, but it helps turn that documentation into a working process: from installation and initial checks to a real-world "ticket - article - reply - result check" workflow.

What the Knowledge Base Integration Does in SupportCandy

A standard knowledge base on a website works on the public-facing side: a visitor opens the help section, searches for an issue, reads an article, and if that still does not solve the problem, creates a ticket. In practice, that flow often breaks down. The user may not find the right article, may not know the right term to search for, may open a ticket immediately, or may describe the issue in a way that forces the agent to manually repeat instructions that already exist.

SupportCandy Knowledgebase Integration brings the knowledge base closer to where ticket work actually happens. A knowledge base link appears in the reply interface. According to the official documentation, clicking it opens a pop-up with articles grouped by category. The agent can insert material into the reply in two ways: as an article link or as the article content itself. For a support team, this changes not the look of the site but the discipline of answering tickets: instead of improvising, the agent works from prepared documentation.

The second important mechanism is suggestions through macros. SupportCandy documentation describes matching the ticket subject against knowledge base article tags and surfacing the most relevant materials. This is not a full search engine with guaranteed perfect results, so it should not be treated like magic. But if your knowledge base has well-written titles, categories, and tags, agents can spot likely instructions faster and spend less time searching.

The integration supports several popular WordPress documentation plugins. The official product page lists BetterDocs, WP Knowledgebase, Knowledgebase by UnboundStudio, Knowledgebase by HeroThemes, BasePress Knowledgebase, BWL Knowledge Base Manager, Echo Knowledge Base, KBx Knowledgebase, and weDocs. That matters because SupportCandy does not become its own knowledge base. It connects to the documentation tool you have already chosen. As a result, the quality of the outcome depends not only on the add-on, but also on how well the articles themselves are organized.

Where the Integration Is Especially Useful

The strongest use case is repeat requests where the answer should already be standardized: access setup, password reset, form errors, service payment instructions, order status checks, integration setup, explaining plan limits, or a step-by-step onboarding path for a new customer. In those situations, the agent does not need to rewrite a long instruction from scratch. It is enough to open the knowledge base from the ticket, find the article, and add it to the reply.

Another strong use case is training new support staff. A new agent does not always remember where the right instruction lives, how to phrase the answer correctly, or which details cannot be skipped. The integration helps use documentation as an internal reference right in the middle of the workflow. It does not replace team training, but it lowers the risk of agents replying off the top of their heads.

The benefit is noticeable for customers too. When an agent inserts a link to an article, the user gets more than a short answer. They get a page they can reopen later, forward to a colleague, or use again after the ticket is closed. If the article includes screenshots, result checks, and updatable information, a link is usually better than a long block of text in an email.

How This Differs from Canned Replies and FAQ

SupportCandy includes canned replies, which let an agent reuse saved responses for common situations. That works well for short templates: a greeting, a request for more information, a standard notice, or a link to your support policy. But a canned reply is not always a good fit for a full instruction. A knowledge base article is usually structured better: it has headings, images, a sequence of steps, explanations, updates, and context.

FAQ integration solves a related but narrower problem. FAQ works well for short question-and-answer pairs, while a knowledge base is better for full documentation. If your incoming requests are mostly things like "where is the button," FAQ may be enough. If the user needs to complete several steps, understand a setting, or verify the result, Knowledgebase Integration is the better fit.

Who SupportCandy Knowledgebase Integration Is For and When Another Approach Makes More Sense

The integration is a strong fit for sites where support is already answering the same types of questions over and over, while the knowledge base lives separately from the ticket system. That can include a WordPress site with digital products, a customer account area, a learning platform, SaaS documentation, a service portal, an online store with technical products, or private documentation for clients. The main sign of a good fit is this: the team has repeatable scenarios that are easier to resolve with a link to a solid article than by explaining everything again every time.

SupportCandy Knowledgebase Integration also makes sense for teams that need more consistent answer quality across agents. If one employee writes detailed replies, another sends very short responses, and a third regularly forgets critical steps, a shared knowledge base becomes a single source of truth for wording. The agent still writes a human response, but it is grounded in a verified instruction.

You should not expect much benefit if you do not really have a knowledge base yet. You can technically enable the integration, but an empty or chaotic documentation section only adds another source of confusion. In that case, create at least 10-20 articles covering your most common requests first: account login, core errors, setup steps, limitations, known issues, contact details, and ticket handling rules. Only then does the integration start saving time.

Good-Fit Projects

• Sites with active support where users create tickets about recurring issues.
• Product sites where documentation needs to be available both to the user and to the support agent.
• Teams using BetterDocs, BasePress, Echo Knowledge Base, Heroic Knowledge Base, or another supported documentation plugin.
• Projects where answers need to stay consistently accurate without reading like mindless template blasts.
• Sites where reducing repeat tickets matters, and updated instructions can be shared through article links.

When the Integration May Not Be the Right Fit

If support mostly handles unique one-off cases, a knowledge base will help less. For example, if every ticket requires manual contract review, a custom calculation, or access to an internal system, a prepared article will only be a supporting resource. In projects like that, it matters more to properly configure ticket fields, agent roles, private notes, and escalation rules.

The integration also does not replace good on-site search. If users cannot find an article in the public knowledge base because the structure is poor, the agent may still find it inside the ticket workflow, but the self-service problem remains. Your knowledge base has to make sense to a human first: clear titles, categories, tags, current screenshots, links between articles, and a short result check at the end of each instruction.

Finally, pasting the full contents of an article should not become your default answer strategy. If the article is long, it will turn into a wall of text in email. In most cases, it is safer to send the link and add 2-3 lines of personal context: which part applies to the ticket, which step the user is stuck on, and what to verify after following the instructions.

What to Check Before Installation and Activation

Before installing the add-on, check more than WordPress itself. Make sure the workflow is ready too. SupportCandy Knowledgebase Integration depends on three layers: the core SupportCandy plugin, the knowledge base plugin you chose, and the quality of your articles. If even one of those layers is not ready, the agent may see an empty panel, irrelevant suggestions, or materials that cannot be safely sent to the customer.

Start with core SupportCandy. Your support pages should already be configured, because the user needs to create a ticket and then open it on the public side of the site. In the official documentation, the full support page uses the shortcode [supportcandy], and the standalone new ticket form uses [wpsc_create_ticket]. If your site still does not display the form or the ticket list, testing Knowledgebase Integration will be incomplete: you may be able to enable the setting, but you will not be able to validate the real user journey.

Next, check your agents. According to SupportCandy documentation, administrators are added as agents by default, but for a real team you need to create users and assign them roles in the agents section. That matters for more than ticket access. Knowledge base integration is built into the reply screen, so the test should be performed not only by the site administrator, but also by a normal agent with real permissions.

Minimum Checklist Before Enabling It

• SupportCandy is installed, activated, and displays a working support page.
• There is at least one test agent who can see tickets and reply to them.
• One of the supported knowledge base plugins is installed, not a random FAQ or wiki tool that the add-on does not support.
• The knowledge base already has categories, tags, and a few articles that are safe to show to customers.
• Public article links open without authentication if those articles are intended for customers.
• Private articles are not being sent to customers by mistake if your documentation is split into public and internal content.
• The reply editor in SupportCandy is configured so the agent can insert links and formatted text without breaking the email.

Preparing Knowledge Base Articles

The most common implementation mistake is enabling the integration before the knowledge base is actually ready for support use. Articles should be written as instructions, not blog posts. The title should contain a question or an action, the opening should briefly explain the task, then come the steps, then the result check, and finally an "if this did not work" section. That structure helps both the user and the agent.

Tags matter especially because of the suggestion mechanism. SupportCandy documentation describes matching the ticket subject against words in article tags. That means the tags should reflect the language users actually use, not just internal feature names. If a user writes "I am not getting the email," the tag email may be less useful than a set of meaningful tags like notifications, mail delivery, and SMTP. In a Russian-language knowledge base, Russian tags may work if the selected KB plugin can search them correctly, but for an English-language support interface it helps to maintain one consistent vocabulary.

Practical check: before installing the add-on, create three test articles for your most common support requests and one test ticket with a similar subject. If the agent cannot quickly tell which article to choose, the problem is not the integration. It is the structure of the knowledge base.

Installation and Initial Verification in WordPress

SupportCandy Knowledgebase Integration is installed as a WordPress plugin add-on for SupportCandy. This guide does not cover purchase, licensing, or workarounds for restricted file access. It assumes you already have the add-on ZIP file, the core SupportCandy plugin, and a selected knowledge base plugin. Work on a staging copy of the site, or at minimum create a backup before making changes.

If you are just rolling out SupportCandy, start with the official order: install the core plugin via Plugins - Add New, activate it, create the support pages, and assign them in the settings. For manual add-on installation, use the standard WordPress path: Plugins - Add New - Upload Plugin, upload the ZIP archive, and activate the plugin. After activation, do not enable every extra extension at once. Keep the test narrow: SupportCandy, one KB plugin, and Knowledgebase Integration.

After installation, open the WordPress admin panel and go to the SupportCandy settings. The documentation points to Support - Settings - Knowledgebase. In that section, choose the knowledge base plugin you want to connect to SupportCandy and save the changes with Save Changes. If your KB plugin is not listed, do not try to substitute it with a random similar option. The integration must match the tool you actually installed.

Initial Check After Enabling

1. Create a test ticket as a customer or through the test support page.
2. Open the ticket in the agent interface and find the Knowledgebase link below the reply form.
3. Click the link and confirm that a pop-up opens with a list of articles and categories.
4. Find one article by title or category and insert it into the reply as a link.
5. Repeat the check and insert the article content if your team needs that mode.
6. Send the reply and verify how it looks in the public ticket view and in the email notification if email is enabled.

Do not stop at testing the admin panel. The agent may see clean HTML while the customer receives an email with extra spacing, a broken link, or an overly long content block. That is why both channels need to be tested: the ticket screen and the email. If you use a rich text editor, check which actions are allowed for the agent and the customer. SupportCandy editor settings let you control formatting, links, images, and attachments for different user types.

How to Roll It Back Safely

If enabling the integration causes problems inside tickets, first return the Knowledgebase setting to a neutral state or disable the add-on in the plugin list. Do not delete knowledge base articles or alter the SupportCandy structure before diagnosing the issue. In most cases, a safe rollback looks like this: disable the integration, verify that the reply form works normally, then enable it again after fixing the selected KB plugin, access permissions, or tags.

If the issue is tied to a specific KB plugin, test that plugin on its own: do the articles open, do categories work, are there permalink errors, and does WordPress recognize the required custom post types. The integration is not supposed to fix problems in an external knowledge base plugin. Its job is to retrieve the list of materials and insert the selected one into a SupportCandy reply.

Configuring the Knowledge Base for Better Ticket Suggestions

Technically, enabling the integration is easy. The harder part is shaping the knowledge base so it actually helps the agent. SupportCandy documentation says macro suggestions are built by matching the ticket subject against article tags. That leads to a simple rule: if the ticket subject is written in the user's language, but the article tags are written in internal developer language, the matches will be weak.

Start with a map of recurring requests. Take recent tickets and group them by task: account login, password reset, payment failure, file problem, plan question, integration setup, email complaint, unclear order status. Each group should have one primary article and, if needed, a few supporting ones. Do not create five nearly identical articles with different names. That makes it harder for the agent to choose correctly and harder for the user to tell which one is current.

Titles, Categories, and Tags

A strong article title answers the user's question and includes an action. For example, instead of "Email settings," it is better to use "What to check if ticket emails are not arriving." Instead of "Account," use "How to restore access to your account." Phrasing like that helps both readers and internal knowledge base search. Use categories as navigation across product areas, and use tags as a vocabulary of symptoms and terms.

For SupportCandy Knowledgebase Integration, the "symptom - cause - article" pattern is especially useful. If the ticket subject is "I do not see the submit button," the article might use tags like form, submit button, theme conflict, and required field. If the user writes "I cannot upload a file," the tags should cover attachment, file size, and allowed types. You will not build that vocabulary in one evening, but you can start with the most common topics and expand it based on real incoming requests.

When to Insert a Link and When to Insert the Article Content

The official documentation describes two insertion options: a link to the article or the full content. A link is better when the article is long, contains images, gets updated over time, or may need to be reopened later by the user. The full content works well for a short instruction with a few steps, especially if the user is already inside the ticket and should not have to open another page.

A practical internal rule looks like this: use a link for documentation, use content for a short answer. If the article is longer than one screen, send the link and add a personalized note. If the article contains 3-5 steps and no complex images, you can paste the content, but the agent should still adapt it to the specific ticket.

Macros and Prepared Replies

The SupportCandy macro list includes items for suggestions from different knowledge base systems, including BetterDocs, BasePress, Echo, HeroThemes, and other supported tools. Macros are useful not only in email notifications, but also in reply templates. If your team often sends the same kind of instructions, you can create a canned reply with a short greeting, a macro containing relevant articles, and space for the agent's personal note.

Do not turn a canned reply into an auto-dismissal. A good template should leave room for a human voice: "Based on your description, this looks like a notification issue. I added the instructions below. Start by checking SMTP and sending a test email. If you see an error during that step, send us a screenshot." That kind of reply uses the knowledge base without sounding cold or mechanical.

Practical Scenario: Closing a Recurring Ticket with a Knowledge Base Article

Let us walk through a concrete example for a site where SupportCandy is used as the support portal and the knowledge base includes articles about the customer account area. A user opens a ticket: "I am not getting the login email after registration." The team already has an article called "What to check if emails from the site are not arriving." The agent's job is not to rewrite the entire instruction, but to quickly send the most relevant material and make sure the user gets a clear next step.

Goal of the Scenario

The goal is to turn a standard ticket into a controlled reply flow: the agent sees the right article, inserts the link, adds a short note, sends the response, and then verifies that the link opens correctly and that the reply email does not break the formatting. This is a basic scenario that can be used to train new support staff.

Preparation

• A support page has been created in SupportCandy, and a test user can submit a ticket.
• The knowledge base includes an article about email delivery issues, with a clear title and tags such as email, notification, and SMTP.
• The correct KB plugin is selected under Support - Settings - Knowledgebase.
• The agent has access to the ticket and can send replies.
• The public article link opens without unnecessary authentication if the article is intended for customers.

Agent Steps

1. Open the ticket and read the subject, description, and any recent replies.
2. Click Knowledgebase below the reply form.
3. Find the article using the category list or the search inside the pop-up.
4. Insert the article link if the instruction is long or includes screenshots.
5. Add a personal note explaining where to start in the article and what information to send back if the problem remains.
6. Send the reply and open the public ticket view or the email to verify the formatting.

Example of a Reply That Does Not Sound Templated

This looks like a notification delivery issue after registration. I added an instruction article with the checks to go through: start with the spam folder, then confirm the email address and test sending. If the message still does not arrive after those steps, send us a screenshot of the last check and we will review the sending configuration on the site side.

In this reply, the knowledge base article does not replace the agent. It handles the detailed instruction, while the agent points the user to the exact path that matters for this ticket. That usually works better than a dry "read the documentation" response or dumping the full article into the message without context.

Scenario Details That Matter

If the article does not appear in the list, check the selected KB plugin, the article publication status, the category, access permissions, and whether the article opens correctly inside the knowledge base plugin itself. If the macro suggestion does not match the ticket subject, check the article tags and the wording of the subject. If the link opens for the agent but not for the customer, the article may be restricted by permissions, saved as a draft, or placed in an internal-only category.

If the agent inserts the full article content, they should remove unnecessary blocks that do not work well inside a ticket: large images, long introductions, internal notes, or links intended only for staff. For a public reply, a short, verifiable instruction plus a link to the full version is usually the better choice.

How to Verify the Result After Setup

Result checking needs to go beyond "the button is there." With SupportCandy Knowledgebase Integration, you want to verify that the entire chain works: the user creates a ticket, the agent sees the knowledge base link, the pop-up shows the right articles, the selected article is inserted correctly, the customer can see the reply, and the macro suggestions do not mislead the agent.

Create a separate test scenario and repeat it after updates to SupportCandy, the selected KB plugin, or the integration itself. On a live site, it is best to run those checks during a low-traffic period, especially if the support team is actively replying to customers.

Result Checklist

• The agent ticket view shows the Knowledgebase link below the reply form.
• The pop-up opens without errors and displays knowledge base categories or articles.
• Search or navigation inside the pop-up helps the agent find the right material within a few seconds.
• Inserting a link produces a clickable URL that opens for the customer.
• Inserting content does not break the reply formatting or add unnecessary system blocks.
• Suggestion macros surface relevant articles for the subject of the test ticket.
• The reply email remains readable and does not turn the instruction into messy HTML.
• The agent understands when to use a link and when to insert a short content block.

Metrics Worth Tracking

The integration does not automatically guarantee a lower support load, but it helps create a measurable process. Track the number of repeat tickets on the same topic, average first-response time, the share of replies that include knowledge base links, and the number of follow-up messages after an instruction is sent. If users still come back with the same question after implementation, check not only SupportCandy, but the article itself. It may be missing a screenshot, a result check, or an error-handling section.

For the knowledge base, it is useful to track zero-result searches, popular articles, and low-utility content if the selected KB plugin exposes that data. For example, Echo Knowledge Base and BetterDocs both extend search and analytics within their own feature sets. Use that data not as decoration, but as a practical backlog for improving documentation.

How to Maintain Documentation So the Integration Does Not Go Stale

Knowledge base integration inside tickets quickly reveals weak spots in your documentation. If agents send the same article every day and users still come back with follow-up questions, that article needs work. If agents consistently choose the wrong article, the titles, tags, or categories need to be rewritten. If customers open the link and still do not understand which step to take, the instruction is too generic.

Make knowledge base maintenance part of the ticket workflow. You do not need to turn agents into editors of every page, but they should have a simple way to suggest changes: add a missing symptom, clarify a step, flag an outdated screenshot, or propose a new tag. Once a week, or on another regular cycle that fits your team, the responsible editor can review those suggestions and update the materials.

The "Ticket Turns into an Article Improvement" Principle

Every recurring ticket can be treated as a signal. If the answer already exists in the knowledge base but the user did not find it on their own, review the title, category, and internal links. If the answer does not exist, create a new article or add a section to an existing one. If the article exists but the agent still has to write a long manual explanation, the instruction is not covering the real scenario.

A strong article for this integration should follow a clear chain: incoming symptom - product logic - action - expected result - what to do if it fails. For example, "the email did not arrive" should lead to checking the address, spam folder, SMTP, sending logs, and retrying delivery. If an article ends with "contact support," it is not very helpful for SupportCandy, because the user has already contacted support.

Safe Handling of Links and Styling

For public articles, use readable URLs, short paragraphs, images with clear captions, and links to related materials. Do not hide critical steps inside images without a text equivalent, because the agent may send only a link and the customer may open the article on a mobile device or from an email. If your knowledge base is multilingual, make sure the agent is sending the correct language version of the article.

If you need to visually emphasize blocks inside knowledge base articles, it is better to use features provided by the selected KB plugin or your theme. Do not introduce risky JavaScript changes into the critical ticket screen. For light visual tuning of the article itself, CSS in a child theme or another safe location for custom styles is usually enough, but only if you know the classes used by your KB plugin. This guide does not include a universal snippet because the official sources do not confirm one shared set of CSS classes across all supported knowledge base systems.

Agent Roles, the Reply Editor, and Internal Workflow Rules

After the integration is technically enabled, it is worth configuring the human side of the process separately. SupportCandy Knowledgebase Integration helps the agent find and insert an article, but it does not decide who may send public instructions, who updates the knowledge base, how outdated articles are flagged, or which materials must never be shown to customers. If those rules are left undefined, the integration quickly turns into a convenient way to send random links.

Start with roles. SupportCandy lets you add individual support agents and assign roles to them. For the knowledge base, that means an agent should have access to tickets, but not necessarily permission to edit every article. On a small site, one senior specialist may handle tickets and update instructions. On a larger team, it is usually better to split responsibilities: the agent uses the articles, the senior agent suggests changes, and the documentation editor approves them.

What a Standard Agent Should Be Able to See

A standard agent only needs to see the ticket, the reply form, the Knowledgebase link, the list of articles, and the modes for inserting a link or content. If you let agents edit all knowledge base materials without any process, the documentation quickly loses consistency: duplicates appear, terminology drifts, unverified advice gets published, and instructions lose their result checks. For most teams, it is safer to limit documentation editing to a smaller group.

At the same time, agents should have a simple path for feedback. For example, an internal note template such as: "Article," "What did not work," "How the user phrased the question," and "What step needs to be added." That way, the ticket becomes a source of knowledge base improvement without breaking the structure of the documentation. If SupportCandy internal notes are being used, those suggestions can be recorded inside the ticket and later moved into an editorial task list.

Configuring the Reply Editor

The rich text editor in SupportCandy affects how the agent formats a reply after inserting material from the knowledge base. The official documentation describes settings for different user types: agent, registered user, and guest user. For the agent, you usually want links, lists, basic emphasis, and the ability to insert an instruction cleanly. For the customer side, it often makes sense to keep a stricter set of actions so the reply form does not turn into a full HTML editor.

Check three things. First, a knowledge base link should remain clickable after the reply is sent. Second, lists from a short instruction should not collapse into a single paragraph. Third, if the article contains images, they should not accidentally be embedded into the email as a heavy content block when the agent intended to send only the link. If formatting is unreliable, set a simple team rule: long articles are always sent as links, and content is pasted only for short text instructions.

A Simple Team Policy Template

Your policy does not need to be a long document. A short set of rules that agents can actually remember during a shift is enough. For example: read the ticket first, find the article next, add a personal note, then verify the link. If there is no suitable article, the agent replies manually and flags the topic as needing a new instruction. If an article exists but is incomplete, the agent does not rewrite it on the fly without review, but leaves a suggestion for the editor.

• Send an article link when the instruction is long, includes images, or may change over time.
• Insert article content only for short checks that fit into a few steps.
• Before sending a public reply, remove internal comments, system-only URLs, and unnecessary technical details.
• If the customer will not be able to open a restricted article, use a public version or write a short explanation instead.
• If a ticket reveals a new symptom, record it as a suggestion for a tag or an article section.

That kind of policy helps preserve balance. The integration speeds up the workflow, but the agent still remains responsible for the meaning of the reply. The customer gets not a mechanical link, but real support with a clear next step.

How It Connects with Email Notifications, Macros, and Reply Quality

Many users read SupportCandy replies not only in their account area, but also in email. That means Knowledgebase Integration needs to be configured with email in mind. Even if the reply looks clean in the ticket view, the email may trim long HTML, alter spacing, or make the link less visible. This matters especially when the agent inserts article content rather than a simple link.

Start by testing a short reply with a link. The user should immediately understand why they should open the article and what to do after reading it. A bad version is a bare link with no context. A good version is one or two sentences before the link and a concrete request after it: "Please go through the test email steps. If you see an error while checking SMTP, reply with that error message." That works both in the ticket and in email.

Macros as a Suggestion Layer, Not Autopilot

Knowledge base suggestion macros are useful when an agent is processing a high volume of requests. But they should never be treated as an infallible recommendation engine. The documentation describes matching between the ticket subject and article tags. That means the macro sees only limited context, not the user's full history. The agent should open the suggested article, confirm it is appropriate, and only then insert it into the reply.

For quality control, it helps to periodically review closed tickets that included article links. If agents often choose the wrong material, the problem may be team training, knowledge base tags, or article titles that are too similar. If users still ask the same question after receiving a link, review the article text and add a "how to tell it worked" section.

How to Write the Reply Around the Link

A strong reply built around an article has three parts: acknowledgment of the specific issue, the link or short instruction, and a verifiable next action. You do not need to restate the whole article in email, but you do need to show why this specific article applies to the ticket. That is especially important for new customers, who may otherwise read the link as an attempt to brush them off.

A good structure looks like this: "Based on your description, this looks like a user permissions issue. Open the instruction article and follow the steps in the role check section. Then return to the ticket and let us know whether you can now see the submit button." That kind of reply is short, but it connects the ticket, the knowledge base, and the result check. That is exactly the workflow SupportCandy Knowledgebase Integration is meant to support.

When It Is Better Not to Use an Article

Sometimes it is better to reply without a link. For example, when the user has sent private data, when the issue involves a one-time server failure, when the instruction would expose an internal process, or when the article has not been verified yet. In those cases, the agent can still use the knowledge base as an internal reference, but should not insert the material into the public reply. That is normal. The integration gives access to knowledge, but the decision to publish it still belongs to the person.

Keep a close eye on articles with outdated screenshots. Even if the text is still accurate, the user may get stuck at a step where the interface no longer looks the same. For those materials, add a short warning to the reply or update the images. Documentation should not merely be available inside the ticket. It should actually be usable.

Common Issues and Troubleshooting

Most problems with SupportCandy Knowledgebase Integration are not caused by a single button. They happen at the boundary between three systems: SupportCandy, the selected knowledge base plugin, and WordPress permissions. Troubleshooting works best when you follow the symptoms instead of changing settings blindly. First confirm that the knowledge base works on its own, then verify that the correct plugin is selected in SupportCandy settings, and only then check what the agent sees in a real ticket.

The Knowledgebase Link Does Not Appear Below the Reply Form

Symptom: the agent opens a ticket but does not see the Knowledgebase link below the reply box. Possible reasons include the add-on not being activated, no KB plugin selected in settings, the agent looking at the wrong screen, or the core SupportCandy interface not refreshing after activation.

Check the WordPress plugin list first, then open Support - Settings - Knowledgebase and confirm that the selected plugin is the one that is actually installed. After saving, open a different ticket or refresh the page without browser cache. If the link appears for the administrator but not for the agent, check the agent's role and ticket permissions.

Rollback: disable the integration and make sure the SupportCandy reply form works normally without it. Then enable the add-on again with just one KB plugin selected, rather than testing multiple extensions at the same time.

The Pop-Up Opens, but the Article List Is Empty

Symptom: the link is there and the window opens, but there are no articles or categories inside. The cause is often that the articles are unpublished, placed in a restricted category, created in a different KB plugin, or tied to the wrong integration type.

Open the admin area for the selected knowledge base and check the article statuses. Then open the public article page in the browser. If the article is not accessible outside the admin panel, SupportCandy may not display it the way the agent expects. Also make sure you are not mixing up FAQ integration and Knowledgebase integration: FAQ works with separate FAQ plugins, while the knowledge base integration works with the supported list of KB tools.

Fix: publish a test article in a simple category, add a clear tag, save the permalink, and run the check again on a new ticket. If the test article appears, the problem is in the structure or permissions of the older materials.

Macro Suggestions Are Not Relevant

Symptom: macros suggest articles that are only loosely related to the ticket subject, or do not suggest the needed article at all. The documentation describes matching the ticket subject against article tags, so the first place to check is the tag vocabulary.

Take a real ticket subject and compare it with the words in the article title and tags. If the user writes "I am not getting the email," but the article is called "SMTP configuration" and has only one tag, mail, the match may be weak. Add several tags that reflect the real language used in support requests. Do not inflate the tags into huge keyword lists, but cover the core symptoms.

Rollback: if the new tags make navigation worse, restore the previous set and create a separate article with a more precise title. Sometimes the problem is not the tags, but an article that is trying to cover five different scenarios at once.

The Customer Cannot Open the Article Link

Symptom: the agent inserted the link, but the customer lands on a login page, gets an access error, or sees a blank page. The article may be restricted, stored in a private knowledge base, published only for internal roles, or affected by a permalink issue.

Test the link in a browser while logged out of WordPress. If the article is meant for all customers, it should open like a normal public page. If the article is restricted, the agent should either send it only to authenticated users with the required access, or use a public version of the instruction with internal details removed.

Fix: split your documentation into public and internal content. Do not send customers materials that include internal procedures, private URLs, employee names, or technical details that should not leave the organization.

Inserted Content Is Too Long or Breaks the Email

Symptom: the agent inserts the full article text, and the customer's email becomes heavy, difficult to read, or filled with unnecessary blocks. The reason is that content insertion was used for an article that works better as a standalone page.

Check how SupportCandy renders the reply in the public ticket view and in the email notification. If the formatting is unstable, use a link instead of the full content. For short instructions, keep only the necessary steps and the agent's personal note.

Rollback: remove the long content block before sending the reply, or create a dedicated canned reply with short text and a link to the article. Use full content only for small materials.

When SupportCandy Knowledgebase Integration Is the Right Choice

SupportCandy Knowledgebase Integration is worth using if you already have, or are planning to build, a real knowledge base and your support team regularly handles repeat questions. The add-on is especially useful when an agent needs to quickly find an instruction, insert a link or a short article excerpt, and keep reply quality consistent without constantly copying from another browser tab.

Before rolling it out, check the knowledge base, tags, agent roles, support page, and a test ticket. After enabling it, do not stop at verifying the button. Walk through the full flow: ticket subject, pop-up, article selection, link insertion, sending the reply, viewing it from the customer's side, and checking the email. If that chain works, the integration becomes more than an extra feature. It becomes part of a normal support workflow.

If you are ready to test the setup on your site, you can move to the download section and download the latest version of SupportCandy Knowledgebase Integration. Start with a staging copy or a small set of tickets, then gradually expand the knowledge base based on real user requests.

The main success criterion is simple: after replying, the agent should not have to explain again what is already documented, and the user should receive a clear next step. If the integration helps you achieve that, it has earned its place in the SupportCandy workflow.