Lex Ask360 kit overview
Lex Sales360 v1.4.6 is released and available now for internal sales coordination. It combines Email Manager campaign review, BDR speed-to-lead qualification and routing, human Account Executive handoff, opportunity review, and pipeline coaching through 14 governed playbooks. Download the public structure kit, import it into the intended Lead360 sub-account, map destination resources, test the draft Piece, and activate it only after administrator review.
How this fits into Lead360Explore the Lead360 agentic platformSee how the agency, client businesses, and Ask360 workforces fit together.- 01
What the Lex kit is
- 02
How Lex helps
- 03
Pieces and channels
- 04
What the public package includes
What the Lex kit is
Lex Sales360 v1.4.6 is released and available now for internal sales coordination. It combines Email Manager campaign review, BDR speed-to-lead qualification and routing, human Account Executive handoff, opportunity review, and pipeline coaching through 14 governed playbooks.
Designed for a destination sub-account
The package is a reusable starting point for governed Sales360 qualification, routing, handoff, and review. It creates a new Ask360 employee and a draft Piece in the selected destination. It does not connect to the source account or inherit the source business data.
Inside Lead360, the imported structure brings the related Piece, playbook, connector, memory, learning, and approval concepts into one reviewable employee profile. This gives the destination team a consistent starting point while keeping every business-specific decision under its own control.
Product focus
Lex is an official release, but import does not grant unrestricted production authority. Import creates review-state structure only. Destination mapping, reviewed memory, Arena testing, Piece publication, configured channel binding, consent and sender checks, and administrator approvals are required before supported effects can run. Backend-only operations remain unavailable.
How Lex helps
Lex is designed to turn authorized destination evidence into reviewable support, growth, and operational work. The employee should explain what it found, identify missing evidence, separate facts from recommendations, and stop for approval before a live effect.
- Review saved email templates, run a prediction-only pre-send spam-risk preview, and compare observed campaign outcomes before preparing a draft automation without activating or sending it.
- Review consented first-party website-intent aggregates to identify high-interest pages, return patterns, and campaign trends without exposing anonymous visitor identities.
- Start a standard automation after a bounded post-baseline Smart List addition, then use only downstream actions covered by the workflow's exact connector and resource grants.
- Qualify and route a lead from exact destination-owned evidence, with a controlled booking or human Account Executive handoff.
- Review opportunities, stalled stages, meeting outcomes, and pipeline velocity without inventing current CRM facts.
- Prepare a supported, bounded change for exact administrator review while keeping backend-only operations unavailable.
Pieces and channels
Lex Sales360
The public package contains one internal draft Piece for reviewed sales coordination. It cannot inherit a source tenant, memory binding, sender, calendar, channel, workflow, customer record, or approval.
What the public package includes
The public package includes one internal channel requirement, 3 connector requirements, 0 plugin requirements, 14 generic playbooks, 4 fresh Learning Collection definitions, 12 reusable memory folders, proactive schedule settings that import disabled, and one draft internal Piece.
Public-safe structure only
- No source tenant memory files or learning observations.
- No provider credentials, tokens, account IDs, private URLs, contact details, or source tenant identifiers.
- No active schedules, automations, channels, campaigns, messages, payment actions, or advertising changes.
- No destination resource mapping. The administrator must choose every account, app, calendar, campaign, channel, workflow, and business resource.
Download the Lex kit
Download the file only from lead360.io. Keep the filename and checksum together so the destination administrator can verify the archive before upload.
Lex Sales360 v1.4.6 official release, 12.7 KB. No source tenant memory or credentials.
SHA-25604acf27ca79cb2c0002636c851f658dd4afac7511d7d392a63b3078dd5ae1bdfFrequently asked questions
Does the Lex kit contain another business's data?
No. The public package contains no source tenant memory files, learning history, credentials, contact details, provider accounts, or private resource identifiers.
Does importing Lex activate the employee?
No. Import creates a new employee, pending memory guides, generic playbooks, fresh Learning Collections, and a draft Piece. Connections, channels, schedules, automations, memory, testing, publication, and activation remain administrator-controlled.
Can the public kit replace destination setup?
No. It provides a governed starting structure. The destination business must map its own resources, add reviewed knowledge, test allowed and disallowed behavior, and approve launch.
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.
Support