Compare / Document360
Landing Platform vs Document360: help centre plus support
Document360 is a dedicated knowledge base. Landing gives you the help centre and the helpdesk, live chat, CRM, projects and client portal it should sit beside, so every article, ticket and customer lives on one record.
Landing suits you if
- You want articles, tickets and live chat in one place, not three
- You run public, client-only and internal help centres on your own domains
- You would rather not price a knowledge base by editors, workspaces and languages
Where a standalone knowledge base stops.
The articles are good. Everything around them lives somewhere else.
Articles in one tool, tickets in another
The help centre and the helpdesk are two systems, so the article and the ticket it should have prevented never meet on one record.
Priced by the configuration
Editors, workspaces, languages, SSO and the privacy model all move the quote, and the AI Premium Suite is an add-on on top.
A second login for clients
Your clients read articles in one place, raise tickets in another and see their projects in a third.
Landing Platform vs Document360, line by line.
On the help centre itself you get what a support team needs. Then Landing keeps going, into the inbox, the customer record and the work.
| Feature | Landing Platform |  Document360 |
|---|---|---|
| Help centre | Public, client-only and internal help centres, each on your own domain, mounted on your site or shared by a private linkCore | Its core product, with public, private and mixed access |
| Search | Search across every published article, with matching articles suggested before anyone writes inCore | Included |
| Keeping articles current | Review dates per article, "was this helpful" on every page, and matching articles suggested beside the support formCore | Included |
| AI answers from your articles | A chat assistant that answers from your published articles, links the ones it used, and hands over to a personGrowth | Eddy AI, with a premium AI suite as an add-on |
| Helpdesk and live chat | One inbox for email, live chat, Messenger and Instagram, with macros and assignment rulesCore | Not part of the product |
| Customer context | Orders, deals, bookings and past tickets beside every conversationCore | Not part of the product |
| A ticket that needs work | Becomes a card on the delivery board in one click, linked back to the ticket and the clientCore | Not part of the product |
| Client portal | Projects, invoices, tickets and deliverables under your logo; clients are free | Not part of the product |
| CRM and sales pipeline | Contacts, companies, deals and pipelinesCore | Not part of the product |
| Email marketing | Campaigns and flows with segments on the whole customer recordCore | Not part of the product |
| Brands | Several brands in one account, each with its own domains and chat assistantScale | Workspaces, priced into the quote |
Plan tags show where a feature starts on Landing: Core, Growth or Scale. Document360 details reflect its publicly available plans as of 2026; check current details on its own site.
What it costs, side by side.
Document360 builds a quote from your configuration. Landing charges full price only for the people who work in it every day, and your readers and clients are free.
Document360, as it lists it
How Document360 is sold, as its pricing page describes it.
And still to buy separately: a helpdesk, live chat, a CRM and a client portal.
a month on Landing, billed yearly, ex VAT
Includes the help centre, AI answers from your articles, the inbox, live chat, SLAs, CRM, email, projects and a client portal.
Work out your own priceExample team: three people who write articles and run support every day, twelve who answer tickets and review. Credits for AI come from a shared pool each Builder adds to.
Switching is our job, not yours.
We move you over one tool a month, against success criteria we agree with you up front. You don't pay until we prove each one is ready.
We map your stack
Show us how you use Document360 and the tools around it. We agree what moves where, and what "ready" means for each tool, before you commit to anything.
We move Document360 across
We move your articles and categories across as part of the switch, set up each help centre on your domain, and keep your URLs working. We check every published article before you switch off.
You sign it off
Billing starts only when we have shown it works against the criteria you set. Then we move the next tool, one a month.
But our knowledge base works.
It probably does. Here is what teams ask us before they move it.
Can the help centre stay on our own domain?
Yes. Each help centre runs on your own domain, can be mounted on your site, or shared by a private link. Run a public one, a client-only one behind the portal login and an internal one for the team.
Does the AI answer from our articles or make things up?
It answers from your published articles and links the ones it used, in your brand's voice. When a customer asks for a person, it hands over. It is part of Growth and draws on the shared credit pool.
How do we know which articles are out of date?
Every article carries a review date, and "was this helpful" on every page shows you which ones are letting readers down.
Do readers or clients need a paid seat?
No. Readers, customers and clients are guests, and guests are free.
Auditing what you pay for?
Run the free stack audit and see what one platform would replace.
“We were running PR, social scheduling and the rest of our marketing across half a dozen tools that never talked. Now we plan, schedule and measure from a single screen.”
Put the answers next to the tickets.
Thirty minutes on your help centre and your inbox. We'll show you what moves, what it costs and when billing would start.