Customizing AWA Presence Color to Orange for "Busy" State when Work-Item Checkbox is Enabled

kamalimurug
Tera Contributor

Hi all,

I'm working on configuring Advanced Work Assignment (AWA) presence states and workspace agent availability.

To meet our business needs, we’ve set up a custom configuration allowing agents to continue receiving work items even when they are marked as "Busy" (by checking a dedicated checkbox (Available to receive work items) to opt-in for work items while busy).

However, we are running into a styling behavior issue:

  • Current behavior: Whenever that checkbox is enabled so agents can receive work items, the workspace status indicator automatically overrides and changes to green (the standard available color).
  • Desired behavior: Even when the checkbox is enabled and they are able to receive work items, we want the presence status color to stay or display as orange (representing the "Busy" state) instead of turning green.

Has anyone successfully:

  • Overridden or customized the default color mapping for AWA presence states based on checkbox triggers or custom conditions in the workspace?
  • Applied CSS or configuration changes to ensure the "Busy" indicator remains orange even when work-item acceptance is enabled?

Any guidance, configuration pointers, or best practices would be greatly appreciated!

1 REPLY 1

kmohammed
Tera Guru

Hi Kamali,

 

What you are seeing is the workspace working as designed, and unfortunately there is no supported configuration for what you want — explaining why:

 

The status indicator/pill in the workspace Inbox is not coloring the presence state's name, it is coloring work eligibility. The AWA presence state record has no color attribute at all; the indicator is rendered by the delivered workspace (Next Experience) presence component, and its color logic is essentially binary: if the agent's current presence state is flagged as able to receive work items (your "Available to receive work items" checkbox), the component renders the "available" treatment (green); if not, it renders the unavailable/busy treatment. That is why ticking the checkbox on your custom Busy state flips the pill to green — from the component's point of view the agent is available, whatever the state is called.

 

Consequences for your two ideas:

- There is no per-state color mapping to override: no field on the presence state, no system property, and no workspace configuration that assigns orange to a named state while it is work-eligible.

- CSS is not a supportable route here: the Inbox/presence component is a delivered Now Experience component, not a portal widget or a classic form you can attach a stylesheet to. Any DOM-level override you force in would be unsupported and would break with workspace/component updates.

 

What you can do instead:

1. Keep the semantics separate and visible: OOTB-style usage is one state per meaning — "Busy" (not work-eligible, orange) and your custom "Busy - available for work" state (work-eligible). Agents/supervisors then read the state name for context and the color purely for eligibility. In practice, most teams that enable work during Busy accept the green pill once users understand green = "will be offered work" rather than "free".

2. If the business objection is really about the exact shade, the only lever that touches these colors at all is Next Experience theming, which can redefine the color tokens the framework uses — but it applies to the availability treatment as a whole, for all states and all users, not per presence state. Changing "available" away from green instance-wide is almost never worth it.

3. If per-state colors are a hard requirement, this is an enhancement request (Idea portal) against AWA/workspace — it's a known type of ask, but today the component simply doesn't expose it.

 

So: configuration-wise you have already done the right thing to let agents receive work while Busy; the green indicator is the platform telling you that part is working, and it can't currently be decoupled from the Busy name.

 

Hope that saves you further time chasing a setting that isn't there.