Set up and hand over a client company in 6am

Outcome and responsibility

A clearly identified company in 6am, with its business profile, data structure, pipelines and access checked against the client’s agreed plan. The onboarding owner coordinates the work; each administrator performs only the actions they are allowed to perform. The client’s responsible person accepts the handoff and any outstanding items.

This procedure connects SOPs 003 through 007. It does not copy another client’s configuration or automatically set up channels, forms, calendars, imports, campaigns or billing.

Before you start

Prepare an approved brief containing:

• The existing company or the need to create one, its existing responsible user and authorized business details.
• Business timezone and default language for new lead forms. Interface language is a separate choice.
• Contact and opportunity field plans: object, key, name, type, group and choices. Reuse standard fields when sufficient.
• Required pipelines, ordered stages and the destination of each contact list. A list is not a pipeline; each deal is an opportunity.
• An access matrix: person/email, approved companies, role, permitted activities and approval. One login may have different roles in different companies.
• Handoff criteria, owners, deadline and the internal location for evidence. Do not include passwords or tokens.

01. Select the company and open onboarding

1. Sign in to the 6am dashboard. Check the company selector before making changes. Look for an existing company to avoid duplicates.
2. If a new company is required, follow SOP 003. A platform administrator selects the correct existing responsible user, who receives administrator access to that company. Do not use an unrelated user as a temporary substitute.
3. Open Client onboarding in the company sidebar. Members with at least one relevant company-settings, CRM or access-management permission can use this overview. Each section shows its data and link only when the corresponding permission is available.
4. Check the company name in the heading. An unavailable section needs an authorized administrator’s review; it does not mean that configuration is empty.
5. Use Refresh overview after returning from configuration pages. The page reads current data but does not save a checklist, approval, completion percentage or client acceptance. Existing records alone do not prove a correct setup.

02. Review the business profile

Use Review company settings and follow SOP 003. Save and reopen the approved details. Keep business contact, login and billing information separate.

The onboarding overview reports whether a profile is saved and shows the explicitly saved timezone and language. Not saved requires review: do not treat an application default as the client’s approved choice. A saved profile may have empty optional fields and must still be compared with the brief.

Changing defaults does not translate or reschedule existing items, connect an email inbox or activate communication channels.

03. Configure the required fields

Open Review custom fields and follow SOP 004. Check object, key, type, group and choices before creating a definition. Person-level information belongs to the contact; deal-specific information belongs to the opportunity.

The overview counts only active definitions, separately for contacts and opportunities. Zero can be correct when standard fields meet the brief. Archived definitions still exist and must be reviewed before creating replacements.

Validate using authorized synthetic records: save, reopen and compare values; include zero, No and empty values when applicable. Types, keys and choices cannot be freely changed after creation. Do not import real customer data simply to prove the basic setup.

04. Organize pipelines and destinations

Open Review pipelines and follow SOP 005. Create only the required processes and check stage order against the agreed plan. Reopen each pipeline after saving. The overview shows active pipelines and their stages, with a warning if an active pipeline has no stages.

When different lists should feed different pipelines, check each list’s destination and starting stage using SOP 088. Creating a pipeline does not configure routing or move existing opportunities. For stage cadences and advancement criteria, use SOP 106 when included in the approved scope.

Test the path with a synthetic opportunity and confirm pipeline, stage, owner and next action. Do not activate live sending or automation to test a configuration that can be checked without a message.

05. Review members and invitations

1. Open Review company members. Compare people and roles against the approved matrix; the count includes existing members and does not prove client access.
2. For a new membership, follow SOP 006. Open Review invitations before creating another: pending and unexpired does not mean delivered or accepted. Creating an invitation sends email; confirm recipients and authorization first.
3. The recipient signs in with the invited email address, verifies the account and accepts a valid invitation. Confirm membership after acceptance. An invitation record alone does not complete onboarding.
4. For separate roles across companies, role changes or removal, follow SOP 007. Preserve an administrator and verify that other company memberships remain intact.
5. Test a permitted and a prohibited action using a controlled account. User does not grant CRM access by default; Admin is broad. Use an approved custom role where needed. Choosing these roles does not provide assigned-record-only visibility.

06. Prove the handoff

Use Before handing over to the client as the review guide. Reopen the actual configuration pages; do not rely only on overview counts.

Complete the handoff only when applicable items match the brief and outstanding items are explicitly agreed. Record a reason for anything not applicable. If permission, information or a product capability is missing, record the blocker and its owner; do not infer approval.

Limits and next phase

The onboarding page is a read-only overview and navigation guide. It does not create companies, grant access, send messages or keep a completion record. Store handoff evidence in the authorized internal record.

Calendars, channels, published forms, imports, campaigns, SSO and record-level permissions are not activated by this procedure. Agree the next phase separately. Synthetic examples do not prove delivery to a real email recipient or operation of an integration that has not been configured.