SupportCreate and manage Ask360 playbooks
Turn a repeatable operating procedure into a reviewable Ask360 playbook with controlled resources, scheduling, runs, and export.
How this fits into Lead360Explore Ask360See how Pieces, memory, channels, playbooks, learning, and kits work together.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Ask360 Playbooks capture a repeatable sequence for investigating, preparing, or carrying out supported work. They can use assigned resources and memory, run manually or on a schedule where supported, and preserve run evidence so teams can review what happened.
When to use this workflow
Use a Playbook for a multi-step procedure that should be followed consistently by a bot or team and can be tested with known inputs and expected results.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Write the purpose, inputs, steps, outputs, owner, and stopping conditions.
- Assign only the memory, connectors, plugins, and capabilities required.
- Identify customer-facing, financial, destructive, or external effects that need confirmation.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Ask360 Tools and select Playbooks.
- Create or import the playbook and define its goal and sequence.
- Attach required memory and resources.
- Test a manual run with controlled inputs and inspect every step.
- Enable a schedule only after idempotency, failure handling, and ownership are verified.
Understand the key controls
Playbook state
A saved playbook is not automatically scheduled or enabled. Manual and scheduled execution remain explicit.
Run history
Each run should be reviewed by inputs, steps, outputs, errors, and final live evidence.
Portability
Playbooks can be exported and included in Ask360 kits, but credentials and tenant resource bindings must be remapped after import.
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.
- Review the exact playbook version and resource assignments.
- Confirm run output against source records.
- Test failure, retry, duplicate, and disabled-resource behavior.
Troubleshooting
A scheduled playbook does not run
Check enabled state, schedule timezone, owner, resource availability, and prior run or cooldown conditions.
A playbook stops mid-run
Inspect the failed step, missing input, connector or plugin state, confirmation requirement, and whether retrying is safe.
Frequently asked questions
Does saving a playbook enable its schedule?
No. Scheduling and enablement are separate controls and should follow successful controlled testing.
Can a playbook carry credentials when exported?
No. Credentials and tenant-specific resource bindings must not be included. They are remapped through approved connections after import.
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.