Nexus v2 Ask360 kit overview

What the Nexus v2 kit is

Nexus v2 is one portable Ask360 kit with four intentionally separated Pieces: Customer Support, Support Operations, Support Automation, and Support Learning. Together they cover the full support lifecycle without collapsing customer communication, internal reporting, automated events, and learning into one confusing role.

Designed for a destination sub-account

The package is a reusable starting point for provider-neutral customer support and support operations. It creates a new Ask360 employee and four unpublished draft Pieces in the selected destination. It does not connect to the source account or inherit source business data.

Inside Lead360, the four Pieces remain separate while their 43-capability provider contract is governed through MCP, Apps, and APIs. Playbooks, memory, learning, channels, and activation stay reviewable and destination-controlled.

Product focus

The kit carries one 43-capability support contract and four role-specific mappings. Provider connections stay destination-owned and are selected through MCP, Apps, or APIs; no Lead360 key, private backend binding, or active grant is included in the download.

How Nexus v2 helps

Nexus v2 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.

• Answer a customer-scoped support question from reviewed public help and the exact authorized ticket or conversation.
• Prepare an approved customer reply without silently choosing the sender, recipient, or sending it.
• Review queue volume, aging, SLA risk, ownership, timeline evidence, and the next accountable action.
• Triage a verified provider event, deduplicate it, route it to the correct owner, and stop safely when the provider is unavailable.
• Identify a recurring issue or knowledge gap from privacy-safe verified outcomes without copying raw customer records into learning.
• Connect a provider owned by the destination tenant through MCP, Apps, or APIs, then assign only supported capabilities to each Piece.

Pieces and channels

Customer Support

A customer-facing Piece limited to reviewed public help and exact authorized customer context. It clarifies uncertainty, prepares responses, and hands off sensitive or unsupported cases.

Support Operations

An internal staff Piece for ticket detail, queue health, aging, SLA, recurring issues, evidence-backed drafts, escalation, and controlled status work.

Support Automation

A system Piece for verified events, deterministic routing, reminders, deduplication, cooldowns, bounded retries, and audited status synchronization.

Support Learning

A read-only staff Piece for verified outcome review, recurring gaps, CSAT evidence, and knowledge candidates that remain subject to human review.

What the public package includes

The public package includes two destination channel requirements, a disconnected provider-choice profile, the complete 43-capability support API contract, 7 generic playbooks, one fresh Learning Collection definition, 6 reusable memory folders, proactive settings that import disabled, and four unpublished draft Pieces.

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 Nexus v2 kit

Download the file only from lead360.io. Keep the filename and checksum together so the destination administrator can verify the archive before upload.