Jasmine Ask360 kit overview

What the Jasmine kit is

Jasmine is the Lead360 Campaigns + Meta Ads Growth Expert. Her four-role Ask360 kit connects customer conversations with campaign, commerce, membership, rewards, referral, booking, customer-app, site, form, advertising, and revenue evidence. Operations can turn verified destination data into approval-ready Lead360 campaigns and paused Meta ad drafts while customer-facing Pieces stay bounded to their assigned channels.

Designed for a destination sub-account

The package is a reusable starting point for Lead360 campaigns, customer conversations, commerce, and Meta Ads growth. 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

Updated September 14, 2026: the official package documents channel-bound custom Pieces for SMS and email, exact approved audiences, campaign edits and paired-channel drafts, branded payment-link setup, and separate activation tests. It includes one draft Operations Piece plus three customer-role setup patterns, not four preconfigured live Pieces. Email draft preparation is supported; end-to-end email delivery remains unverified for this release. No source business data is included.

How Jasmine helps

Jasmine 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.

• Connect Meta campaign and ad evidence with Lead360 leads, reply speed, bookings, purchases, won outcomes, revenue, and message-opener performance.
• Review customer app, commerce, membership, rewards, referral, promotion, and campaign activity using mapped destination records.
• Prepare governed SMS or email campaign drafts with exact audience criteria, sender readiness, consent controls, waits, reply routing, costs or quotas, and results windows.
• Pause an SMS launch when wallet headroom is exhausted, retain the remaining approved audience, and resume without duplicate enrollment after funding and fresh safety checks.
• Create one weekly seasonal or trend-based campaign proposal from current evidence without inventing offers, deadlines, limited spots, prices, or results.
• Recommend keep, pause, or test from verified CTR, CPL and Lead360 outcomes, then prepare one new Meta ad paused for administrator approval while activation and spend remain separate approvals.

Pieces and channels

Jasmine Front Desk

A customer-facing website chat and SMS pattern for service questions, memberships, treatment guidance, availability, deposits, checkout, and booking. Destination publication, sender selection, calendars, memory, and widget assignment require separate review.

Jasmine Lead Response

The custom campaign-conversation pattern for SMS and email. Publish and bind the destination customer Piece separately for each channel, verify its connected sender and reviewed knowledge, and check the generated Ask360 Conversation node. Never substitute another role or a generic AI action when this binding is missing.

Jasmine Automation Concierge

An automation-enrolled lead pattern for deposit-first booking, payment links, and unpaid-deposit reminders. Destination workflows, payment resources, timing, and stop conditions must be created and reviewed separately.

Jasmine Operations

The internal Piece included as a draft in the public kit. It supports reporting, opportunity ranking, customer app and Meta review, campaigns, commerce, memberships, rewards, referrals, sites, forms, approvals, and learning.

What the public package includes

The public package includes one internal channel requirement, 4 connector requirements, 1 plugin requirement, 17 generic playbooks, 3 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 Jasmine kit

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