Skip to navigation

ServiceNow Discovery Guide for Message Brokering

View as Markdown

Answer these questions before you configure ServiceNow Live Agent Message Brokering. The answers decide the Context Bender keys and the AWA queue conditions. Message Brokering keeps the handoff in the same AI Assistant chat, with no browser redirect, by relaying messages through the ServiceNow Virtual Agent API.

Overview

  • Same-chat handoff: the user stays in the AI Assistant. Messages are relayed to ServiceNow, and the agent works in Agent Workspace or Service Operations Workspace.
  • Queues live in ServiceNow: Moveworks does not own routing. It sends contextVariables (key-value pairs) when it starts the chat, and the AWA queue conditions decide where the chat lands.
  • Context variables are configurable: the Context Bender in Moveworks Setup builds them from the handoff item’s domain (for example IT), the user’s language code (for example en), and the fields on the live agent request form. Moveworks always adds live_agent_only and short_description. Nothing else is sent unless you configure it.
  • Translation: with Multilingual Support and On Demand Machine Translation enabled, user messages are translated into the Agent Language and agent replies back into the user’s language, whenever the two differ.

Prerequisites

  • Virtual Agent API plugin enabled in ServiceNow (typically requires ITSM Pro).
  • Agent Chat plugin enabled in ServiceNow.

1. ServiceNow Platform Readiness

  1. Is the Virtual Agent API plugin enabled? (It typically requires ITSM Pro.)
  2. Which workspace will agents use: Agent Workspace or Service Operations Workspace?
  3. Is AWA already configured for chat between users and agents, or is this a new setup?
  4. Which ServiceNow instances are in scope, and on which release (for example Yokohama, Zurich, or Australia)?
  5. Does the instance run ServiceNow Virtual Agent alongside Moveworks? If so, a separate provider application and App Inbound ID are needed.

2. Queue Strategy

Queues and queue routing live in ServiceNow. Moveworks passes context that the queues route on.

  1. How many queues handle live chat, and what do they split on (domain, region, language, business unit, VIP)?
  2. For each queue, what AWA conditions or skills does it use?
  3. Is a default fallback queue needed when no condition matches? Without one, ServiceNow ends the chat.
  4. Are any queues 24/7, or do some need business-hours handling in ServiceNow?
  5. Should HR, IT, and Finance requests go to dedicated queues?
  6. Are there VIP or executive routing requirements?

3. Context Variables Passed at Handoff

Moveworks sends the keys you define in the Context Bender. Key names must match exactly what each AWA queue condition reads.

  1. What context variable names does each AWA queue condition read? (Field names, not just concepts.)
  2. Which field does skills-based routing use, if any? (For example liveagent_optional_skills.)
  3. Should the routing value come from the request’s domain (HR, IT, Finance)?
  4. Are custom context variables needed beyond domain and language?
  5. Can each value come from the handoff item’s domain, the user’s language, a field on the live agent request form, or a fixed value? User profile attributes, such as department or location, are not available.
  6. Do any values need transforming, for example HR to hr_chat? The Context Bender can map values with CONDITIONAL() or LOOKUP().

4. Language and Translation

Moveworks sends the user’s language code as language. With Multilingual Support and On Demand Machine Translation enabled, user messages are translated into the Agent Language and agent replies back into the user’s language.

  1. Is Multilingual Support enabled?
  2. Which languages are in scope for users?
  3. Are there language-specific queues, or one queue with multilingual agents?
  4. Is each user’s preferred language set in Moveworks?
  5. Which language do agents use? This becomes the Agent Language.
  6. Should chats route to a native-language queue when one exists, and use translation only when it doesn’t?
  7. Are there regions where translation should not be enabled, for example for data residency?

5. Handoff Timing and Flow

  1. Which Get Help categories should offer live chat?
  2. What should the user provide on the request form before joining the queue?
  3. Should users see the estimated wait time from ServiceNow?
  4. Should a ticket be filed for every live chat request? It is filed even when no agent is available.
  5. How much of the AI Assistant conversation should the agent see: the last messages (6 by default, up to 20), a generated summary, or none?
  6. After the agent ends the chat, should anything happen, such as a satisfaction survey?

Quick Reference: Example Context Bender

{
"language": "language OR null",
"liveagent_optional_skills": "domain OR null"
}

Each output key becomes a context variable on the interaction and must match the variable the AWA queue condition reads. See Configuring Queue Routing.

Related Pages