AI Chatbot on Your Help Center: Zendesk Guide, Help Scout, Freshdesk

If your customers search a help center on Zendesk, Help Scout, Freshdesk, HubSpot or Intercom before they write to you, this guide shows how to put an AI support agent on it: where the script goes and which plan allows it, how to get the articles into a knowledge base and keep them in sync, how unanswered questions reach the helpdesk, and how to measure the result.

Two older guides cover the steps on either side: building a self-service help center is about writing the articles, and letting a chatbot create tickets covers ticket fields and helpdesk setup in depth. This page is the install-and-import job in between.

PepoChat is our product; its behaviour below was checked in its code and documentation on 22 October 2026. Every vendor menu path, plan and API route comes from that vendor's own documentation, read the same day.

Why put an AI chatbot on your help center instead of your homepage?

An AI chatbot does the most good on a help center, because the people reading it already have a problem, have already tried to solve it alone, and are one click away from filing a ticket.

The platforms keep that exit close. Zendesk help centers carry a Submit a request link, Freshdesk portals a Submit a ticket button, and HubSpot lets you add a support form so that visitors "can contact your team if they don't find an answer to their question". Zendesk, Help Scout and Freshdesk also publish sitemaps for search engines, so many visitors land on one article straight from Google with one specific question. A homepage chat, by contrast, mostly meets prospects asking about price and fit.

Help-center deflection is a question answered on the help center that would otherwise have become a ticket, whether an article, search or a chatbot answered it. An AI support agent works in the gap between "this article did not quite answer me" and the contact form. A visitor who landed on your returns policy can ask whether the 30 days start at delivery; the agent answers from the returns and shipping articles together, or collects the order number and files a ticket.

One limit holds on every platform: the agent can only answer what an article says. When visitors keep asking about something your help center never covers, the fix is a new article, not a cleverer bot.

Where does the chatbot script go on Zendesk, Help Scout, Freshdesk, HubSpot and Intercom?

As of 22 October 2026, Zendesk Guide, Help Scout Docs, Freshdesk's customer portal and HubSpot's knowledge base each have one place for a site-wide script, each tied to a plan, while Intercom's Help Center accepts no custom code at all.

Menu paths and plans from each vendor's help center and developer documentation, prices from each vendor's pricing page, checked 22 October 2026. Zendesk's pricing page shows no price for Suite Growth, and the Freshdesk vs Zendesk comparison works a full monthly bill on both.

Whichever platform you use, the snippet is the same script tag you would put on any website:

<script
  src="https://widget.pepochat.com/widget.js"
  data-organization-id="YOUR_ORGANIZATION_ID"
></script>

Zendesk Guide: the footer.hbs template

Zendesk's article on customizing your help center theme lists embeddable third-party widgets among the things a template can hold, and the footer template renders at the bottom of every help center page.

1. In Knowledge admin, click Customize design, then Customize on your theme. Zendesk's own workflows suggest editing a copy of the live theme and publishing it when you are done.
2. Click Edit code and open footer.hbs under Templates.
3. Paste the script tag at the end of the file and click Save.
4. Open an article in a private window and click the launcher.

Two cautions from Zendesk's documentation: a theme with edited code becomes a custom theme that no longer receives new features and updates, and trial accounts get code editing but lose it if they then buy Suite Team.

Help Scout Docs: the Custom Code page

Help Scout's Docs customization article puts JavaScript in the Insert <head> Code field at Settings → Docs Sites → your site → Custom Code, with a warning that Help Scout does not generally recommend custom JavaScript and cannot promise it will not break the page.

A script in the head runs before the page body exists. PepoChat's loader waits for the page to be parsed before drawing the launcher, as its code shows, so the standard snippet works there; check that any other widget supports head placement. The Custom Code article names no plan, but the pricing page leaves custom site branding off Free, which also caps a Docs site at 10 articles.

Freshdesk customer portal: the Layout footer

Freshdesk's article on portal layout and pages says the Layout footer can hold external JavaScript snippets for third-party tools, and marks the code editor as Pro and Enterprise only.

1. Go to Admin → Portals and click edit next to the portal.
2. On the Appearance tab, click Clone & Edit theme for the live theme.
3. On the Pages tab, open Layout → Footer, paste the script tag at the end, then save and publish the theme.

Freshdesk's CSP article asks for a nonce attribute on every custom script and style tag in the Marina theme, and any Content Security Policy you add must allow https://widget.pepochat.com for scripts and frames:

<script
  src="https://widget.pepochat.com/widget.js"
  data-organization-id="YOUR_ORGANIZATION_ID"
  nonce="{{portal.nonce}}"
></script>

