Overview
Last updated February 28, 2026
Product model, boundaries, and core flows in Vicket.
Product Model
Vicket is a support operations platform with two connected surfaces:
- A public support experience for your customers
- An internal dashboard for your support team
Core hierarchy
- Organization
- Website
- Team
- Template
- Ticket
What is created by default
When a new organization is created, Vicket initializes:
- A first website
- Default ticket statuses
- Default ticket priorities
- A free subscription
This lets you start triage immediately and then refine your setup.
Public to internal flow
- Customer opens your support page
- Customer selects a template and submits a ticket
- Ticket is created with initial status and computed priority
- Team members and admins process the ticket in the dashboard
- Optional workflows apply automated actions
Scope boundaries
- Data is isolated by organization
- Operational settings are scoped by website
- Access is controlled by role and plan
Use websites to separate brands/products, and teams to separate ownership.