Skip to main content
SupaCortex
Sign in Book a Demo
Industry

Answers that keep pace with weekly releases

Your docs change every sprint. Your customers ask the same how-to questions anyway. SupaCortex re-reads the help centre on a schedule and answers from the current version, with a link to the article it used.

Book a demo See pricing
  • Help centre kept in step
  • In-app and account-aware
  • Cited drafts for agents

How do SaaS companies use SupaCortex?

SaaS teams feed their help centre, release notes and API docs into a project, put the chat widget on the help centre and inside the product, and turn on reply drafts in the help desk. Public visitors get how-to answers with citations; signed-in users can also ask about their own account through lookups on your API; agents start each ticket from a cited draft. When a release changes the docs, the next feed run changes the answers.

  • Website feed for the help centre, re-read on a schedule; only changed pages refetched.
  • Ingest API to push docs from your own pipeline.
  • Widget by script tag; a mobile URL for app WebViews.
  • Identified mode: a signed token tells the assistant who is asking.
  • Reply drafts in UnifyDesk or any desk on the Draft API.
Typical questions

Questions it answers for software companies

"How do I set up SSO for my team?"

Answered from the admin guide, with the article linked so the customer can follow the screenshots.

"What's the rate limit on the orders endpoint?"

From the API reference - a developer gets the number and the section it came from.

"Where did the export button go?"

From this week's release notes, because the feed re-read them after you published.

"Which plan am I on, and when does it renew?"

In identified mode, a lookup on your billing API for the signed-in user only.

"Add two seats to our account."

An action on your API - the assistant asks for confirmation before anything changes.

"The webhook keeps failing - help?"

Escalated to your desk, where the agent starts from a draft citing the troubleshooting guide.

Set-up

How SaaS teams set it up

  1. 01

    One project per product

    Or one for public docs and one for internal runbooks - so support-only notes never reach the public widget.

  2. 02

    Feed the help centre

    A website feed with a preset for TheDocs help centres, or any public docs site, plus uploads for PDFs.

  3. 03

    Widget in two places

    Public mode on the help centre with allowed origins; identified mode inside the app for signed-in users.

  4. 04

    Drafts in the desk

    Agents get a cited draft on every ticket; the desk reports whether it was sent as-is or edited.

Honest limits

What to know before you start

SupaCortex answers from what you have written. That is the point, and also the limit.

  • Undocumented behaviour stays unanswered - the assistant says so rather than guessing.
  • Answers arrive whole after a few seconds of searching and checking; they are not streamed word by word.
  • No Slack or Microsoft Teams channel yet - both are on the roadmap.
  • Account lookups need you to describe your API endpoints; there is no ready-made connector for your product.

Read next

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.

In-Product Assistant for SaaS

An assistant inside your web or mobile app that knows who is asking and can act on their account.

AI Support Assistant for Your Website

Answer customers' how-to questions on your site, any hour, from the docs you already have.

Website & Help-Centre Crawling

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

Actions & API Connectors

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

SupaCortex vs Intercom Fin

An AI agent tied to one help desk, against knowledge you can use in any desk and channel.
Frequently asked

Questions people ask before they start

A website feed re-reads your help centre on a schedule - daily on Starter, every 6 hours on Growth and hourly on Business - and only changed pages are fetched again. You can also press "Run now" after a release, or push changed articles through the ingest API from your build pipeline.

Yes, in identified mode. Your backend signs a short-lived token for the signed-in user, and you describe the lookups it may call on your API. Who is asking always comes from the verified token, never from what the user typed, so nobody can ask about another tenant's data.

The assistant says it does not have enough evidence rather than inventing a feature. Those unanswered questions are a useful list of the docs you have not written yet.

No. It sits in front of it and beside it. Questions it cannot answer still reach your team, and in UnifyDesk or any desk on the Draft API your agents get a cited draft to start from.

Point it at your help centre and ask it last week's tickets.

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