Question 200
At Juniper Civic, a public agency service counter is improving permit status following a quarterly access review (SF-A19-03). The administrator observes that a spoken customer request needs a human handoff but the voice implementation has only text fallback. Any fix must ensure that citizen information stays limited to the relevant case. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: Voice channel delivery has modality and escalation requirements beyond text-only configuration. In this permit status scenario, this separates supported agent behavior from assumptions about the AI model. Because a spoken customer request needs a human handoff but the voice implementation has only text fallback, the intended response is to configure the supported voice route and escalation path with context retention. An observable check is that a voice test transfers to the intended human team with the relevant case context.
Incorrect Answers
The idea “An agent definition does not automatically establish its channel delivery; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: A service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that financial identifiers are masked outside authorized roles. That situation depends on: An agent definition does not automatically establish its channel delivery. The present question instead concerns a spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Voice channel delivery has modality and escalation requirements beyond text-only configuration.
The idea “Channel connections must preserve the intended audience and authorization context; interpret this independent of the surface wording of the conversation” explains another source-defined situation: Internal employees expect the company agent in Slack but the connector exposes an unrelated public service agent. The correction must ensure that quoted amounts use authorized account and price-book records. That situation depends on: Channel connections must preserve the intended audience and authorization context. The present question instead concerns a spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Voice channel delivery has modality and escalation requirements beyond text-only configuration.
The idea “Standard agent topics can be reused when they already fit the task; interpret this as distinct from unrelated UI configuration” explains another source-defined situation: A customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that part inventory decisions use approved current records. That situation depends on: Standard agent topics can be reused when they already fit the task. The present question instead concerns a spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that citizen information stays limited to the relevant case. Its directly relevant mechanism is: Voice channel delivery has modality and escalation requirements beyond text-only configuration.