SupportAsk360 kits overview
Package a portable Ask360 bot configuration for controlled download, review, import, remapping, testing, and activation.
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
An Ask360 kit is a portable archive that can include bot identity, channel requirements, capabilities, effect policies, playbooks, automations, memory structure or reviewed files, Learning Collections, proactive settings, an optional portable Piece, and a README. Lead360 removes tenant identifiers, credentials, and source bindings before export.
When to use this workflow
Use a kit when a tested bot configuration should be transferred, backed up for review, or offered as a reusable starting point for another sub-account.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Confirm the source bot and every included resource are approved for portability.
- Choose structure-only or complete reviewed memory intentionally.
- Remove or rewrite tenant-specific instructions and private business content.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Review the source bot configuration and dependencies.
- Preview the intended kit contents and memory mode.
- Download the .ask360 archive and protect it as business configuration.
- Preview the archive in the destination sub-account.
- Import, remap resources, review memory, test, and activate manually.
Understand the key controls
Portable format
The .ask360 file uses the Lead360 Ask360 kit archive format and includes checksums and safety limits.
No credentials
Exports strip tokens, provider credentials, tenant identifiers, and live source bindings.
Safe destination state
Imported memory starts pending review, schedules and automations are disabled, observations start fresh, and the optional Piece starts as a draft.
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 the preview manifest with the intended source resources.
- Confirm no credential or source tenant identifier appears in the archive.
- Complete destination mapping, review, testing, and activation.
Troubleshooting
A kit is larger than expected
Review complete-memory selection and attached files. The archive is limited to 128 MB and expanded content to 256 MB.
A named kit is not available
Only published, tested kit artifacts should be offered. A bot name or template in source code is not itself a downloadable .ask360 kit.
Frequently asked questions
What file type does an Ask360 kit use?
Lead360 downloads a .ask360 portable archive using the Ask360 kit format. Treat it as controlled business configuration.
Does a kit include API keys or connected accounts?
No. Credentials and tenant-specific source bindings are removed. The destination administrator maps approved resources 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.