Veterinary technicians want to ask an internal assistant quick clinical-policy questions without leaving the messaging app they already use all day for team communication. Which channel and agent-type pairing fits?
Select an answer to reveal the explanation.
Short Explanation
Technicians live in Slack all day already, so meet them there, and since it's staff asking staff-type questions, that's an Employee agent's job, not a Service agent wearing the wrong badge.
Full Explanation
Slack is a supported channel connection specifically well suited to internal staff workflows, letting technicians ask quick policy questions inside the messaging app they already use, and pairing it with an Employee agent matches both the channel's typical audience and the internal, staff-facing nature of the requirement. Email paired with a Service agent misses on two counts: email is not what the requirement describes, staff explicitly want to stay inside their existing messaging app rather than switch to inbox-based interaction, and Service agent is oriented toward external customer support rather than internal staff questions. A digital experience channel is built for portal-based, typically browser-based experiences; it does not match "without leaving the messaging app they already use," and pairing it with a Sales agent additionally mismatches the audience, since this is a clinical-policy lookup, not sales-pipeline work. Agent API is for embedding an agent into a custom or external application via direct API calls when no existing native channel fits; it is unnecessary here since Slack is already a supported native channel, and pairing it with a Service agent again misapplies an external-support-oriented type to an internal-staff scenario.