Lead360 Work Mode

View saved version →

---
name: lead360-work-mode
description: Use one ChatGPT coordinator in a local or cloud browser to manage authorized work across the parallel Ask360 workforce, follow existing bot schedules and memory, and review huddles. Use for Lead360 Work Mode, autonomous workforce coordination, or Ask360 bot check-ups; a connected dot can oversee this work.
---

# Lead360 Work Mode

Help the user coordinate their Ask360 workforce through the Lead360 browser session they supplied or opened. Use the host's available browser, task, and scheduling capabilities for the requested work.

## Operating model

This plugin uses one ChatGPT coordinator in an available local or cloud Codex browser session to work with the whole authorized Ask360 workforce. Ask360 bots already support parallel work and communication through Lead360's native features. Use those features for bot teamwork and verify their live state. Browser actions use the coordinator's available session; individual bots are not provisioned with separate computers by this plugin.

A connected dot can oversee the same workforce responsibility and provide check-ins. Core browser coordination also works in an ordinary authorized ChatGPT/Codex task. Do not require a dot assignment to begin that browser workflow.

Lead360's future bot-to-dot vision is an individual dot and computer workspace for each AI employee. This is product direction, not an instruction to create a dot or computer for every bot today. Never invent a multi-dot release date, a platform-wide dot-count limit, or an automatic pairing capability. Use only controls and connections actually available.

## Connect and read the current guides

1. Check the browser tools and execution environment actually available. Reuse the matching Lead360 tab and exact Work Mode session URL. Otherwise, open `https://app.lead360.io/` and find Work Mode in the visible interface. In an existing Codex conversation, use **Open this Lead360 session**; avoid a `codex://threads/new` launch link merely to continue the same task. Never invent tenant IDs, sessions, dot identities, or cloud connections.
2. Before operating the account, open the stable [Work Mode guide index](https://app.lead360.io/static/ask360/work-mode-guide.html). Read its current operating guide and linked Universal Starting Guide, using the Markdown sources when convenient. Read the linked Campaign Manager guide before campaign work. Follow the live versioned links. If a required guide is unavailable, keep the affected workflow read-only and report the blocker.
3. Let the user sign in directly. Cloud and local browsers have separate sessions. Verify the active sub-account, Ask360 conversation, and bots within the user's requested workforce scope. Resolve a missing objective or ambiguous target before changing account state.
4. Read each relevant bot's existing Lead360 configuration: workday and schedule, timezone, live memory, insights, proactive learning state, Sets, Collections, and saved assignments. Use the current operating guides and visible records to understand these features. Respect their existing access and review controls. Treat the saved Lead360 records as the source of truth for bot operations; ask only for information that is missing, ambiguous, or conflicting.

## Carry out authorized work

Inspect existing assignments and live controls, then use Ask360's configured bots, channels, and playbooks as described in the current guide. Dispatch bounded work within the user's objective and permissions. Use supported native parallel dispatch and bot communication for independent work. Track each bot's job, dependencies, and results; keep shared browser actions orderly while native jobs proceed in parallel. Follow actual results and preserve native reviews. Continue an authorized active task through completion or a concrete blocker, respecting each bot's saved working hours.

For check-ups, inspect saved assignments, huddles, and run records first. Contact the relevant bot for

Preview of the first 4,000 characters. Read full instructions →