← Genesys Cloud Intelligence
Genesys CloudNew Feature

ServiceNow email metadata can drive routing and auto-acknowledgment

The first inbound email of an interaction can have its subject, body and addresses captured for use in Architect routing, with optional automatic acknowledgment in ServiceNow CSM Workspace.

What changed

Administrators can capture and keep metadata from the first inbound email of a customer interaction, including subject, body, From, To and CC/BCC. Architect flows can use it for priority-based and skill-based routing. For inbound emails associated with ServiceNow CSM Workspace, Genesys can also automatically send an acknowledgment to the sender.

Vendor documentation (opens in a new tab)

Why it matters

Email routing can use what the message actually says and who sent it rather than one queue per mailbox. Persisting email body content also widens what routing logic can see, so data handling should be reviewed alongside the flow design.

CxCave practical context

Who should care

  • Integration developers
  • Routing administrators
  • CX architects

Action

REVIEW

Identify ServiceNow email queues that would benefit from keyword or sender-based routing, design the Architect logic, and confirm acknowledgment wording before enabling auto-answer.

CxCave recommendation, not a vendor mandate unless explicitly stated.