Skip to main content
Test profiles live on the Test Profiles tab under Simulations. They apply to simulation runs, so you need an agent set up for inbound or outbound simulation to use them.

What are test profiles?

A test profile is a named set of key-value fields that the Simulated Caller is given before the call starts. With it, the caller can play a specific type of customer, such as a new user who doesn’t know the product, an angry user on a repeat call, or someone in a rush, and refer to their own name, issue and reason for calling. Without a test profile, the Simulated Caller has no caller-specific context.
  • Profile data is snapshotted when the run starts. Editing or deleting a profile later doesn’t change results from that run.
  • Profiles are scoped to the agent. Profiles created for one agent aren’t visible to other agents in your workspace.

The Test Profiles tab

Go to Simulations and open the Test Profiles tab to manage profiles for your agent. Test Profiles list showing New User, Angry User, and Rushed User profiles with their field tags Each profile card shows:
  • Profile name: what you see when selecting it in the Run Simulation dialog.
  • Field tags: the key names defined in the profile (for example caller_name, issue, urgency).
When no profiles exist yet, the tab shows No test profiles yet.

Create a profile

1

Open the form

Click Create Profile on the Test Profiles tab.Create test profile modal with profile name and key-value field inputs
2

Name the profile

Enter a Profile name that identifies the caller, for example Angry User, New patient, first visit or Rushed Caller.
3

Add fields

Under Profile fields, click Add field for each key-value pair. The key is the variable name (for example caller_name, issue, urgency) and the value is what the Simulated Caller knows (for example Jane Doe, billing error, high).
  • Keys start with a letter or underscore and contain only letters, numbers and underscores. Each key can appear once.
  • Values are plain strings, one level deep, with no nested objects.
For outbound agents, you can also pass a field to your trigger endpoint: write {{profile.<key>}} in the trigger body, for example {{profile.caller_name}}. Tuner replaces it with the field’s value. A key the profile doesn’t have, or a run without a profile, gives an empty string. See Set up outbound simulation.
4

Save

Click Save. A profile needs a name and at least one field.

Use a profile in a run

In the Run Simulation dialog, under Call settings, click Change next to Test profile:. Run Simulation dialog showing Test profile selector with No profile, New User, Angry User, and Rushed User options Choose one:
  • No profile: the Simulated Caller has no caller-specific context. This is the default.
  • Any profile from your list: the Simulated Caller is given its fields before the call starts.
Then click Done. The profile applies to every call in the run, and you can combine it with any Simulation Mix, language or environment. For example, run 10 calls with the Angry User profile focused on escalation-handling Pressure tests.

Edit a profile

Click the pencil icon on a profile card to open Edit test profile. You can rename the profile, add fields, change keys or values, and remove fields. Click Save. Changes apply to future runs only. Runs that already used the profile keep the snapshot taken when they started.

Delete a profile

Click the trash icon on a profile card, then confirm in Delete test profile. Deleting a profile can’t be undone, but past runs that used it keep their snapshotted profile data.

Limits

Test profiles are also available through the public API, in the Simulation group of the API Reference.

Next steps

Introduction to Call Simulation

How the Simulation Mix, Routine callers and Pressure tests work together.

Set up outbound simulation

Pass test profile fields to your trigger endpoint.