Workspace launch checklist

For

Company admins and customer owners

Owner

Customer operations

Outcome

Launch the workspace with approved ownership, data, connections, recovery, and support paths.

Last verified

2026-08-30

Next review

2026-11-28

Status

supported

Customer journey

Launch a workspace

Estimated time

20 min

Permissions and roles

Company admin · Customer owner

Open the completion checklistSteps, proof, and recoveryClose checklist

Prerequisites

• The approved customer workflow
• Company admin access
• Named business, technical, data, and support owners

Permissions in practice

• Company admin: configure workspace, data, roles, and providers.
• Customer owner: approve the workflow, limits, launch date, and rollback decision.

Steps

• Confirm the company, time zone, roles, owners, support contact, and approved launch scope.
• Test one synthetic lead through person, account, deal, pipeline stage, and next task.
• Test each import mapping, provider connection, monitoring view, and fallback path.
• Run the frontline acceptance journey and record one allowed and one denied role action.
• Record the approver, accepted limits, launch window, support path, and rollback decision.
• Enable real intake or provider work only after all required checks pass.

Success proof

• The customer owner can point to the first useful record, deal, owner, and next action.
• Each active dependency has a health check, recovery owner, and fallback path.
• The launch decision records its proof level and does not rely on a saved setting alone.

Common failures

• A user has too much or too little access for the job.
• A mapping, provider health check, or fallback path is missing.
• The team treats local or synthetic proof as live customer proof.

Recovery

• Pause the affected intake, send, call, or automation path and keep failed work visible.
• Correct one dependency at a time, retest with synthetic data, and record the result.

Rollback

• Disable newly enabled intake or provider work before changing data or ownership.
• Restore the previous approved configuration and keep the launch evidence for review.

Next task

Run the controlled customer-data import.

Open next guide

Use this checklist after the first-value journey and before real customer intake or communication. Complete each check in the customer workspace that will go live.

Confirm people and ownership

• Confirm the company name, time zone, business owner, company admin, and support contact.
• Invite only approved users and verify one allowed and one denied action for each role.
• Assign owners for unassigned customer records, deals, tasks, and failed work.

Confirm CRM and data

1. Approve the person fields, customer sources, pipeline stages, deal rules, and task conventions.
2. Test one synthetic customer from creation through deal and next task.
3. Test the import mapping and duplicate policy before the full import.
4. Verify the approved export and retention path.

Confirm connections and recovery

• Complete the provider-specific guide for every active connection.
• Confirm credentials, health, provider limits, monitoring, rotation, and disconnect ownership.
• Test failure handling without real customer sends or calls where possible.
• Record the fallback path for lead intake, email, WhatsApp, calling, and automation.

Approve launch

1. Run the admin and frontline-user acceptance journeys.
2. Confirm support contacts, known limits, incident communication, and the change window.
3. Record the approver, accepted limits, launch date, and rollback decision.
4. Enable real intake or provider work only after every required check is complete.

A local test or saved provider setting is not production proof. Record the exact proof level for each check.