Skip to main content
Solution

The VPN question, answered before it is a ticket

Much of an IT queue is the same handful of questions, and the answers are already in your runbooks. SupaCortex gives employees a place to ask them - and raises the ticket for them when the runbook is not enough.

  • Runbook cited
  • Raise a ticket on confirmation
  • Internal knowledge stays internal

How does SupaCortex provide IT self-service?

You put IT runbooks, how-to guides and software lists in an internal project and add that project's chat widget to your intranet or IT portal, with employees signed in. Employees ask in plain language and get step-by-step answers citing the runbook. Connect your IT desk's API and the same assistant can look up a ticket's status or raise a new one - always after the employee confirms.

  • Runbooks from uploads, a Confluence space, SharePoint or a docs site.
  • Identified widget on the intranet; a WebView URL for a mobile app.
  • Lookups and actions against any HTTPS API, from the Growth plan.
  • Every action waits for the employee's confirmation.
  • Teams and Slack channels are on the roadmap, not available today.
Getting started

What you set up

  1. 01

    1. An IT project

    Runbooks, onboarding guides, approved-software lists. Mark the current ones official so they outrank old tickets.

  2. 02

    2. Connect where they live

    A Confluence space or SharePoint site as a feed, kept in step on a schedule, plus uploads for the odd PDF.

  3. 03

    3. A widget for signed-in staff

    Your intranet signs a short token for the employee; the script tag goes on the IT page.

  4. 04

    4. Connect the IT desk (optional)

    "Ticket status" as a lookup and "Raise a ticket" as an action, described by hand or imported from OpenAPI.

Capabilities

What it handles well - and what it does not

How-to questions

Resetting a password, setting up VPN, requesting software - answered step by step from your own runbook.

Status lookups

"What is happening with my laptop request?" - looked up for the signed-in employee only.

Raising a ticket

Missing details are asked for; the ticket is raised only after a yes, with a key that stops duplicates.

Not covered? It says so

No runbook, no answer - and the question appears in the logs as a gap to document.

No direct system changes

SupaCortex only calls endpoints you describe. It has no access to your directory or devices of its own.

Every call recorded

Each lookup and action is audited with endpoint, status and timing.

Frequently asked

Questions people ask before they start

Only if your own system has an API that does it and you connect that endpoint as an action - and even then the employee confirms before it runs. Out of the box, SupaCortex answers how to do it from your runbooks; it does not touch your directory.

Not yet - Teams and Slack are on the roadmap. Today employees ask in a widget on your intranet or IT portal, and IT staff can also use SupaCortex's own team chat.

Yes, if your IT desk has an HTTPS API. Add a "create ticket" action to a custom connector; the assistant fills in what it can, asks for anything missing, and raises the ticket only after the employee confirms.

No. Admin procedures, server names and internal links belong in an internal project. A public widget answers from anything in its project, so keep the two apart.

On the Business plan, resolved tickets from osTicket, Zendesk or UnifyDesk can be mined into Q&A. Names, emails and IDs are redacted, and nothing is searchable until someone in IT approves it.

Write the answer once. Stop typing it every week.

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.

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

Still curious? Ask your favorite AI about SupaCortex.