Websites

A website is the operational scope for support configuration in Vicket.

Each website has its own:

• Templates
• Statuses
• Priorities
• FAQ
• Articles
• API key for public support intake

Website settings

At minimum, a website stores:

• Name
• URL
• Email delivery mode

Email delivery mode can be:

• VICKET_HOSTED
• SELF_HOSTED (requires a delivery URL)

API key management

Each website has a dedicated API key used by public support pages.

You can:

• Retrieve the active key
• Refresh (rotate) the key

If you rotate a key, update all client apps using that website.

For production deployments, prefer a backend proxy/BFF between browser clients and Vicket public endpoints to reduce abuse risk and keep sensitive controls server-side.

Website tabs in dashboard

The website settings area includes:

• General
• Priorities
• Templates
• FAQ
• Statuses
• Articles

Treat each website as a separate support configuration domain.

Creating a website

From the dashboard, navigate to Settings > Websites and click Create website. Provide a name and URL, then select your preferred email delivery mode. The website is immediately available and comes with default statuses and priorities inherited from your organization settings.

You can create additional websites at any time within the limits of your current plan.

When to use multiple websites

Multiple websites are useful when you operate distinct brands, products, or business units that each require their own support identity. For example, a digital agency managing client support portals would create one website per client. Each website maintains independent templates, FAQ content, articles, and priority definitions, so configuration changes on one website never affect another.

Websites can also be assigned to specific teams to control which agents handle tickets from each support channel. This pairing of website and team provides clean routing boundaries in multi-brand setups.

Embedding the support page

Once a website is configured, embed its public support page into your product using the Vicket SDK. See Installation for integration steps covering script tags, React components, and iframe options. The embedded page automatically reflects the templates, FAQ, and branding configured for that website.

White-label configuration

Each website supports independent white-label settings. You can customize the logo, colors, domain, and messaging per website. This means a single Vicket organization can serve multiple branded support experiences without any shared visual identity between them.

API key security best practices

API keys grant public access to your support intake endpoints. Follow these guidelines to minimize risk:

• Never expose API keys in client-side source code without a backend proxy
• Rotate keys immediately if a key is accidentally committed to version control
• Use a BFF (backend-for-frontend) layer to proxy requests and apply server-side rate limiting
• Monitor key usage in the dashboard for unexpected traffic spikes
• Restrict CORS origins to your known domains when possible