A specialist must choose between a standard topic and a custom topic for handling routine appointment enquiries in a Service agent. What is the strongest reason to start from the standard topic?
Select an answer to reveal the explanation.
Short Explanation
You save time by starting with a standard topic because its classification, instructions and related actions are already prepared for a common job. Think of it as a stocked exam room: you can build on the basics and adjust them for your practice.
Full Explanation
Standard topics arrive as pre-configured units for common jobs, with classification, instructions and associated standard actions already in place. Starting with a fitting one reduces build and tuning effort and can give you better classification out of the gate than writing a topic from scratch. The claim that standard topics are locked after deployment confuses being pre-built with being unchangeable: you can extend and adjust them for local needs, and behaviour can differ across orgs because their data and assigned actions differ. Standard topics do not bypass the reasoning engine; standard and custom topics are selected through classification and planned in the same loop. Deterministic routing comes from filters, variables and deterministic actions, not from a topic being standard. Nor are custom agent actions exclusive to standard topics: custom actions can be assigned to topics generally. Exam caveat: pre-configured does not mean fixed, and standard does not mean deterministic. Practical check: before creating a custom topic, inspect whether a standard topic covers the job, then review its classification, instructions and actions to confirm they fit your org.