Test a Piece in Arena

How Lead360 helps

Arena gives reviewers a controlled environment for testing how a Piece uses its identity, tools, memory, behavior, safety, and model settings. The synthetic customer stays inside the test environment and does not enter Contacts, which allows teams to explore normal and difficult cases before live use.

When to use this workflow

Use Arena after validation, after any material revision, and before publishing or updating a consumer to a new Piece version.

Before you begin

Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.

• Save and validate the exact revision to test.
• Prepare expected outcomes and source data for each scenario.
• Include normal, ambiguous, missing-data, sensitive, disallowed, and failure cases.

Complete the workflow

Follow the steps in order and stop when a required resource, permission, review, or approval is missing.

1. Open the Piece revision and select Arena.
2. Create or choose a scenario with a clear expected outcome.
3. Run the scenario and continue turns needed to expose the full workflow.
4. Review responses, source use, tool proposals, refusals, and evidence.
5. Record findings, revise the Piece, and rerun the same scenario until the result is acceptable.

Understand the key controls

Synthetic customer

Arena customer activity stays in the test environment and does not create a live Contact or ordinary customer conversation.

Exact revision evidence

A run evaluates the selected draft or version. Changing the Piece means prior evidence no longer proves the new revision.

Realistic boundaries

Include what the Piece should refuse or escalate, not only happy-path prompts that are easy to satisfy.

Confirm the result

Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.

• Compare each turn with the expected outcome.
• Check source attribution and proposed effects.
• Preserve passing and failing evidence for review and certification.

Troubleshooting

A scenario passes inconsistently

Reduce ambiguity, inspect model and source variability, tighten behavior, and repeat enough runs to understand the pattern.

Arena cannot access a resource

Check the draft resource binding and Arena availability. Do not assume a production connection will make an untested scenario pass.