SupportUpdate a Piece consumer
Move a bot, automation, chat widget, or other supported consumer to an approved Piece version through an explicit controlled change.
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
Consumer updates keep publication and deployment separate. A new Piece version can exist without changing live bots, Automations, Chat Widgets, or other consumers, which lets teams test compatibility and choose a controlled rollout schedule for each use case.
When to use this workflow
Use a consumer update after the new Piece version is published and the specific consumer has been reviewed for compatibility.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Identify the current and target Piece version identifiers.
- Review channel, capabilities, resources, inputs, and expected behavior for the consumer.
- Prepare a test and recovery plan.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the supported consumer configuration.
- Review its current Piece version and dependencies.
- Select the approved target version.
- Save or deploy the consumer change through its normal workflow.
- Run a controlled end-to-end test and confirm live behavior and audit evidence.
Understand the key controls
Independent rollout
Each consumer can remain on a prior published version until its own compatibility and timing are approved.
Consumer context
A Piece can behave differently when channel, input, resource, or effect context differs, so test the real consumer surface.
Recovery
Keep the prior compatible version and deployment evidence available when a rollback is supported.
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.
- Confirm the consumer shows the target version identifier.
- Test normal and high-risk requests through the real surface.
- Monitor errors, refusals, customer impact, and downstream effects after rollout.
Troubleshooting
The target version is unavailable
Confirm it was published in the same tenant and that the consumer supports the Piece type and version.
The consumer works in Arena but not live
Compare channel context, user authority, resource mappings, inputs, and live provider state with the Arena setup.
Frequently asked questions
Why does Lead360 not update every consumer automatically?
Independent updates let teams review compatibility, test each surface, control rollout timing, and recover without changing unrelated workflows.
Should every consumer use the latest Piece version?
Use the latest approved compatible version, not automatically the newest. Review each consumer before moving it.
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.