Configure, test, and activate Chloe

Review the imported employee

Open the imported employee before enabling anything. Compare the profile with the import preview and resolve every warning. Confirm the employee belongs to the intended destination sub-account and has a clear internal owner.

• Review connector and plugin requirements without assuming a source connection exists.
• Review each generic playbook and remove any workflow the destination does not need.
• Review the disabled proactive schedule and choose the destination timezone, workdays, hours, interval, cooldown, and blackout dates.
• Keep channels unassigned until the Piece and destination memory pass testing.

Activate the four Chloe roles

Map the full intended service menu, calendar, commerce apps, memberships, intake forms, sender and handoff staff for each customer role. Publish each Piece and select its exact published generation in the destination widget or workflow.

1. Employee Ops: assign it to the internal Ask360 employee and select the Team Room channel.
2. Front Desk: select it in the website widget and connect the contact form and booking calendar.
3. App Concierge: open the imported Home-app blueprint, select the Home tag and notification recipient, choose this published Piece in Ask360 Conversation, then validate, publish and enable the workflow.
4. Lead Response: select it in Approved Workflow Pieces for campaign conversations. Configure SMS or a separate reviewed email publication and sender.

The archive includes SETUP.md and CHANGELOG.md. Existing installations keep their current published generations until their owner updates the relevant bindings. The release does not automatically replace other bots or workflows.

Map connectors, apps, and Meta Ads

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.

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.

• Connect the destination-owned provider account and confirm the signed-in administrator.
• Grant only the permissions needed for the approved workflow. Reporting requires an eligible read permission.
• Select exact advertising, app, campaign, site, form, commerce, calendar, and workflow resources instead of granting broad access.
• Keep effects read-only or draft while testing. Any supported live Meta or automation effect remains approval-gated.
• Current Meta safety defaults limit budget changes to 20 percent, cap a new campaign daily budget at 100 in the configured currency context, create supported new ads and retargeting campaigns paused, and expire approvals after 30 minutes.

Add destination memory and learning

1. Open Memory Brain and review the pending collection guides created by the import.
2. Upload only current destination-owned knowledge into the appropriate folders.
3. Remove credentials, payment data, private notes, unnecessary personal data, and unsupported claims before review.
4. Approve the exact revisions and make them available through the normal snapshot workflow.
5. Create or update a Memory Set when the Piece should use a controlled subset.
6. Open each imported Piece, bind its reviewed memory and intended Learning Collections, then save its new draft revision.

Validate and test in Arena

Validation checks the Piece contract. Arena testing checks how the draft behaves. Neither step proves that destination data, provider permissions, messages, prices, campaigns, or customer outcomes are correct.

• A daily Meta performance run with an exact destination account and the previous calendar-day window.
• A five-day dormant Mesosphere, Body Contouring, or Anti-Aging tag review that excludes new, booked, replied, opted-out, DND, purchased, active-conversation, previously enrolled, or duplicate contacts.
• A seven-day winner review that refuses to name a winner when evidence or attribution is insufficient.
• An approved winning-ad handoff that creates the ad PAUSED and refuses activation without a second approval.
• A revoked, suspended, unselectable, or missing Meta account that produces a truthful blocked result without guessing.

Review the answer, cited evidence, tool trace, blocked operations, handoff behavior, and resulting draft. Correct the Piece or destination mapping and repeat the test before publication.

Publish and activate deliberately

1. Publish all four reviewed Piece revisions and record their owners and intended roles.
2. Assign Employee Ops to the imported employee; select the exact customer Piece generation in its widget or workflow.
3. Choose the intended internal and customer channels for each role and verify their destination configuration.
4. Enable approved playbooks and schedules one at a time and verify their delivery destination.
5. Enable customer-facing channels, automations, app changes, campaign changes, or provider writes only after their separate consent, content, payment, and operational reviews pass.
6. Monitor early runs, approvals, errors, opt-outs, escalations, and business outcomes before expanding access.

Troubleshooting and safe removal

The archive fails validation

Download the official file again and compare its SHA-256 checksum. Do not edit the archive or change its internal files.

A connector or plugin needs review

The destination may not have the required provider, permission, feature, or resource. Connect an eligible destination account or disable the unneeded capability.

The Piece has no useful business context

This is expected until destination memory is reviewed, made available, bound to a new Piece revision, and tested.

A playbook or schedule does not run

Imported playbooks are generic and schedule blueprints remain disabled. Map resources, review the prompt and effect, choose an internal delivery channel, then enable the workflow deliberately.

Remove the imported kit

Disable channels, schedules, automations, and bindings first. Use the supported kit-removal action while the import ledger can still prove which draft resources were created. Later changes, shared use, publication, or run history can block automatic removal and require manual ownership review.