Jasmine capabilities, Pieces, and controls

Role and intended outcomes

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.

The role is evidence-based and permission-aware. A successful answer should identify the destination records used, the relevant time window, uncertainties, the recommended next action, and the person or approval required.

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

Powered by Ask360

Channels

• Website visitors through the Front Desk pattern.
• Campaign replies through the Lead Response pattern.
• Deposit-required leads through the Automation Concierge pattern.
• Internal planning, reporting, campaign preparation, approvals, and learning through Operations.

Ask360 Pieces

• Jasmine Front Desk for treatment guidance, availability, deposits, checkout, and booking help.
• Jasmine Lead Response for campaign education, replies, governed follow-up, and booking.
• Jasmine Automation Concierge for deposit-first booking and verified unpaid-deposit reminders.
• Jasmine Operations for reporting, opportunity ranking, campaign creation, approvals, and outcome learning.

Connectors

• Lead360 for tenant-scoped CRM, conversations, campaigns, calendars, forms, sites, pipeline, and reporting.
• E-Commerce for services, memberships, purchases, customer activity, and governed contact-level membership, rewards, promotion, wallet, and referral lookups.
• Automation Pieces for mapped workflow, wait, reply, booking, deposit, and follow-up context.
• Sites Builder AI for mapped sites, pages, funnels, forms, widgets, and campaign destinations.

Automations

• Workflows are created or assigned to the destination Pieces and enabled only under their mapped permissions and matching approvals. The portable package contains no live workflows.
• Generated SMS and email workflows must use the assigned published customer Piece for that channel through Ask360 Conversation. A renamed node is not proof of a valid binding; a missing binding must stop preparation instead of substituting a generic AI action.
• SMS and email use separate reviewed workflows, senders, channel-specific consent and launch approvals, even for one campaign topic. Email drafts can use reviewed templates, verified service images, HTML and plain text; sender and unsubscribe readiness must be tested.
• Editing a campaign or adding its other channel must preserve its topic and exact approved audience. Channel-specific Smart Lists must not change the original source list; a missing or changed audience requires review, not a similarly named replacement.
• Explicit waits, reply and booking stops, one governed no-reply follow-up, and outcome tracking.
• A named Smart List stays authoritative: Jasmine recalculates its live opted-in, non-DND audience, while unnamed re-engagement groups use their own eligible count rather than the whole account total.
• Wallet-aware SMS partial launch, funding-required pause receipt, persisted remaining audience, and duplicate-free resume.
• Deposit reminders and payment or booking safeguards only when the destination has verified the required offer and resources. Configure slot holds, expiry and deposit or full-payment choice; use verified branded short payment links with the supported app.lead360.io fallback.

Memory

• Twelve reusable folder guides and three fresh Learning Collection definitions; no source tenant memory files or learning observations are included.
• Destination teams may add reviewed services, policies, memberships, rewards, referrals, campaign rules, and operating knowledge, then bind an approved Memory Set or snapshot.
• Learning remains timestamped, evidence-backed, tenant-isolated, and separate from reviewed business knowledge. Memory Sets bind reviewed knowledge, not CRM snapshots; Learning Collections store governed observations, not fine-tuned model weights.

Plugins

• Meta Ads is the only plugin requirement. Its reporting and governed ad-management capabilities are described separately below. The destination must connect its own account, authorize the required scopes, grant the Piece the required tools and select exact resources.

Playbooks

• Seventeen generic playbooks, including Weekly Meta To CRM Quality, Weekly Creative And Opener Review, Weekly Winning Ad Recommendations, the 72 Hour Campaign Opportunity, Weekly Seasonal Campaign Studio, and Catalogue Contact Rotation.
• Evidence-based weekly and 72-hour campaign reviews retain their evidence requirements. Catalogue Contact Rotation is a separate catalogue-discovery path that can propose a service without a performance signal; it does not bypass consent or authorize an automatic blast.
• A campaign-shell approval creates no audience, tag, workflow or send. Automatic daily waves through the whole contact base must not be assumed from the rotation playbook alone.
• Imported playbooks remain reviewable starting points and schedules import disabled.

