Vicket Documentation
Last updated February 28, 2026
End-to-end guide to deploy, configure, and operate Vicket for support operations.
Welcome
This documentation explains how Vicket works in production, from onboarding to daily operations.
It is based on the implemented product behavior in the current codebase and is written for customer-facing use.
What you will learn
- How Vicket structures organizations, websites, teams, templates, and tickets
- How public support pages and internal dashboard operations connect
- How workflows, billing, knowledge base, and integrations fit into your process
Reading paths
New to Vicket
Support operations setup
Governance and scale
What is Vicket
Vicket is a white-label customer support platform built for SaaS companies and agencies. It provides a complete ticketing system that you embed directly into your product under your own brand. Your customers interact with support pages that look and feel like your application — not a third-party tool.
Key capabilities
- Ticketing — structured ticket intake with typed questions, file attachments, and automatic priority scoring. See Templates and Tickets.
- Workflows — rule-based automation that triggers actions on ticket events such as assignment, status change, or escalation. See Workflows.
- Knowledge base — publish FAQ entries and articles that appear on your public support page. See Knowledge Base.
- White-label — full branding control including colors, logos, and custom domains. See White Label.
- Multi-tenant — a single account can manage multiple organizations, each with its own websites, teams, and billing. See Organizations and Access.
- Embeddable SDK — install support pages in your app with a script tag or iframe. See Installation.
Prerequisites
Before starting with Vicket, make sure you have the following:
- An account — sign up at the Vicket dashboard to create your first organization.
- A website to embed into — you will need a web application or marketing site where the support page will be installed.
- A support plan — review available plans in Billing and Plans to understand feature availability (workflows, integrations, storage quotas).
- Team members (optional) — if you plan to distribute ticket workload, gather the email addresses of teammates you want to invite during Onboarding.
Once you have these, follow the New to Vicket reading path above to get your first support page live.