Many brands. One help desk.
Run multiple branded help desks from a single Ticaga install — each with its own domain, logo, colour, and email identity — while your staff work them all from one shared back office. It is multi-tenant branding, not separate installs: one database, one login, many faces.
One install resolves every brand.
Point any hostname at the install and it is resolved to a brand by the request Host header, then served with that brand's theme and email identity. A ticket opened on one brand's domain belongs to that brand.
Domain, theme,
and email — per brand.
Each brand owns a custom domain, light/dark logos and favicon, an accent colour that drives the portal theme, and its own sender name, from-address, and reply-to. Optional welcome header and slogan finish the customer-facing portal.
- +Custom hostname per brand, resolved automatically
- +Per-brand logos, favicon, and accent colour
- +Brand-specific sender, from-address, and reply-to
- +One default brand as the fallback host and home for shared records
Isolated where it matters,
shared where it helps.
Core records carry a brand, staff see only the brands they're assigned to, and HTTPS provisions itself — all inside the extension. Disable it and the core help desk behaves exactly as before.
Certificates, automatically.
Saving a brand domain queues a Let's Encrypt certificate. A scheduled task issues and expands it, reloads the web server, and flags domains whose DNS isn't pointing here yet — no shelling out to certbot by hand.
Staff see only their brands.
Agents assigned to a brand see that brand plus shared records; admins and multi-brand agents see across everything from one screen. Enforced globally on tickets and departments, plus pickers, search, and notifications.
Departments where you want them.
Departments can be shared across every brand or pinned to one. Tickets always belong to a single brand; existing data is backfilled to the default brand on install so nothing starts life unbranded.
Know whose ticket it is.
For viewers who see more than one brand, a brand-coloured dot and name sit beside each ticket, a Brand row appears in ticket properties, and an "All Brands" filter narrows the list — hidden for single-brand staff where it's redundant.
Delegate brand management.
Name one or more leads per brand. They manage that brand's identity and team without being a global admin — scoped strictly to the brands they lead, and never able to touch slug, domain, or default flags.
Surface what needs a manager.
Leads are notified when a brand's tickets go unassigned past a threshold or breach SLA — once per reason, by database, broadcast, and email — so the right manager sees the right brand's problems.
Lives entirely
inside the extension.
Every core touch-point is guarded, so the help desk renders identically whether Multi-Brand is uninstalled, disabled, or fully enabled. Per-request work — host resolution and visibility lookups — is cached, because it runs on every page load and Livewire round-trip.
- +Disable-safe — core behaves exactly as before
- +Brand resolution cached per host, bumped on save
- +Cross-extension safe — SLA escalation only when SLA Tracking is enabled
- +Managed from Admin → Brands alongside every other extension
One extension. One monthly price.
Add Multi-Brand to an active Ticaga installation and serve as many branded help desks as you need from a single back office.
Start with core. Add brands when one help desk needs many faces.
Multi-Brand is an optional paid extension for Ticaga, requiring a valid licence to enable — the same model as Live Chat and Public RoadMap. Your core help desk licence remains separate, so you only add multi-tenant branding when your team is serving more than one identity.
Price shown in GBP, excluding VAT where applicable. Prices are subject to change before purchase.
One install. Every brand.
Give each brand its own domain, look, and inbox while your team works them all from one shared back office — with isolation, HTTPS, and delegated management handled for you.