Logically align assets

Pair personas with scenarios that naturally align. Avoid unlikely combinations—such as a hostile customer calling to join a positive promotion—as they produce unrealistic data and lack real-world utility.

Selecting personas: Focus on objectives, not numbers

Instead of focusing on the number of personas to include in a profile (test suite), prioritize the specific results that you want to achieve. To find the right balance, define your main testing goal:

Testing goal Number of personas
Agent readiness across customer types 5-10 personas. Expose your agents to the full spectrum during training.
A specific edge case or failure mode 1-2 specific personas that reliably trigger the behavior you're investigating.
A specific AI agent interaction (repeatedly and reliably) 1 persona + 1 scenario. This minimizes variables, so you can isolate the flow being tested.
AI agent quality and helpfulness (for example, an FAQ agent) 5-10 personas. Test that the bot handles different communication styles well.
Comprehensive QA As many distinct personas as practical. Maximize variance for realistic coverage.

Key principle: Prioritize unique personas over a high volume of similar ones. While more personas increase variety and realism, adding those with overlapping traits provides little extra value.

Validate your strategy

Ensure every combination is realistic and directly supports the specific testing results you aim to achieve.

  • Negative scenarios: Pair disputes, outages, and complaints with any persona, from friendly to irate. Use the persona to dictate the intensity of the frustration rather than the situation itself.
  • Positive scenarios: Match sign-ups and inquiries with neutral or positive personas. Reserve hostile pairings for rare edge-case testing rather than standard simulations.
  • Complex scenarios: Pair technical or multi-step tasks with confused or impatient personas. This stress-tests an agent’s ability to guide difficult customers through challenging processes.