SupportChoose a Piece model
Select supported model settings for the Piece role, test them with the same scenarios, and treat model changes as revision changes.
How this fits into Lead360Explore Ask360 Piece StudioUnderstand the commercial operating model behind versioned Ask360 roles.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Piece model settings determine which supported language model configuration runs the role. Lead360 keeps the selection inside the versioned draft so teams can compare behavior, quality, latency, and policy fit through consistent Arena scenarios before publication.
When to use this workflow
Use model selection after the role, tools, data, behavior, and safety are defined, or when a supported model change must be evaluated.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Define task quality, latency, reliability, and data-handling requirements.
- Prepare a stable Arena scenario set and expected outcomes.
- Identify any provider or plan availability limits.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the Piece draft model settings.
- Review supported choices and availability for the sub-account.
- Select one model configuration for the draft.
- Run the same Arena scenarios used for the current baseline.
- Compare evidence, resolve regressions, and save the model choice in the revision.
Understand the key controls
Versioned selection
A model change belongs to a new Piece revision and should not silently alter an immutable published version.
Same-test comparison
Use the same prompts, resources, and expected outcomes when comparing models so observed differences are meaningful.
No capability expansion
Changing the model does not grant new tools, memory, tenants, or operation permissions.
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 scenario outcomes, refusals, source use, latency, and consistency.
- Retest consequential and edge-case scenarios.
- Confirm the saved revision and published version use the intended model setting.
Troubleshooting
A model option is unavailable
Check deployment support, sub-account access, and current product configuration. Do not work around availability by embedding external credentials in the Piece.
Quality changed after model selection
Compare the exact revision, resources, and scenarios, then adjust behavior or choose the prior supported setting before publication.
Frequently asked questions
Does changing the model change the published Piece?
Not until the new revision completes review and is published explicitly. Published versions remain immutable.
Can model selection replace Arena testing?
No. Every supported choice should be evaluated against the role-specific scenario set and safety expectations.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.