This guide tells how to create and manage topics and scenarios in Genezio. Genezio uses the scenarios when it runs conversations with answer engines, and good scenarios make your AI visibility data more accurate. A good scenario simulates the situation of a real user. Thus, the answer engine gives the same answer that a real buyer gets.

​
Open the topics and scenarios in the settings

1

Open the brand

Sign in to Genezio and open your Brand.
2

Open the settings

Go to Settings.
3

Open the topics and scenarios

Go to the Topics & Scenarios section.
This section shows the current list of topics and the scenarios of each topic. In this section, you can:
  • Create topics
  • Edit or delete topics
  • Create scenarios
  • Edit or delete scenarios

​
Create or edit topics

A topic is a subject area where your brand must appear in the answers of answer engines. Each topic can have one or more scenarios. For more information, refer to Topics. When you create a topic, you must select a type of Genezio agent:
  • Prompter Agent: One prompt that Genezio sends directly to the answer engine.
  • Recommender Agent: A multi-step conversation about recommendations.
  • Comparer Agent: A conversation that compares many brands.
  • Introspector Agent: A conversation that examines one specific brand.
To compare the four agent types, refer to How the 5 agents work.

​
Create scenarios

A scenario is a short story that describes a realistic situation. It gives the context, the constraints, and the goals that cause a person to ask an AI assistant for help. A scenario is not a prompt or a question. It is a paragraph with many specific details. Genezio divides the scenario into shorter, natural messages. Then, Genezio sends these messages to the answer engine one at a time, as a person does in a real conversation. A scenario must include:
  • The situation of the persona
  • The goal of the persona
  • Specific constraints (budget, team size, technical requirements, compliance requirements, and other constraints)
A scenario must not include persona details such as role, age, country, or language. You define these details separately in the persona. Genezio combines the persona with the scenario when it runs the conversation. Example scenario:
From this scenario, Genezio makes natural messages such as:
I’m looking for a marketing automation platform that’s easy to set up without any developer help. My team of 6 isn’t very technical. What would you recommend?
Our budget is around $800/month and we need all 6 team members to be able to work in the platform at the same time. Which tools support that?
Does any of these have SOC2 compliance? That’s a requirement for us.
The scenario gives the full picture. Genezio changes it into the exchange of messages that a real person has with an AI assistant.

​
Write prompts for Prompter Agent topics

Prompter Agent topics use prompts, not scenarios. A prompt is a direct question that Genezio sends word for word to the answer engine. The conversation has one interaction only. Example prompt:
Write each prompt as a direct discovery question that a user can ask an AI assistant.

​
Write custom queries for Google AI Overview

For Google AI Overview, Genezio sends a search-style query, not a conversational prompt. For the prompts of the Prompter Agent, Genezio makes this query automatically. You can override the query that Genezio makes and write your own search query. Thus, you can test how a specific Google search changes the results of AI Overview.

​
Use the topics and scenarios that Genezio suggests

Genezio can also make topics and scenarios automatically. During onboarding, or when you extend the analysis, Genezio can suggest:
  • Relevant topics for your category
  • Realistic scenarios for your persona
You can examine and edit these suggestions before you use them.

​
Run the conversations again after a change

When you do one of these actions, Genezio lets you run the conversations again immediately:
  • Add a scenario
  • Edit a scenario
  • Change a topic
Thus, you can test an improvement and see quickly how answer engines respond to the updated scenario.

​
Best practices for realistic scenarios

A good scenario:
  • Is like a short story or a brief, not like a question
  • Describes a clear situation with specific details and constraints
  • Includes a concrete goal of the persona
  • Gives the name of the persona, but does not repeat the persona details (role, location, language)
If a scenario is too vague or too abstract, the responses can mention no brands. This decreases the relevance of the scenario. Do not write scenarios that are similar to prompts. For example: Bad: What is the best CRM for startups? Good: John's team of three has been tracking leads in a spreadsheet but they are losing follow-ups as inbound volume grows. They need a simple CRM that integrates with Gmail and costs under $50/user/month.

​
Next steps

To learn how Genezio changes scenarios into conversations and analyzes the results, read these pages:

​
In the API

To read and change scenarios with the public API, refer to List scenarios.