Index Document360 categories and articles so your knowledge base answers questions with citations, paired with tickets and internal docs.
Representative data is enough. No production access required for the first demo.Document360 connects through an admin-defined boundary. Each object type below lists what Linkence reads, the scope condition that applies and the limitation you should know about before the first sync. Your Document360 account remains the system of record.
Article content and categories
Approved projectsFind · Prepare · Act
Pair Document360 with Zendesk, Freshdesk, Gitbook and the answer stops being a search result. Evidence arrives from every connected system, and the next step waits for your approval.
A cited answer that opens the exact article
Bring one of these to the demo on representative data. Every answer arrives with citations that open the original Document360 record.
Every answer reflects the verified connector behaviour, never generalised.
Admin-approved projects and categories; Scheduled sync of articles; Citations to the exact article.
Draft articles; Writing back into Document360; Projects outside the approved scope.
Scheduled sync through the Linkence indexing pipeline. Scope: Admin-approved projects and categories.
The Document360 connector is read-focused. Writes happen through connected companions, for example a grounded reply in mail or an approved update in chat, always with approval.
We will show how Linkence finds the relevant context, presents the work and keeps every sensitive change under your team's control.
Representative data is enough for the first demo. No production access required.