Planning workspace onboarding and troubleshooting

1. Sign in, create a workspace and confirm your role

Open your workspace and choose Sign in with ChatGPT. Complete authentication only through the identity provider. Create a workspace with a recognizable business name.

Permissions differ by action; do not treat administrator access as owner access. If a control is missing, confirm your current role instead of trying another tenant or account.

2. Check connection availability before setup

Open Integration availability before following any provider instructions. The current release has no customer-ready email, CRM, calendar, accounting, payment or model connection flow. There is no valid destination for an API key.

Do not create credentials for this preview or paste secrets into briefs, policies, evidence references, contact forms or support requests. When a provider is introduced later, its guide must name the exact provider, authorized account, requested scopes, test tenant, disconnect method and evidence of a successful read/write before a connection can be considered ready.

3. Select and configure the planning worker

1. Select Sales & Booking, Customer Care or Quote-to-Payment in the onboarding panel. Selection does not activate execution.
2. Approve business settings with services, pricing boundaries, communication tone, escalation reference and business hours in an explicit IANA timezone.
3. Add only approved knowledge and link it to the correct client and project. Pending, stale, conflicting or cross-project knowledge must not be treated as current.
4. Set worker permissions and action limits. Missing permission or an expired approval must stop the proposed action.

Each successful policy change creates a new version. If another editor saved first, reload, compare the current version and review it again. Never retry a stale approval unchanged.

4. Save, check and approve the exact work

1. Save a draft brief. A stored draft confirms storage only.
2. Queue and run a format check. A pass confirms supported worker and brief limits; it is not an AI result or completed customer work.
3. Review the exact brief and current business-policy version in the Planning approval queue. Changes or expiry require a new decision.
4. If an external action is ever staged, review its exact connector, operation, scope and argument digest in the External action approval queue. Approval records permission only; it does not execute the action.
5. Use task history and activity records to inspect what the system actually stored. Do not infer delivery, payment, booking, customer satisfaction or revenue from an internal status.

5. Recover without duplicating or overstating work

• Save conflict: preserve entered text, reload the current record, compare versions and submit a new deliberate decision.
• Failed or unavailable check: keep the draft. Review the bounded failure reason. Retry only when the displayed state is eligible; a running lease must expire before another claim.
• Ambiguous external result: do not replay it. Reconcile the provider result with the stable action ID first. No provider is connected today.
• Workspace pause: pause new checks and cancel pending or running checks from Workspace controls. Completed history and saved drafts remain.
• Removed assignee: reassign the retained request to a current member. A prior acknowledgement is cleared on reassignment, and the new assignee must acknowledge.

Use the support page for the current self-service routes and contact limits. The contact form stores a request for review; it does not send email or establish an emergency channel.

6. Review internal support requests truthfully

The Internal support request queue retains verified requests. Valid current service coverage can assign the primary responder and calculate a first-response target across staffed minutes. Missing or invalid coverage leaves the request visible as needs assignment.

Only the assigned current member can acknowledge. Owners and administrators can assign, escalate to the policy backup and record an internal resolution. These records do not prove an external inbox received a message or that a customer received a response. Do not advertise staffed hours or response targets until a real owner approves current responders and coverage.

The Customer service action ledger binds scheduling, asset collection and status-update proposals to an exact active requester grant, route, client, project, privileged owner, approved policy and argument digest. Approving a staged record does not execute it. Only an exact trusted provider receipt can create provider-confirmed evidence; ambiguous outcomes remain non-replayable. No customer-service provider or API-key destination is configured in this preview.

7. Pause, export, remove data and cancel safely

1. Pause the workspace and cancel pending checks before offboarding.
2. Owners and administrators can download the workspace export. Store it privately.
3. Use Manage early-access signup or Manage a contact request with the private removal code saved when the record was created. Each route removes only that record.
4. Workspace deletion is owner-only and requires the exact displayed confirmation. Requesting deletion pauses new checks and cancels queued or running checks. Cancelling the deletion request does not resume the workspace.
5. Completed workspace deletion does not delete the ChatGPT identity or data in third-party providers. No paid Laborbot subscription or connected provider exists to cancel today.

Troubleshooting table

What still requires real launch evidence

Customer tool connections, real AI execution, external message delivery, paid checkout, provider cancellation, staffed support, incident delivery and customer validation are not established by this guide. Those items remain open until authorized accounts, real operators and observed end-to-end rehearsals exist.