SupportCreate and manage Ask360 bots
Create a tenant-scoped Ask360 bot profile and assemble its channels, capabilities, playbooks, memory, plugins, and effect policies.
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 bot profile defines a named operational role inside one sub-account. The profile becomes useful only when administrators deliberately assign the channels, capabilities, automations, connectors, plugins, playbooks, memory resources, and effect controls required for that role.
When to use this workflow
Use Ask360s when the business needs a repeatable bot identity with a clear audience and responsibility rather than a one-off workspace conversation.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Define the bot name, role, audience, owner, and success criteria.
- List required tools and knowledge separately from optional resources.
- Document prohibited actions, escalation paths, and human review requirements.
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 Ask360s.
- Create a bot profile with a clear role and tenant-specific identity.
- Assign the minimum capabilities and resources required for the first workflow.
- Attach reviewed memory, playbooks, and supported plugins or connectors.
- Test the bot in a controlled channel and review every effect before enabling broader use.
Understand the key controls
Profile versus Piece
A bot profile assembles runtime resources and channel behavior. A Piece is a versioned internal role definition that can be attached where supported.
Exact resource grants
A bot does not inherit every sub-account resource by default. Connectors, plugins, Memory Sets, Learning Collections, and playbooks are assigned explicitly.
Lifecycle
Bots can be changed, disabled through channels, exported as kits, or removed according to their dependencies and audit requirements.
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 complete capability and resource summary.
- Test normal, ambiguous, sensitive, and disallowed requests.
- Confirm channel behavior and live operation evidence before launch.
Troubleshooting
A new bot cannot complete a task
Check capability, connector, plugin, playbook, memory, and effect-policy assignments one layer at a time.
The bot has more access than expected
Remove optional capabilities and resources, retest the smallest intended workflow, and review channel and agency-level grants.
Frequently asked questions
Does creating a bot automatically connect channels and data?
No. The profile is tenant-scoped, but capabilities, channels, connectors, plugins, playbooks, and memory are assigned separately.
Can a bot be copied to another sub-account?
Use the portable Ask360 kit workflow. Exports remove tenant identifiers and credentials, and imports require new resource mapping, review, and activation.
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.