Hello @mehak1890 

To get automation topics, have a specific function for your VA topic. If "phishing" is a situation you want to address as a VA topic, then your intents are going to have example utterances around that subject: "I might have a virus", "I've been phished", "I clicked on a link", "I received a scam" etc. In that VA topic, your utterances are specific to the subject "phishing". When the user types in a "phishing" related utterance, the topic will display.  Within that VA topic, you can create a specific type of ticket/task record when this topic is launched.  This "phishing" topic is not going to be used when a user types in "report a problem with my monitor" or "I need a new badge".

It might help to review "Email issues" or "Email Setup" (there's an example of this topic in the ITSM Virtual Agent Conversations and ITSM NLU Model in the content packs), you'll see that when a user types in very specific utterances around 'email" and email -related utterances (outlook, messages, mail, authentication)  this topic will surface. 
Let's say you create a "Phishing" topic and you have an "Email" topic. And then your user types in "Request a new badge" (which might be a record producer in your catalog). Neither the phishing or email topic should display. You don't need to create a new topic. Instead, I would rely on AI Search - Fallback to surface KB and Catalog content that might answer the user's question. That topic presents the user with a "did you find this helpful?" and if the user says no, then "Fallback" the topic can surface options to further assist the user. I modified my fallback topic to create a ticket. I shared this solution on a VA Academy. https://youtu.be/E1gc3JoUr6A
Hope that helps, 

Tricia