HubSpot knowledge base: Site Footer HTML for its domain

HubSpot's knowledge base theme editor covers colours, fonts and layouts; for anything deeper, its theme article points to code snippets, and the domain-wide footer is the setting that reaches every article.

1. Click the settings icon, then Content → Pages in the left sidebar.
2. Choose the domain your knowledge base uses. Avoid Default settings for all domains, because HubSpot says that code also appears on quotes.
3. Under Site Footer HTML, click Override default settings, paste the script tag and click Save.

Overriding means code in the default settings stops applying to that domain, so copy across anything already there, such as an analytics tag. Each article also has a Head HTML field, but HubSpot says the footer HTML field is not available for knowledge base articles.

Intercom Articles: no custom code, so use a link or another surface

Intercom's Help Center customization article states that the Help Center "does not support embedding forms, iFrames (inline frames), or custom HTML in articles or pages", so no third-party chat widget can run on it. Three alternatives remain:

• Keep Intercom's Messenger there. Intercom integrates its Help Center with the Messenger and Fin, its AI agent.
• Link to a full-page chat. The header takes up to 3 links, and one can open PepoChat's hosted chat page. If you use an allowed-domains list, switch on Allow the hosted chat page first, as the install docs explain.
• Answer elsewhere from the same articles. Put the widget on your website and app, and import the Intercom help center into its knowledge base by crawl or through the Articles API.

Why doesn't the chat widget show on the help center?

When a chat widget works on your website but not on your help center, the cause is usually a host missing from the allowed-domains list, a theme that is not live, a content security policy, or a second chat button covering the first.

Help centers often live on the vendor's host, such as yourcompany.zendesk.com, yourcompany.helpscoutdocs.com or yourcompany.freshdesk.com, which is not a subdomain of your website. Add the help center's exact host. PepoChat includes subdomains automatically, so an entry of zendesk.com would let every Zendesk help center load your agent and spend your replies.

Messages from PepoChat's loader and widget; the Zendesk setting from its Web Widget installation article, checked 22 October 2026.

How do you get help center articles into the chatbot's knowledge base?

There are three ways to get help center articles into a chatbot's knowledge base: import the public help center by sitemap or crawl, export the articles through the platform's API and upload them as files, or move them into a help center inside the chat widget.

Import the public help center by sitemap or crawl

A sitemap import reads the list of page addresses a site publishes for search engines instead of following links. In PepoChat it takes up to 200 addresses per run, filtered by include and exclude paths, and the whole import counts as one knowledge source.

Sitemap addresses from Zendesk's and Help Scout's documentation and Freshdesk's robots.txt, checked 22 October 2026.

The include path matters most on multilingual help centers. Zendesk's own help center sitemap lists 40,891 addresses in nine languages, and its first 200 addresses hold only 28 English pages, so an import without a filter would fill most of its 200 places with other languages.

We also ran one public article from each vendor's own help center through PepoChat's page converter, the step every crawl uses. All five kept the full article text, from 1,020 to 4,917 words, and dropped feedback buttons and menus; Freshdesk's breadcrumbs and plan badges and Intercom's image descriptions came through as extra lines. Your theme may differ, so check one imported article.

PepoChat's crawler follows links 3 levels deep, respects robots.txt Disallow rules and stays on the host you start from, so a help center on help.example.com needs its own import. A help center with more than 200 articles needs several runs, for example one crawl per category page with the articles include path; runs on the same site share one knowledge source, as the add your website docs explain.

Export through the API and upload files

An API export suits a help center that needs a sign-in, or a team that wants to choose article by article what the agent may quote. Every export route is in the first table, with these details:

• Zendesk: public articles need no credentials if the request names a locale. Zendesk's announcement of 1 June 2026 removes API tokens from the Help Center API as well as ticketing, with no new tokens from 27 October 2026 and none working after 30 April 2027, so a script that signs in needs OAuth.
• Help Scout: each user's Docs API key sits under Your Profile → Security and Access. The list call returns short article references, and the full article comes from each one's text field.
• Freshdesk: walk categories, then folders, then articles, and keep those with status 2, which means published.
• HubSpot: the export file holds "article data such as title, language, URL, and more", and HubSpot's article does not mention the body, so use the beta API or a crawl for the text.
• Intercom: the list returns up to 250 articles a page, each with its state and a Markdown copy of the body.

PepoChat accepts Markdown, HTML, PDF, DOCX, TXT, CSV and JSON files. Each upload is one knowledge source, and the Free plan holds five, so group articles into one file per category. Uploading a file with the same name replaces the old version, but a Free workspace already at five sources must delete the old file first. Leave out internal or sign-in-only articles you would not show a stranger, because anything in the knowledge base can be quoted to any visitor.

