Konrado.AIdocs
Getting Started

Quickstart

Choose the fastest setup path for your support stack

Use this guide to get Konrado.AI processing tickets, generating drafts, and using the right customer context. Start with the path that matches your current support workflow.

Path A
WHMCS only
Fastest setup when WHMCS is your ticketing and billing system.
Path B
SupportPal + WHMCS
Use SupportPal for tickets and WHMCS for billing/service context.
Path C
Server context later
Start with tickets first, then add panels, VM platforms, or email APIs.
After setup
Tune quality
Add knowledge sources, tweaking rules, and reports review.

Choose a Rollout Path

PathUse whenRequired guides
WHMCS onlyYour team handles tickets in WHMCSConnect WHMCS, then Browser Extension
SupportPal + WHMCSYour team handles tickets in SupportPal but billing lives in WHMCSConnect WHMCS, Connect SupportPal, Webhook Macro
Add server context laterYou want AI drafts first, then deeper technical answersTicketing setup first, then Server Integrations

1. Create Your Account

Sign up at app.konrado.ai and create an organization for your company.

Konrado.AI dashboard onboarding screen

2. Connect Ticketing

Choose the ticketing path you use in production:

  • For WHMCS ticketing, install and connect the WHMCS module.
  • For SupportPal ticketing, connect WHMCS first if you want billing context, then connect SupportPal.
  • After SupportPal is connected, create the SupportPal webhook macro so new ticket events reach Konrado.AI.

3. Verify the First Ticket

Create or update a real test ticket. In Konrado.AI, open Tickets and confirm:

  • the ticket appears in the list,
  • the conversation is visible,
  • customer or billing context appears when WHMCS is connected,
  • generated replies are available or the missed-reply reason is clear.

4. Add Server Integrations

Connect server integrations only after ticketing works. This keeps the rollout easier to debug.

Use Server Integrations to add cPanel, DirectAdmin, Plesk, Proxmox, Solus2, Rackspace Cloud Office, Remote Agent, or Generic MCP.

If your systems are behind a firewall, configure IP Restriction before testing the connection.

5. Set Up Your Knowledge Base

Add website sitemaps, documentation URLs, and high-value help pages so replies can reference your own content.

Knowledge Base guide

6. Fine-Tune AI Behavior

Use Tweaking to define tone, escalation rules, policies, and technical response guidelines.

Tweaking guide

7. Install the Browser Extension

Install the browser extension for in-ticket AI assistance. This is the fastest daily workflow for support agents using WHMCS ticket pages.

Browser extension guide

Success Checklist

Your first rollout is complete when:

  • Ticketing connection test passes.
  • A real or test ticket appears in Konrado.AI.
  • At least one generated reply is visible for review.
  • Knowledge Base sources are processing without crawl errors.
  • Support agents can open the browser extension or SupportPal widget.
  • Reports begin showing generated, seen, or used replies.

It can take a few minutes after connecting for the first AI responses to appear. The system needs ticket data, integration context, and indexed knowledge before it can generate reliable replies.

On this page