Lead360Support

Configure Piece behavior

Write clear instructions for how an Ask360 Piece should reason about its role, communicate, use sources, and handle uncertainty.

How this fits into Lead360Explore Ask360 Piece StudioUnderstand the commercial operating model behind versioned Ask360 roles.
Lead360 workflow mapConfigure Piece behavior
  1. 01

    How Lead360 helps

  2. 02

    Before you begin

  3. 03

    Complete the workflow

  4. 04

    Understand the key controls

A visual sequence for completing Configure Piece behavior in the intended Lead360 business context.

How Lead360 helps

Behavior translates the Piece identity into consistent operating instructions. It can define response style, source use, clarification, workflow order, escalation, and what to do when evidence is incomplete, while capabilities and safety controls continue to define what is actually possible.

When to use this workflow

Use Behavior after identity, capabilities, and business data are understood, and revise it when Arena evidence shows inconsistent or confusing responses.

Before you begin

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

  • Collect approved operating procedures and customer communication standards.
  • Separate behavioral preferences from hard safety and permission controls.
  • Define how the Piece should cite sources and handle missing or conflicting data.

Complete the workflow

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

  1. Open the Piece draft and select Behavior.
  2. Describe the normal workflow in direct, testable language.
  3. Define clarification, source checking, response style, and escalation.
  4. Remove contradictions, hidden assumptions, and unsupported promises.
  5. Save the revision and test each instruction with an Arena scenario.

Understand the key controls

Instructions are not permissions

Behavior cannot grant an unavailable operation, resource, tenant, or user authority.

Testable language

Use instructions that reviewers can observe in a scenario rather than vague qualities that cannot be evaluated.

Uncertainty

The Piece should identify missing evidence, ask a focused question, or escalate instead of inventing a value or claiming an unverified result.

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.

  • Map each important instruction to at least one Arena scenario.
  • Check behavior under normal, ambiguous, conflicting, and incomplete inputs.
  • Confirm responses remain aligned with Identity and Safety.

Troubleshooting

The Piece follows one instruction but violates another

Remove contradictions, set a clear priority, and keep safety and source requirements explicit.

Responses are verbose or generic

Narrow the role, require task-specific evidence, and provide a concrete response structure without forcing filler.

Frequently asked questions

Can Behavior override Safety?

No. Safety, permission, tenant, and effect controls take priority over ordinary behavioral instructions.

Should behavior include exact business facts?

Stable facts belong in reviewed memory and changing facts belong in live tools. Behavior should explain how to use those sources.

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.

Try Early AccessLearn more about Ask360 Piece Studio Guides