A specialist copies a topic built for the group's Service agent into a new Employee agent, expecting it to work identically. Some of the standard actions referenced by the topic are missing from the new agent. What best explains this?
Select an answer to reveal the explanation.
Short Explanation
Different agent types come with different toolkits. When you copy a topic built for a Service agent into an Employee agent, you may find that an action simply isn’t available in the new agent’s set.
Full Explanation
The standard topics and actions available for configuration depend on the agent type. A topic built for a Service agent can reference an action that is not offered in an Employee agent, so copying the topic does not guarantee that its actions will be available there. This is expected behavior, not evidence that the topic file is corrupted. The claim that standard actions are shared across agent types and become available automatically after copying is therefore incorrect: the available catalogue is type-specific. The claim that standard actions expire after a fixed period is also incorrect; expiration does not explain this mismatch. Exam caveat: distinguish an action missing from an agent’s type-specific catalogue from an action that has expired or a file that is damaged. To check the practical cause, confirm the destination agent’s type and review its available standard actions; then look for an appropriate Employee-agent action or determine whether a custom action is needed.