Use Roleplay Scenario Name to identify bots in Hyperbound

Last updated: June 3, 2026

You can now use a Scenario Name to identify bots across Hyperbound.

If a bot has a Scenario Name set, Hyperbound will use that as the primary name in key admin and navigation surfaces. This makes it easier to recognize the right bot at a glance, especially when multiple bots use similar personas.

The persona still remains visible during the actual roleplay experience, including pre-call, in-call, and post-call views.

image.pngimage.png

Scenario Name is now available for all bot types. If it’s left blank, nothing changes and Hyperbound will keep showing the persona name.

Best practices

Use a Scenario Name when you want the bot name to reflect the scenario rather than just the character.

A good Scenario Name should:

  • describe the situation clearly

  • be easy to scan in lists

  • distinguish similar bots from each other

Use cases

Use case

Example scenario name

Objections

"Pricing objection"

"Security threat objection"

"Budget pushback"

Persona

"Enterprise CXO"

"MM Industry leader"

"SMB managers"

Persona + Scenario

"Enterprise CXO pricing objection"