EXT.07 — MULTI-BRANDMany faces · one back office

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.

// HOST-AGNOSTIC

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.

// A BRAND IS A TENANT IDENTITY

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
●support.acme.io/admin/brands
Brands admin listing Acme Support and Acme Notes with their domains, sender email addresses, HTTPS status and employee counts
// SAME INSTALL, TWO FACES

Each customer sees only their brand.

Two customers sign in to the same Ticaga install from different domains. Each gets their brand's logo, colour and tickets, and nothing from the other brand.

●support.acme.io
Acme Support customer portal on support.acme.io showing the Acme Support logo and the customer's own tickets
Olivia, an Acme Support customer
●help.acmenotes.app
Acme Notes customer portal on help.acmenotes.app with the teal Acme Notes logo and the customer's own tickets
Daniel, an Acme Notes customer
// MULTI-TENANT, NOT MULTI-INSTALL

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.

// HTTPS

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.

let's encryptauto-renew
// ISOLATION

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.

scoped queriessafe by default
// SHARED OR PINNED

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.

ticketsdepartments
// INDICATORS

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.

brand pillsfilters
// LEADS

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.

delegated adminscoped
// ESCALATION

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.

unassignedsla breach
●support.acme.io/tickets
Staff ticket list with an All Brands filter and a brand name and colour dot beside each ticket
Brand pills and the All Brands filter in the ticket list
●support.acme.io/admin/brands/overview
Brand Overview showing open, unassigned and SLA-breached tickets, agents and first response time for each brand
Brand Overview: workload and responsiveness per brand
// BRAND SWITCHER

Focus one brand,
and everything follows.

Staff who work more than one brand get a topbar switcher — a pill with the current brand's colour dot that opens a flyout of the brands they can target, plus "All brands". Pick one and the focus filters everything they see: tickets, clients, knowledge base, announcements, status, chat, and SLA. "All brands" clears it.

  • +One focus drives both the active brand and visibility scope
  • +Shown only to staff who can target 2+ brands, on the admin domain
  • +A real brand domain stays host-authoritative — a customer is always their brand
  • +Handy for matching the /help KB to the brand you're helping, or authoring brand content
$ brand switcher — working on

● Brand A  focused
   Brand B
   Brand C
   All brands (default)

✓ tickets · clients · KB · status · chat · SLA — all scoped to Brand A
// BRAND-AWARE EXTENSIONS

Brand scoping doesn't stop
at the core.

Five customer-facing extensions are brand-aware too, following the same column + scope + active-brand pattern — so each brand gets its own surfaces, and removing an extension leaves no trace. Other extensions stay install-global by design.

// KB
BRAND-AWARE

Knowledge Base

Per-brand articles and categories. The public /help centre shows only the active brand plus shared content.

articlescategories
// ANNOUNCE
BRAND-AWARE

Announcements

Announcements and their categories scope to a brand, so each portal shows its own notices.

noticesper brand
// STATUS
BRAND-AWARE

Service Status

Groups, services, incidents, and subscriptions per brand. Status pages, RSS, and real-time updates stay isolated.

incidentsper brand
// LIVE CHAT
BRAND-AWARE

Live Chat

Each widget carries a brand; sessions, messages, and visitor records inherit it, with per-brand real-time channels.

widgetssessions
// SLA
BRAND-AWARE

SLA Tracking

Policies, calendars, and holidays per brand. A ticket's brand picks its policy, so each brand keeps its own targets.

policiescalendars
// SAFE TO ADD, SAFE TO REMOVE

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
$ ticaga extensions:status brands

brands: enabled
active brands: 4
scheduler: brands:provision-pending · brands:escalate-leads

$ ticaga extensions:disable brands
✓ core renders exactly as before
// PRICING

One extension. Pay monthly, yearly, or once.

Add Multi-Brand to an active Ticaga installation and serve as many branded help desks as you need from a single back office.

OPTIONAL EXTENSION
MULTI-BRAND EXTENSION
MONTHLY£8/ mocancel anytime
YEARLY£79/ yrsave 18%
ONE-TIME£149onceyours to keep
14-day trial · updates included
See licensing
Unlimited brands, domains, and portals
Automatic per-brand HTTPS
Staff and customer visibility isolation
Brand leads with delegated management
// LICENSED SEPARATELY

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 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.

Prices shown in GBP, excluding VAT where applicable. Prices are subject to change before purchase.

// SHIP IT

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.