SupportManage Ask360 bot memory
Assign reviewed files, Memory Sets, Learning Collections, observations, insights, and manual memory to the exact bot that needs them.
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
Bot Memory shows the knowledge resources available to one Ask360 bot without turning knowledge into tool permission. Administrators can combine reviewed files, immutable Memory Sets, live Learning Collections, promoted insights, and carefully scoped manual memory while preserving source and tenant boundaries.
When to use this workflow
Use Bot Memory when a bot needs stable business context, approved subsets, recent privacy-safe learning, or a small piece of manual operational context.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Classify the information as stable reviewed knowledge, a live filter, a verified insight, or temporary manual context.
- Remove credentials, payment details, and unnecessary personal information.
- Confirm the bot role requires the information.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the bot profile and select Memory.
- Review current files, Memory Sets, Learning Collections, observations, insights, and manual entries.
- Assign the smallest appropriate resource type.
- Test retrieval with an expected question and a question outside the resource scope.
- Remove stale manual entries and unneeded resources after verification.
Understand the key controls
Knowledge is not capability
Memory can help a bot answer but never grants a connector, operation, profile, tenant, or live write target.
Immutable and live resources
Memory Sets preserve exact reviewed revisions. Learning Collections evaluate their saved category, scope, and history filters against current eligible learning.
Manual memory
Manual entries should be small, non-sensitive, owned, and removed when no longer accurate.
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.
- Confirm the bot cites or uses the intended resource.
- Test that excluded knowledge is not retrieved through this assignment.
- Review source timestamps and use live tools for changing values.
Troubleshooting
The bot cannot find reviewed content
Check review state, available snapshot, Memory Set contents, bot assignment, and the exact query language.
The bot uses stale information
Replace or review the source revision, update the Memory Set binding, and keep live prices, availability, and transaction states in product tools.
Frequently asked questions
Does bot memory grant access to live actions?
No. Memory supplies knowledge only. Live actions require separate capabilities, resources, user authority, and effect controls.
Should changing values be stored in a Memory Set?
Stable explanations can be stored, but current availability, prices, payment status, and other live values should be queried through their owning Lead360 tools.
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.