Chloe capabilities, Pieces, and controls

Role and intended outcomes

Chloe 2.0 is Lead360's official Meta Growth Expert kit, ready to configure and activate. Four dedicated Pieces bring together Employee Ops, website Front Desk, Home-app Concierge and campaign Lead Response, with 16 playbooks and five proactive schedules.

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.

• Receive one daily 9:00 AM Meta-to-Lead360 performance post with evidence-backed recommendations and no automatic changes.
• Every five days, find the strongest exact dormant service-tag cohort and prepare a separately approved reactivation path without treating tags as consent.
• Every seven days, identify one verified winning source ad and prepare a new ad PAUSED only after approval.
• Explain why a winner, audience, creative, placement, budget, or recovery angle was chosen using the exact evidence available.
• Continue using connected Lead360 CRM, campaign, automation, pipeline, booking, commerce, and revenue insights when Meta is unavailable, while marking fresh Meta evidence unavailable.

Powered by Ask360

Customer booking and conversation continuity

• Customers choose a real appointment time. Chloe holds the selected slot for up to 96 hours, offers deposit or full payment and confirms the booking after successful payment.
• Checkout uses the sub-account verified branded short-link domain, falling back to app.lead360.io when no verified branded domain exists.
• The widget, contact form and staff conversation retain the same customer context. Service availability and campaign preparation use the assigned menu and current destination resources.
• The compatible Lead360 platform provides these shared runtime improvements. The portable kit supplies configurations and setup guidance; it does not install platform software.

Five proactive playbooks: three featured plus two supporting

• Daily Meta Growth Report: every day at 9:00 AM in the destination timezone, joining the previous calendar day of Meta delivery to exact Lead360 opener coverage, replies, bookings, wins, and revenue.
• Five-Day Tagged-Lead Reactivation: every five days at 9:00 AM, ranking exact service-tag cohorts after five days without contact activity while reporting consent-qualified eligibility and exclusions.
• Seven-Day Winning-Ad Review: Mondays at 9:00 AM, comparing the latest seven complete days with the prior period and identifying one evidence-backed winner.
• Catalogue Contact Rotation: Mondays at 9:00 AM, choosing the next unused eligible catalogue service from a consent-safe audience without requiring a performance signal.
• Ad-to-Revenue Learning: daily at 9:00 AM, joining verified Meta delivery to Lead360 outcomes, posting material changes, and measuring approved changes after 14 days.

Approval boundaries

• Scheduled reports never change Meta, create audiences, create campaign assets, enroll contacts, or send messages.
• Approve the campaign card and Chloe prepares the audience and messages card automatically. Approve that card and Chloe prepares the separate launch card. Each approval advances only its own stage; launch rechecks eligibility, sender readiness, consent and funding.
• A separate winning-ad command may prepare one approval that creates the new ad PAUSED. Activation, budget changes, and other status changes require another fresh approval.

Generation, memory, and learning

• The Piece name is chosen by the owner. Gen 1, Gen 2, and later generations are assigned automatically from that Piece's publication history, not hard-coded into its name. A shared kit imports as a new draft and receives its own destination generation when published.
• Attaching a Memory Set gives a playbook a named subset of reviewed files as runtime context. It does not schedule the playbook, connect a provider, grant a tool or write, or expand tenant scope. Re-save an existing schedule to freeze the new memory version.
• Learning Collections filter verified, timestamped insights by category, Learning scope, and History window. They do not create memory files, connect Meta, import account data, or fine-tune model weights.
• A disconnected, revoked, or suspended Meta account produces a truthful unavailable result instead of guessed performance. Other connected Lead360 evidence remains available under its own connector state.

Easy setup in Lead360

• Memory Set: Automations > Ask360 Piece Studio > Memory Brain > Sets & learning > Create a Memory Set. Choose reviewed files and save, then attach it from the playbook's Memory used by this playbook selector or from the Piece or Ask360 Memory controls.
• Learning Collection: in Sets & learning, name the collection, describe what it should remember, select Live Insight categories, Learning scope, and History window, then save and attach it to the intended Piece or Ask360.
• Signal playbook: Dashboard > Ask360 tools > Playbooks > New Signal Playbook. Set Name, Purpose, Approved source, Evidence window, Memory, and Signal instructions; create it, open Recurring, then choose frequency, channel, timezone, and Post automatically.
• Imports remain disabled until the recipient maps its own connectors, Meta account, channels, memory, learning, and exact resources, tests read-only behavior, and activates schedules one at a time.

Portable by design

• The official 2.0 archive includes all four Piece configurations, 16 playbooks, five proactive definitions, one Home-app workflow blueprint, four connector requirements, one Meta Ads plugin requirement, eight empty memory-folder guides and one fresh Learning Collection. Pieces import unpublished and schedules and workflows import disabled for destination setup.
• It contains no source tenant credentials, Meta account, campaign, audience, sender, contacts, memory contents, learning history, or advertising objects.
• Every destination reconnects its own providers, maps exact resources and channels, reviews memory, tests the Piece, and activates schedules one at a time.

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.

Chloe Employee Ops

The internal employee you talk to. She runs growth playbooks, reviews Meta and Lead360 evidence, prepares campaigns and automatically prepares the next approval card after a successful approval.

Chloe Front Desk

The website chat and booking Piece. It answers service questions, preserves chat through contact-form submission, offers available appointment times and supports payment-before-booking with staff handoff.

Chloe App Concierge

The Home-app role, equivalent to the existing Chloe 1.4 app Piece. The included Home-tag workflow waits one minute, notifies selected staff and starts Ask360 Conversation with this published Piece.

Chloe Lead Response

The customer reply Piece selected inside an approved campaign automation. It handles the approved opener, questions, service guidance and booking. The supplied configuration uses SMS; email requires its own reviewed publication and sender setup.

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 contacts, conversations, tags, opportunities, appointments, campaigns, openers, pipeline, purchases, revenue, and reporting evidence.

E-Commerce

Provides mapped services, offers, purchases, memberships, rewards, and customer activity for revenue-aware analysis.

Automation Pieces

Provides destination workflow context after the administrator maps and reviews the eligible workflow, waits, stops, sender, and owner.

Sites Builder AI

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

Plugins

Meta Ads

Provides live delivery, CTR, leads, CPL, campaign and ad evidence, plus governed PAUSED-ad creation only after the destination-owned account, permissions, and exact resources are connected.

Playbooks included for review

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

• Chloe Contact Follow Up
• Chloe Lead Briefing
• Chloe Meta Growth Daily Report
• Chloe Daily Lead Response Brief
• Chloe Weekly Meta To CRM Quality
• Chloe Weekly Creative And Opener Review
• Chloe Campaign Change Outcome Review
• Chloe Bookings Qualified Leads Sales Revenue
• Chloe Ad To Revenue Learning
• Chloe Catalogue Contact Rotation
• Chloe 72 Hour Campaign Opportunity
• Chloe Customer Growth Review
• Chloe Evening Commerce Pulse
• Chloe Growth Outcomes
• Chloe Five Day Tagged Lead Reactivation
• Chloe 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 8 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

• Chloe Growth Outcomes

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 four imported Pieces remain unpublished drafts 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.