To write effective scenarios in Genezio, start from the real questions of your buyers. A scenario is the situation of a persona who asks an answer engine for help. This guide tells you how to write good scenarios and how to change the type of a scenario later. A good scenario is similar to the questions that your customers really ask answer engines. It includes the constraints and the follow-up questions that have an effect on which brands the answer engine recommends. For each topic, Genezio makes scenarios for different intents. The intents go from open discovery questions to direct requests for a recommendation and questions about a specific brand. You can examine and edit these scenarios before you confirm them.

​
How to write scenarios that copy real buyers

  • Copy a real buyer: Write scenarios from real customer questions, call transcripts, and FAQs.
  • Include constraints: The team size, the budget, the location, and the technology stack all have an effect on the recommendations.
  • Include branded and non-branded entry points: Measure how answer engines find your brand, and how they examine your brand by name.
  • Add follow-up turns: A conversation with many turns shows the deeper reasoning of the model.
Each scenario is the situation of a persona. To make strong personas first, read Generate personas from documents.

​
Change the type of a scenario after the setup

Your first selection is not permanent. You can later convert an existing scenario to a different type. For example, you can convert a Prompter into a Recommender. You select the persona for the converted scenario. For the available scenario types and when to use each type, read Scenarios. For the agent that runs each type, read How the 5 agents work.

​
Next steps

After you confirm your scenarios, Genezio runs conversations with answer engines. To monitor them, read Run conversations.

​
In the API

The public API reads and changes scenarios in List scenarios.