Download and install the Chloe kit

Download the official file

Use the official lead360.io file below. Do not rename the extension, open and re-save the archive, or use a file received from an unverified source.

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.

Verify the file before upload

The checksum confirms that the downloaded bytes match the published public kit. A mismatch means the file is incomplete, altered, or not the current release.

Windows PowerShell

Get-FileHash .\chloe.ask360 -Algorithm SHA256

macOS or Linux

shasum -a 256 chloe.ask360

The result must be c929da33c7b11963937e1e0237050769eca453f6ac41532c4a94e6103fbece1c. The separate checksum file is available from the download details.

Upload from the Ask360s area

The kit upload is beside the Ask360s heading, not inside Piece Studio, Memory Brain, Plugins, or Automation Pieces.

Confirm the destination and administrator

Before selecting the file, confirm that the correct Lead360 sub-account is open and that you have permission to create an Ask360 employee. Record who will own the imported employee, review its data access, approve its Piece, and respond when testing reveals a problem.

1. Sign in to Lead360 and choose the exact destination sub-account.
2. Open Dashboard, enter the Ask360 workspace, and select the Ask360s tab.
3. Select the upload icon beside the Ask360s heading.
4. Choose chloe.ask360 and wait for the preview to finish.
5. Review the kit name, suggested employee name, four-Piece count, memory mode, and resource counts.
6. Confirm the import. Lead360 creates a new employee and review-state resources without activating channels, schedules, automations, or source connections.

Understand the import preview

The preview should identify Chloe, structure-only memory, four draft Pieces, 16 playbooks, 8 memory folder guides, 4 connector requirements, and 1 plugin requirement.

• Cancel when the kit name, memory mode, Piece state or count, or resource counts differ from this page.
• Import creates a new employee with a unique destination name. It does not replace an existing bot.
• Memory guides start pending, Learning Collections start without observations, and all four Pieces start as unpublished drafts.
• Schedules and automations remain disabled, and channels and provider accounts are not inherited.

Complete setup after import

1. Open the new employee and review its connectors, plugins, effect policies, playbooks, learning definitions, schedule blueprint, and warnings.
2. Connect only destination-owned providers and choose exact resources.
3. Upload and review destination knowledge, make it available, and bind it to the appropriate Piece revisions.
4. Validate and test each Piece in Arena with allowed, disallowed, missing-data, and failure scenarios.
5. Publish each approved revision. Assign Employee Ops to the internal employee, Front Desk to webchat, App Concierge to the Home workflow and Lead Response to approved campaign automations.
6. Enable schedules, automations, customer channels, or provider writes one at a time after their owners approve them.