# Launch a client workspace

> The exact Super Admin checklist that turns a new Beam workspace into a verified client launch.

One source of truthThe full launch checklist is in Beam under Platform, Client launches. This page is the team playbook. A workspace is not called live until the recorded checks are complete.

## What the client needs to do

Explore first. Preview owners can open Inbox, Analytics, Grow, Screening, Assistant, Email, Numbers, Billing, and Settings. The sample conversation with Alex is a private practice exercise: Alex is fictional, no message leaves Beam, and no phone or customer is contacted. It lets you try a reply, team takeover, call handling, and booking before connecting a real number. Agencies also see Clients and their own agency branding. Live sending and paid services stay locked until the matching plan is active. Super Admin controls are never exposed to a client.

  - Choose the plan. Billing must be confirmed before sending can unlock.
  - Connect their CRM, if they use one. Choose the one client account during authorization.
  - Forward each public business line. The client line forwards to Beam's shared inbound gateway. The forwarding provider must preserve the number originally dialed.
  - Approve the assistant. The client owner reviews draft-mode behavior before live assistant sending is enabled.

## What the Beam team verifies

  1. Create the workspace and owner sign-inWhen an agency creates a client workspace, enter the client owner's real email. Beam does not send an invitation or reveal a reusable owner key. Give the client the normal Beam sign-in link; they enter that address and request their own six-digit code. An owner email belongs to one owner identity, so resolve an existing-account conflict instead of creating a second ambiguous sign-in.
  2. Confirm billing and line assignmentBeam shows the real payment state and active assigned lines. Do not mark this complete based on an expected plan or a pending number request.
  3. Assign the inbound receptionistEvery active Beam line needs its own approved inbound agent endpoint. Calls are never routed by guessing.
  4. Confirm forwardingCall each public client number from a separate phone. Confirm the shared gateway receives the original dialed-line identity and routes to the correct receptionist.
  5. Run the messaging testSend one inbound text. It must appear once in Beam. Send one intentional reply and confirm the recipient receives it once.
  6. Run the CRM test, when connectedSend one message from the CRM to Beam and one reply from Beam to the same CRM contact. Both directions must stay on the same record.
  7. Test the assistant and takeoverStart in draft mode. Verify business rules, calendar actions, and handoff behavior. A human reply must immediately pause the assistant for that conversation.
  8. Approve the launchOnly a Super Admin can approve a completed launch. The approval records who approved it and when. It does not replace the safety controls already enforced by billing and number assignment.

## When to stop

Do not approve a launch with a guessStop and mark the step blocked if a call does not reach the assigned agent, a message is duplicated or missing, a CRM record is unclear, or the assistant takes action without a confirmed result. Add the blocker to Client launches so the next operator has the real context.

## Client-facing next steps

After launch, the client uses the Inbox for conversations, Numbers to view their assigned lines, Settings for their connection status, and the Assistant page to review their business rules. Platform launch details remain visible only to Super Admin.