Skip to content
Getting started5 min read

How to use this Help Center

Search by task, browse by category, or ask the Help Assistant. Every article follows the same seven-section shape.

Browse topics

What it is

The Help Center is the product manual for Agentency. Every article is a how-to for one task, written with the exact dashboard path you need to click, what you should see when it works, and what to do when it does not.

It is deliberately not the blog. The blog is marketing writing about ideas; the Help Center is reference material about buttons. If the two ever seem to disagree, the Help Center is the one to trust.

There are three ways in, and they suit different moods:

You are…Use
Looking for one specific thingSearch at the top of /help
New and want the lay of the landCategory browsing on the hub
Mid-task and just want an answerThe Help Assistant chat bubble on the marketing site

When you would use it

Read this once, early. Knowing that Test Chatbot is documented under Getting started and that widget failures are documented under Website widget saves you the search entirely.

Where to find it

Open /help.

Steps

  1. Start at /help. The hub shows a category grid, featured articles, and a search field.
  2. Search by task, not by feature name. "upload a PDF" and "embed widget" work better than "knowledge ingestion". Search needs at least two characters.
  3. If search comes up short, open the category that owns the area and scan the titles. Categories are organised by the part of the product you are in, which matches how you got lost.
  4. Read the article top to bottom the first time. The Steps section is the answer; Common problems is the part you will come back for.
  5. Check the FAQ at the bottom of the article, or the combined list at /help/faq.
  6. Follow the related links at the end. Most tasks in Agentency touch two or three areas, and the related links are the shortest path between them.
  7. On marketing pages, open the Help Assistant bubble and ask in your own words.

How the categories are organised

Roughly in the order you meet them:

  • Getting started — account, first chatbot, dashboard, going live. Start here.
  • Account and profile, Security and sign-in, Team workspaces — you and your people.
  • Chatbots — creating, styling, activating, retiring one chatbot.
  • Knowledge base, Website crawling — what the chatbot knows.
  • Instructions and actions — how it behaves and what it may do.
  • Conversations, Customers and leads, Analytics — what came back.
  • Channels, Website widget, Hosted chatbot page, Plugins and integrations — where visitors reach it.
  • Billing, Developer, Troubleshooting — money, code, and everything on fire.

How to read an article

Every article uses the same skeleton, so you can skip to the part you need:

  • What it is — the concept, in plain words.
  • When you would use it — whether you are in the right place.
  • Where to find it — the exact dashboard path.
  • Steps — the numbered procedure.
  • What you will see — so you can confirm it worked.
  • Limits and plan notes — caps, permissions, and what your plan includes.
  • Common problems — the failure modes, with fixes.

Paths are written the way the dashboard reads, for example Dashboard → Chatbots → your chatbot → Integrations → Web widget.

The Help Assistant

The chat bubble on the marketing site is itself an Agentency chatbot, trained on these same articles. It is a genuinely useful demo of what you are about to build: ask it a question in your own words and watch it answer from a documentation set with the sources attached.

Two things to know. It is Agentency's chatbot, not yours — conversations there land in Agentency's dashboard, not in your account. And because it is trained on these pages, it can be briefly out of date after an article changes. If it contradicts an article, the article wins.

What you will see

The hub has a category grid, featured articles, and search. Article pages have breadcrumbs, a sidebar, an FAQ block, and related links. Articles are ordinary web pages — your browser's print dialog and Ctrl/Cmd+F both work normally.

Limits and plan notes

The Help Center is English-only, like the rest of the marketing site. The signed-in dashboard itself is available in Arabic, English, and Spanish — that is a separate setting under Settings → Appearance. See Appearance, language and timezone.

Nothing in the Help Center is plan-gated. Articles describe features you may not have on your plan; those say so in Limits and plan notes.

Common problems

Search returns nothing.

Use a shorter phrase — two words beats a sentence, and you need at least two characters. Then try the vocabulary the dashboard uses: the product says "chatbot", "knowledge", "Call action", "channel". If you still find nothing, browse the category.

I found the article but it does not match my screen.

Check whether it is describing a different plan tier, or a deployment-dependent feature such as a messaging channel. Those cases are called out in Limits and plan notes.

The Help Assistant contradicts an article.

Trust the article, then tell support — the assistant is trained on these pages and may be between updates. See Contact support.

I cannot find the topic anywhere.

Try Troubleshooting, which collects the cross-cutting failures that do not belong to one feature.

Common questions

How should I phrase a search?

By task rather than by feature name. "Upload a PDF" and "embed widget" work better than "knowledge ingestion". Two characters is the minimum.

Can I print an article?

Yes. Articles are ordinary web pages, so your browser's print dialog and Ctrl/Cmd+F both work as normal.

Is this the same as the blog?

No. The blog is marketing writing about ideas; the Help Center is reference material about buttons. If they disagree, trust the Help Center.

What is the chat bubble on the marketing site?

Agentency's own Help Assistant, trained on these same articles. It is a live demo of the product — but it is Agentency's chatbot, so those conversations do not appear in your dashboard.

Was this article helpful?

Ready to try it on your own content?

Create a free workspace, add a document, and ask the questions your team is tired of answering.