Admin vs agent vs chat screen colors in VICIdial

VICIdial gives you three separate screen color pulldowns, and it is worth understanding why they exist before you pick palettes. The admin, agent, and chat screens serve different people doing different jobs, so theming them independently lets each surface fit its audience. The same template can power all three, or you can give each its own look. This choice is purely visual and never touches your Campaign logic.

What each pulldown controls

Admin Screen Colors theme the administration interface, where supervisors build campaigns, lists, and reports. Agent Screen Colors theme the workspace your callers stare at all shift, so readability there matters most. Chat Screen Colors theme the chat interface used for text-based interactions. Each pulldown lists only active templates, and whatever Web Logo a template carries follows it onto its assigned screen. Because they are independent, you can keep admins on a neutral palette while giving each Agent a brighter, brand-matched view.

The underlying fields are the same in every template: a Colors ID of 2 to 20 characters with no spaces or special characters, a Colors Name, an Active flag, an Admin User Group, a Menu Background defaulting to 015B91, a Frame Background defaulting to D9E6FE, the row backgrounds, and the Web Logo. What differs is not the template, but where you assign it. The same template can drive all three pulldowns, or you can author one template per surface and assign each separately.

The one agent-specific quirk

Most hex fields behave the same across all three screens, with one exception worth remembering. The Standard Row 5 Background is reused on the agent screen as the color behind the logo after an agent has logged in. So if you assign a template to Agent Screen Colors, check that fifth standard row value, since it shapes the post-login look in a way it does not on the admin or chat screens. If your logo has a transparent background, this is the color that shows through it, so a mismatch can make an otherwise polished logo look boxed-in or washed out.

flowchart LR
  T[Screen Colors template] --> A[Admin Screen Colors]
  T --> B[Agent Screen Colors]
  T --> C[Chat Screen Colors]
  A --> A2[Admin UI palette and logo]
  B --> B2[Agent UI palette logo and row5 behind logo]
  C --> C2[Chat UI palette and logo]

The diagram shows one template feeding three independent assignments, with the agent branch carrying that extra row-5 behavior. For the full setup picture, see our agent screen configuration guide.

When to use which

If you white-label for several clients, theme the agent and chat screens per brand while keeping a single recognizable admin palette so your operators never get confused about where they are. Keep the agent contrast high, because hard-to-read rows slow Wrap-up and tire people out. Admins, by contrast, can handle a denser palette because they are not reading the same screen for eight hours straight. The chat screen usually wants to echo whatever your customers already associate with your brand, since it can sit inside a customer-facing window.

A simple rule of thumb keeps this manageable: pick one shared template for everything when you run a single brand, and only split into separate admin, agent, and chat templates when a real reason appears, such as white-labeling or accessibility tuning. If you are also building out the agent workspace itself, our guide on adding a VICIdial script is a natural next step.

Want all three screens branded and hosted without the manual fiddling? Take a look at VICIfast pricing.