SupportSync Lead360 data into Memory Brain
Create reviewable Memory Brain revisions from supported Lead360 business sources without making them available automatically.
How this fits into Lead360Explore Ask360 memory and learningSee how reviewed business knowledge supports exact roles and client boundaries.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Memory sync converts supported tenant data into normalized, reviewable knowledge files for catalogue, business, memberships, booking, campaigns, and operations. It preserves source context and creates pending revisions so a reviewer can inspect exact content before any new snapshot or Memory Set uses it.
When to use this workflow
Use sync when stable business context already exists in Lead360 and should become governed knowledge for a Piece or bot.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Choose the supported source area and exact sub-account.
- Decide which values are stable knowledge and which must remain live queries.
- Assign a reviewer familiar with the source records.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Memory Brain and select the supported Lead360 sync source.
- Preview the records or categories that will be normalized.
- Start the sync to create or update pending file revisions.
- Review source evidence, normalized text, and checksums.
- Mark approved revisions reviewed and make a new snapshot available through the normal release flow.
Understand the key controls
Pending by default
Sync does not silently publish knowledge. New or changed files require review and a later available snapshot.
Supported source families
Use the product sync controls for catalogue, business, memberships, booking, campaigns, and operations rather than copying database output into memory.
Live values
Current availability, transaction state, balances, and other fast-changing values still belong in live Lead360 tools.
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 file counts and source identifiers with the preview.
- Review normalized content and revision status.
- Confirm the intended available snapshot and consumer binding after approval.
Troubleshooting
A supported record is missing
Check source status, tenant, eligibility, permissions, and sync category before creating a manual duplicate file.
A sync overwrote reviewed knowledge
Sync creates or updates revisions. The prior available snapshot and immutable Memory Sets remain unchanged until a reviewer releases new content and binds it.
Frequently asked questions
Does sync update every Piece automatically?
No. It creates pending revisions. Review, snapshot availability, Memory Set membership, and Piece binding remain explicit.
Should live booking availability be stored in memory?
No. Store stable booking explanations in memory and query current availability through the live calendar 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.