A specialist is defining a new custom topic and must decide what belongs in the topic's scope statement versus the agent's company description. Which pairing correctly separates the two?
Select an answer to reveal the explanation.
Short Explanation
Company description is the agent's ID badge: who it works for, in general. Scope is the job description for this one topic: what this particular conversation is actually here to accomplish. Mixing the two up is a common early mistake.
Full Explanation
The company description sits at the agent level and supplies persona, tone and organisational context that every topic inherits, such as identifying the agent as representing the veterinary group, while a topic's scope statement is topic-specific and states, in positive terms, what that topic is responsible for handling, such as appointment scheduling or refill eligibility. Reversing the levels, putting company description at the topic level and scope at the agent level, gets the hierarchy backwards; company description is deliberately agent-wide precisely so persona stays consistent across every topic a conversation might touch. Calling them the same setting with only one needed misses that they answer different questions: "who are we" versus "what is this topic for," and both are real, distinct configuration fields a specialist fills in. Scope statements do not filter data, and company descriptions do not govern action availability; those functions belong to filters and to the topic's assigned actions respectively, so attributing them to scope and company description conflates several separate mechanisms into two boxes they do not belong in.