Skip to main content
SupaCortex
Sign in Book a Demo
Industry

The right page of the right manual, for whoever is asking

Dealers ask about warranty terms, engineers ask about torque settings, customers ask how to descale the thing. The answers are all in documents you already have. SupaCortex finds the page and cites it.

Book a demo See pricing
  • Manuals and spec sheets
  • Dealer and customer projects
  • Cited to the section

How do manufacturers and distributors use SupaCortex?

Manufacturers load product manuals, spec sheets, installation guides, service bulletins and warranty terms into projects by audience - customers, dealers and distributors, service engineers - and often by product line. Each audience asks through a widget on the website or partner portal, or in team chat, and gets an answer cited to the manual's section. Where an ERP or warranty system has an API, lookups such as warranty status can be added.

  • Uploads: PDF, DOCX, XLSX, HTML, Markdown, TXT; a .zip becomes one document per file.
  • Up to 50 MB per file and 500 files per upload.
  • Projects per audience or product line.
  • Citations name the document and section.
  • Lookups on your own systems through described HTTPS endpoints.
Typical questions

Questions it answers in manufacturing

"What's the torque setting for the M12 bolts on the X200?"

From the service manual, cited to the section and page heading.

"What's the maximum operating temperature?"

From the spec sheet for that model - not a similar one.

"Error E07 on the control panel - what now?"

From the troubleshooting table and the latest service bulletin.

"Is a cracked housing covered after 14 months?"

From the warranty terms in the dealer project.

"Is serial 4471-B still under warranty?"

A lookup on your warranty system, if you describe its API.

"How do I descale it?"

Asked by an end customer on your website, answered from the user manual.

Set-up

How manufacturers set it up

  1. 01

    Projects by audience

    Customers, dealers and service engineers apart; split further by product line if the catalogue is large.

  2. 02

    Upload the library

    Zip the manuals folder and upload it; tag each document with its product line.

  3. 03

    Keep it in step

    A SharePoint or Drive feed (beta) for the engineering folder, re-read on a schedule.

  4. 04

    Widget on the partner portal

    Identified mode, so the assistant knows which dealer is asking.

Honest limits

What to know before you start

Manuals are often older than the company website. That matters here.

  • It does not read diagrams, exploded views or scanned pages without a text layer.
  • No ready-made ERP connectors; lookups need an HTTPS API you can describe.
  • No offline mode for engineers without signal.
  • No WhatsApp channel for dealers yet - it is on the roadmap.

Read next

Document Uploads

Drop in PDFs, Word and Excel files, Markdown and HTML in bulk - or a zip of them. Each is parsed and indexed.

Knowledge Projects

Keep each product, team or audience in its own project - its own sources, widget and API keys.

Google Drive, SharePoint & Confluence

Connect once with OAuth, pick folders, sites or spaces, and only changed files are fetched again.

Actions & API Connectors

Let the assistant look up an order or raise a request in your own systems - with confirmation first.

Internal Knowledge Assistant

One place your whole team asks "how do we...?" - across policies, wikis, drives and past tickets.

Preparing Documents for AI Answers

Ten habits that make the same documents answer twice as well. Most take minutes.
Frequently asked

Questions people ask before they start

If they are PDF, Word, Excel, HTML, Markdown or text files with real text in them, yes. Upload them one by one or as a .zip, up to 50 MB per file. Scanned images of pages without a text layer will not answer well.

Put dealer material in a dealer project and customer material in a customer project. A widget or API key only answers from the projects it is given. Per-dealer content can also carry a CustomerId so only that dealer can retrieve it.

The widget has a mobile URL you can open in a phone browser or embed in a field-service app, and signed-in staff can use team chat from any browser. It needs a connection; there is no offline mode.

If your ERP or warranty system has an HTTPS API, describe the lookup as a custom connector. There is no ready-made SAP or Tally connector.

Bring one product's manual. Ask it what your dealers ask.

Book a 30-minute demo on your own documents. We set up a 14-day trial workspace for you - no credit card, no setup fee.

Book a demo See pricing

Questions first? Email info@greatdevelopers.com or call +91 8585953085.

Still curious? Ask your favorite AI about SupaCortex.

ChatGPT Claude Perplexity Grok