Skip to main content
SupaCortex
Sign in Book a Demo
Solution

Answer how-to questions before they become tickets

Your help centre already has most of the answers. Customers just do not find them. Put an assistant on your site that reads the help centre for them and shows exactly where each answer came from.

Book a demo See pricing
  • One script tag
  • Every answer cited
  • Says "I don't know"

How does SupaCortex answer customers on your website?

You create a project for your public knowledge, point a crawler at your help centre or docs site, and add the project's chat widget to your site with one script tag. Visitors ask in their own words; SupaCortex searches the project, writes an answer only when it finds evidence, and shows numbered citations to the pages it used. When the documents do not cover a question, it says so instead of guessing.

  • Help centre kept in step on a schedule - only changed pages are fetched again.
  • Public mode: anonymous visitors, allowed origins only, rate-limited.
  • Your title, colour, greeting and up to eight quick actions.
  • Thumbs up and down on every answer, transcripts for admins.
  • Runs on open models we operate - your docs are not sent to a third-party AI API.
Getting started

What you set up

  1. 01

    1. A public project

    Create a project such as "Help centre". Only what goes into it can be used to answer visitors - keep internal notes elsewhere.

  2. 02

    2. Feed it the help centre

    Add a web-crawler feed (presets for TheDocs help centres and Google Sites, or any public docs site), and upload PDFs or manuals the site does not have.

  3. 03

    3. Test the questions

    Ask the questions your team answers every week. Where an answer is missing or weak, fix the article, not the assistant.

  4. 04

    4. Paste one tag

    List your site's origins, set the greeting and quick actions, and add the script tag. There is a WebView URL for your mobile app too.

Capabilities

Built to be trusted by customers

Citations on every answer

Numbered sources name the article and section, with a link when the page is public. Citations are checked before the answer is shown.

A confidence gate

No evidence, no answer. The assistant says it could not find it rather than inventing a policy or a feature.

Docs that stay current

Feeds re-read your site on a schedule. A page removed from the help centre leaves the project after a complete crawl - a broken crawl never wipes it.

Locked to your site

The public widget only loads on the origins you list, limits messages per visitor, and never calls your systems.

Feedback you can act on

Visitors rate answers. Admins read the transcripts per project and see which questions found nothing.

Costs you can see

One AI credit per answer, no charge per resolution. Alerts at 80% and 100% of your monthly credits.

Read next

Website & In-App Chat Widget

One script tag for your site, a WebView URL for your mobile app - public or signed-in users.

Website & Help-Centre Crawling

Point it at a help centre, Google Site or docs site and it stays in step on a schedule.

Answers With Citations

Hybrid search, a confidence gate and checked citations - it says "I don't know" instead of guessing.

Answer Quality & Usage

Thumbs up and down on every answer, conversation logs, and AI credits you can see being spent.

SaaS: Half the How-To Tickets Answered on the Site

A widget on the help centre, fed by the help centre, with every answer cited.

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

Only from the project behind the widget: the help-centre pages SupaCortex crawls, the files you upload and any other feeds you connect to that project. It does not answer from the open web or from general model knowledge, and every answer lists its sources.

A confidence gate checks the evidence before an answer is written. When nothing relevant is found, the assistant says it could not find this in the documentation rather than guessing. Those questions show up in the conversation logs, which is a useful list of articles to write next.

The public widget answers from the project's shared knowledge only and never calls your systems. But it will answer from anything in that project - so if your help centre has private or internal articles, keep them out of the public project.

No. Seats are your own team's users. Visitors are counted as widget sessions, and each answer uses one AI credit. Every plan includes the widget, from 2,000 sessions a month on Starter.

The public widget is not a live-chat tool and has no hand-over to a person. Use the greeting to say how to reach your team. For signed-in users, a connector action can raise a ticket in your own system, with the user's confirmation first.

See your own help centre answer questions.

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