Chloe Ask360 kit overview

What the Chloe kit is

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.

Designed for a destination sub-account

The package is a reusable starting point for Meta Ads performance, tagged-lead reactivation, and winning-ad operations. It creates a new Ask360 employee and four unpublished Pieces 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

Chloe has five proactive playbooks. Three featured Meta Expert schedules cover the daily report, five-day reactivation, and seven-day winning-ad review. Catalogue Contact Rotation runs Mondays at 9:00 AM, and Ad-to-Revenue Learning runs daily at 9:00 AM. Each due playbook posts separately; all customer and Meta changes remain approval-gated.

How Chloe helps

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

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

Pieces and channels

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.

What the public package includes

The public package includes one internal channel requirement, 4 connector requirements, 1 plugin requirement, 16 generic playbooks, 1 fresh Learning Collection definition, 8 reusable memory folders, proactive schedule settings that import disabled, one disabled Home-app workflow blueprint, and four unpublished 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 Chloe kit

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