Wirebot Client Workspace Setup (Onboarding)

Wirebot Client Workspace Setup (Onboarding)

1. 01

   Sign up for the Wirebot Cloud plan at $7.99 USD per month and connect the client's Telegram, Slack, or Discord workspace

   Confirm the client's team holds an active ChatGPT plan with Codex access before provisioning, since Wirebot cannot execute coding tasks without it.

2. 02

   Provision the dedicated always-on server and map the persistent shell and disk to the client's project directory structure

   Wirebot Cloud advertises live setup in 60 seconds; the persistent environment is what keeps repos, dotfiles, and sessions alive between work sessions.

3. 03

   Create a dedicated chat channel per client for alerts and commands, then register the client's GitHub repository access so Wirebot can clone repos and manage pull requests

   Keep one channel per client so CI/CD alerts and suggested fixes do not cross between retainers.

4. 04

   Define the delegated task list for the pilot, such as porting a codebase or fixing CI failures, and encode client-specific command shortcuts in the bot

   Scope the first 30 days to two or three recurring task types so the client sees measurable output before expanding.

5. 05

   Verify repo and dotfile sync survives a restart by triggering a long-running build and confirming the session resumes

   The always-on server is meant to run builds and crons 24/7 without a laptop open, so test that path before handoff.

6. 06

   Confirm automatic updates, backups, and monitoring are active on the isolated box

   Wirebot Cloud includes zero-maintenance updates and backups; document the monitoring cadence in the client's runbook.

7. 07

   Deliver the handoff guide covering daily usage, session management, and escalation, then schedule the first weekly health check

   Agencies running the Wirebot Starter Dev Bot offer at $2,250 with 20 hours of setup should treat this handoff as the close of onboarding.