SupportPreview and import an Ask360 kit
Inspect a .ask360 archive, create a new destination bot, remap resources, review memory, test behavior, and activate it manually.
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
Kit import creates a new destination bot from a portable archive without silently connecting source resources or enabling live behavior. Lead360 validates the archive, shows a preview, creates pending memory and draft resources, disables schedules and automations, and records an import ledger for controlled cleanup.
When to use this workflow
Use import when an approved .ask360 kit should become a new bot starting point in the current sub-account.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Verify the kit source, owner, version, and intended destination.
- Review the preview manifest, included memory mode, capabilities, playbooks, automations, and optional Piece.
- Identify destination connectors, plugins, channels, and resources that require mapping.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Ask360 kit import in the destination sub-account.
- Upload the .ask360 file and review validation results and manifest.
- Approve creation of the new disabled bot and draft resources.
- Map channels, connectors, plugins, automations, and other destination resources.
- Review pending memory, test the bot and Piece, then enable schedules, automations, and channels only when ready.
Understand the key controls
Fresh destination state
The import creates a new bot. Learning observations start fresh, imported memory requires review, and portable Pieces remain drafts.
No inherited connections
Credentials, provider accounts, and source tenant bindings are not carried into the destination.
Admin activation
Schedules, automations, and channels are not activated merely because the archive imported successfully.
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 created resources with the preview and import ledger.
- Review and make available only approved destination memory.
- Test allowed, disallowed, failure, and customer-facing scenarios before activation.
Troubleshooting
The archive fails validation
Confirm it is an unmodified supported .ask360 kit within archive, expanded size, file count, path, and checksum limits.
An imported workflow cannot run
Map its destination automation, connector, plugin, channel, or resource and confirm current user and bot permissions.
Frequently asked questions
Does importing a kit activate its bot?
No. The destination administrator must map resources, review memory, test behavior, and enable channels, schedules, and automations.
Does imported learning history come from the source tenant?
No. Learning observations start fresh in the destination. The kit can carry reviewed memory or Learning Collection definitions according to its manifest.
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.