Move the articles into a help center inside the widget

PepoChat's Help Center shows articles in the widget's Help tab and mirrors every published article into the knowledge base. Its import takes one page by address, the first 20 pages of a sitemap, or the first 20 knowledge base entries, as drafts. Free holds 50 articles and Starter and Growth 300, and articles do not count as knowledge sources. The articles are read inside the widget rather than on public pages of their own, so keep a copy on your website if they need to rank in Google.

How do you keep the help center and the chatbot's copy in sync?

Keep one copy as the source of truth: when the help center platform stays the source, a weekly re-fetch keeps the chatbot current, and when articles move into the widget's help center, publishing updates the chatbot at once.

PepoChat re-fetches website pages every week and re-indexes only pages whose words changed. Sync website pages does the same on demand after a price or policy change, and Import again on the import's card picks up new articles, because a sync only refreshes pages it already has.

Retired articles need a manual step. An article you unpublish or archive stops loading for the public, and PepoChat's weekly re-fetch keeps the stored copy of any page that fails to load, so the agent could go on quoting a retired policy. Make deleting that page's row on the Knowledge Base page part of retiring an article.

With the API route you own the schedule. Zendesk's incremental endpoint returns articles updated since a time you pass, and Intercom lists the most recently updated articles first, so a weekly job can rebuild only the category files that changed and upload them under the same names.

In PepoChat's own Help Center, publishing updates the Help tab and the agent together, and unpublishing removes the article from both. Deleting is immediate and has no confirmation, so unpublish when in doubt.

How does the chatbot hand questions it cannot answer back to the helpdesk?

The chatbot should create a ticket in the helpdesk behind your help center, with a written summary and the visitor's email, and tell the visitor what happens next, so your agents work it in their usual queue.

As of October 2026, PepoChat's prebuilt actions cover five helpdesks and CRMs:

• Zendesk, Freshdesk and Zoho Desk: create a ticket and check its status by number. The ticket carries an AI-written summary and the email the visitor typed, not the transcript.
• HubSpot: find a contact by email and create a ticket in the default support pipeline.
• Salesforce: find a contact, create a case and check a case's status.
• Help Scout and Intercom: no prebuilt action; a custom action can call any HTTPS endpoint with up to 10 inputs, or a Zapier Catch Hook can pass the details on.

Zoho Desk, Salesforce and HubSpot offer one-click connection, though HubSpot limits it until it approves the app, and Zendesk connects through an OAuth card, since Zendesk is retiring API tokens. Actions added with a pasted key start switched off.

Keep the help center's contact form too, since some customers will always prefer one. If you are weighing the helpdesk's own AI agent instead, the Zendesk AI agent decision guide covers when it is the better path.

How do you measure help-center deflection?

Measure help-center deflection as contacts per 1,000 help-center sessions, counting tickets plus chats handed to a person, over the same four weeks before and after launch, so a fall in tickets cannot hide a rise in chat handoffs.

Zendesk's self-service metrics guide defines the self-service score as total help center user sessions divided by total users in tickets: a ratio of 4:1 means one person filed a ticket for every four who tried self-service, and a rising ratio means self-service is working.

Formulas as defined in this guide; the self-service score is Zendesk's definition.

A worked example with illustrative numbers, not PepoChat results: the four weeks before launch bring 18,000 help-center sessions and 540 tickets, 30 contacts per 1,000 sessions. The four weeks after bring 19,500 sessions, 420 tickets and 60 escalated chats with no ticket: 480 contacts, or 24.6 per 1,000, a fall of 18%. Counting tickets alone would show 21.5 per 1,000 and a 28% fall, which flatters the bot.

Compare like with like: the same weeks of the month, no product launch in either window, the same contact form. PepoChat's Analytics shows sentiment votes and topics, not conversation volume, so chat counts come from the inbox's CSV export, which does not record the page a chat started on; if the widget also runs on your website, count help-center contacts on the helpdesk side. We publish no deflection figures for PepoChat; the ticket deflection benchmarks explain why published rates vary, and the ticket reduction tactics cover what to fix when one topic keeps producing tickets.

What to do next

• Check your plan against the first table, paste the script into the one template or field your platform names, and add the help center's host to your allowed domains in the same sitting.
• Import the help center's sitemap with the articles include path, following the add your website docs, then ask five questions from last week's tickets in the Test the agent drawer.
• Connect your helpdesk so the agent can file tickets, with the field and trigger advice in the ticket creation guide.
• Create a free PepoChat workspace: every feature is on the free plan, including the crawl, the Help Center and the helpdesk actions, with 200 AI replies a month.
• Related guides: AI chat for docs sites.