Which four functional limitations are Whisper Announcements subject to? (Choose four.)

Question

Options

• AAnnouncements do not play for outbound calls made by an agent.
• BFor a Whisper Announcement to work with agent-to-agent calls, use the SendToVRU or
• CAnnouncements do not play when the router selects the agent through a label node.
• DCVP Transfers do not support Whisper Announcements.
• EWhisper Announcements do not support Silent Monitoring.
• FOnly one announcement can play for each call.
• GWhile an announcement plays, you cannot put the call on hold, transfer, or conference; release
• HWhisper Announcements are not supported in a Mobile Agent deployment.

• A
  88% (14)
• E
  6% (1)
• H
  6% (1)

Explanation

Whisper Announcements play a pre-recorded message to an agent just before a call connects, giving them context about the caller. Four core functional limitations govern their behavior: they skip outbound agent-initiated calls (A) because the feature is designed only for inbound routing flows; they are bypassed when a label node handles agent selection (C) since label routing returns an external DNIS rather than completing the standard agent-assignment path where the announcement would trigger; only a single announcement can play per call (F), so you cannot chain multiple messages; and during playback, the agent's call controls - hold, transfer, conference, and release - are locked (G) until the announcement finishes.

The distractors are wrong for these reasons: B describes a workaround (using SendToVRU for agent-to-agent calls), not a limitation; D is incorrect because CVP transfers do support Whisper Announcements; E is incorrect because Silent Monitoring is compatible with Whisper Announcements; and H is incorrect because Mobile Agent deployments do support Whisper Announcements.

Memory tip: Think of the acronym "OLAG" - Outbound calls skip it, Label nodes bypass it, Announcements are limited to one, and Going hands-on (hold/transfer/conference) is blocked during playback. These four represent what the feature cannot do during normal operation, not configuration workarounds or unrelated features.

No community discussion yet for this question.