Hello,
So let's clarify.
A Topic is a specific Activated set of "activities/actions" within an Agent and is not stand alone
An Agent is an actual Stand Alone Interactive Process that leverages Topics as a way to answer peoples questions or do things.
In the feature you are referring too, it links Agents together, allow Agent A, who cannot answer the question (On purpose because it wasn't designed too, or to perform certain activities), to pass that onto another Agent. That agent can be specifically linked when you Select Add Agent and you pick a New One or Link to Existing
So imagine you had an Central Agent
Agent Master (conversational example)
Accepts all incoming questions
It then is able to pass requests onto other Agents that are designed specifically to handle that particular subject. Now you may say why not just make it a Topic. The answer is, because a Subject can have 50 topics, not 1. So you bundle those are Agent #2, and Primary Agent is linked too it, but doesn't have to actually KNOW how to answer the question, or activity
So in your Example
For example I used to have a topic on Hardware Laptop with uploaded pdf with troubleshooting guide, request for purchase...etc.
it depends really on many factors but let's look at yours
1. You specifically said Laptops, you didn't say ALL hardware, so its focused
2. You minimized the footprint of what it does as it relates to the Subject (Laptops)
3. however, you said ...etc which means you might come up with 50 other Topics related to Laptops
So, Imagine that you wanted to create a single Agent that has the ability to accept the initial question for Laptops in General. Then it knows to pass that onto and re-direct you to the Agent (purchase and procurement) to gather information about the type of laptop you want.
You COULD do all of that in Topics. So it does NOT require that you build another agent, but for the sake of discussion, how and when you decide to separate out its solely based on your discretion.
If you feel that you want a Conversational AI together information and then potentially have separate Autonomous to do the heavy lifting then feel free to separate and LINK them via the Agents feature.
I boils down too, your preference. There are going to be suggestions, such as I gave by Subject or By Activity or by Type of "actions etc" you will do to help you decide.
Would I build one massive Agent that does everything for a single Subject, no because that Subject (Purchase and Procurement) can not only be huge, but much of it being autonomous versus conversational, but I want the flexibility to treat the entire EcoSystem of bots as one giant Subject processing "engine"
Does that help?
And yes in your case, I initially would say 1 agent, but with the ...etc, it depends.
If this helps resolve your issue, I'd appreciate if you Marked as Such and maybe a like.
Thanks!