Question 910
At Valley Utilities, a customer billing center is improving billing questions following a quarterly access review (SF-A17-02). The administrator observes that a service agent is configured but customers cannot reach it from the approved support site. Any fix must ensure that billing adjustments require verified eligibility. Which underlying Agentforce or Salesforce design principle explains the appropriate approach?
Explanation
Correct Answer
The governing distinction is: An agent definition does not automatically establish its channel delivery. In this billing questions scenario, this separates supported agent behavior from assumptions about the AI model. Because a service agent is configured but customers cannot reach it from the approved support site, the intended response is to connect the appropriate supported digital experience channel and test the service session. An observable check is that an end user opens the authorized support entry point and sees the intended agent behavior.
Incorrect Answers
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 service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that billing adjustments require verified eligibility. Its directly relevant mechanism is: An agent definition does not automatically establish its channel delivery.
The idea “Voice channel delivery has modality and escalation requirements beyond text-only configuration; interpret this while preserving the specified source of truth” explains another source-defined situation: A spoken customer request needs a human handoff but the voice implementation has only text fallback. The correction must ensure that shipment changes remain attributable and reversible. That situation depends on: Voice channel delivery has modality and escalation requirements beyond text-only configuration. The present question instead concerns a service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that billing adjustments require verified eligibility. Its directly relevant mechanism is: An agent definition does not automatically establish its channel delivery.
The idea “Agent API supports conversation patterns that differ from single transaction automation endpoints; interpret this with boundaries enforced by supported platform controls” explains another source-defined situation: An external partner requires conversational follow-ups but the design offers only a one-shot Flow endpoint. The correction must ensure that escalations preserve only the needed guest context. That situation depends on: Agent API supports conversation patterns that differ from single transaction automation endpoints. The present question instead concerns a service agent is configured but customers cannot reach it from the approved support site. The correction must ensure that billing adjustments require verified eligibility. Its directly relevant mechanism is: An agent definition does not automatically establish its channel delivery.