Proactive

• Portable proactive settings are included but import disabled so the destination chooses its own operating days, hours, timezone, interval, cooldown, channel, and owner.
• Material-change and semantic duplicate suppression prevent filler recommendations and competing campaign proposals. An hourly check does not run every weekly or 72-hour playbook hourly; test each due schedule and its failure receipt separately.
• This package does not upgrade existing installed employees or install shared server fixes. Receiving teams must review their bindings and test each channel before activation. The release specification and test checklist are included in the download.

Ask360 Pieces

A Piece defines identity, channels, allowed operations, reviewed business data, behavior, limits, safety boundaries, and model settings. The public kit imports the internal operations Piece as a draft. Customer-facing Pieces described below require separate destination configuration, Arena testing, publication, and channel assignment.

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.

Connectors and apps

A connector requirement does not carry a connection. After import, the destination administrator must connect the provider, confirm the owning sub-account, select exact resources, and verify user and employee permissions.

Lead360

Provides mapped CRM, conversation, opportunity, calendar, campaign, form, site, customer app, pipeline, and reporting operations.

E-Commerce

Provides mapped services, products, packages, memberships, checkout, purchases, customer activity, and governed membership, rewards, promotion, wallet, and referral context.

Automation Pieces

Provides mapped workflow and run context. Imported schedules and automations remain disabled until the destination administrator reviews resources, waits, sender identity, stop conditions, and ownership.

Sites Builder AI

Provides mapped websites, pages, funnels, forms, widgets, and campaign destinations for review and draft preparation.

Plugins

Meta Ads

Provides governed advertising reads and approval-gated status, budget, paused-ad, and paused-retargeting operations after the destination account, required permissions, and exact resources are connected.

Playbooks included for review

The public kit contains 17 generic playbooks. They preserve the intended review categories without source prompts, private business instructions, tool snapshots, or provider identifiers.

• Jasmine Operations Briefing
• Jasmine Meta Ads Performance
• Jasmine Daily Lead Response Brief
• Jasmine Weekly Meta To CRM Quality
• Jasmine Weekly Creative And Opener Review
• Jasmine Campaign Change Outcome Review
• Jasmine Bookings Qualified Leads Sales Revenue
• Jasmine Ad To Revenue Learning
• Jasmine Commerce Growth
• Jasmine Growth Outcomes
• Jasmine Lead To Revenue Learning
• Jasmine Customer Growth Review
• Jasmine Evening Commerce Pulse
• Jasmine 72 Hour Campaign Opportunity
• Jasmine Weekly Seasonal Campaign Studio
• Jasmine Catalogue Contact Rotation
• Jasmine Weekly Winning Ad Recommendations

Imported playbooks are starting points. Open each one, map destination resources, confirm read and write boundaries, test the output, and schedule it only when its owner, frequency, delivery channel, and stop conditions are documented.

Memory and Learning Collections

Memory folders

The kit creates 12 pending collection guides and zero source memory files. Upload current destination policies, products, services, app content, campaign rules, support guidance, or other approved knowledge into the matching folders. Review each file and make it available before binding it to a new Piece revision.

Fresh learning definitions

• Advertising and Revenue Learning
• Commerce and Customer Learning
• Business Operations Learning

Learning observations do not transfer between businesses. Every collection starts empty and should learn only from eligible destination evidence after its categories, lookback window, limits, consumer binding, and privacy policy are reviewed.

Risk controls

• The imported Piece remains a draft and has no inherited source memory binding.
• Schedules, proactive recommendations, and standalone automations remain disabled.
• Meta Ads and Automation Pieces effects require explicit destination connection and administrator approval where applicable.
• Customer communication must respect consent, sender identity, opt-out, do-not-disturb, quiet-hour, and channel-provider requirements.
• Advertising, app, payment, booking, campaign, membership, and customer-facing changes require review in the owning Lead360 area.
• Generated output may be incomplete or wrong and must be reviewed before consequential use.