White-Label CRM Launch Checklist for Agencies

What should an agency check before launching a white-label CRM?

Verify the brand and sign-in domain, client account access, communication providers, support ownership and one complete customer workflow. In Chirply, start with White-label branding and domain settings, then pilot a client account with the intended user role. A successful launch includes the client's ability to sign in, complete work and get help.

Define the service your client will receive

Choose one client profile and the work your service will help them complete. For a local-service client, that could be receiving an inquiry, assigning a follow-up and tracking an appointment. For an agency team, it may be moving a new client from agreement into onboarding. Use that journey to decide which screens and integrations the pilot needs.

Write a responsibility sheet before inviting clients. Name the person who handles onboarding, the person who manages provider connections, the contact for billing questions and the support route. State your own service terms clearly and check the current Chirply plan and White-Label Partner entitlement for the capabilities you intend to offer.

A practical pilot starts with one account and one operator. Give that operator a short acceptance checklist and observe the complete journey. Their ability to finish the work is more useful launch evidence than a branding preview alone.

Apply the brand and verify the destination

Use the agency account that owns the white-label setup and an authorized administrator. The White-label screen shows the available configuration or the required entitlement.

1. Open White-label and find the Brand card. Set Display name and review Logo, Favicon, Sign-in page image, Primary color and Accent color.
2. Choose Save branding after reviewing the fields. An uploaded image still needs the branding save to apply it. Reopen the page to confirm the saved settings.
3. Find Custom domains and configure the intended app hostname. Follow the displayed DNS instructions for that exact hostname and wait for domain and SSL readiness. Manage all domains opens the wider domain directory when needed.
4. Open the actual sign-in URL and check its title, logo, favicon and mobile appearance. Test using the intended client role and a separate sign-in session so an administrator's broader access does not substitute for the client's experience.
5. Review the client account's team, provider connections and support route. Document how the agency requests or receives access to help; client access governance is part of the service arrangement.
6. Complete one inquiry-to-follow-up pilot in the client account. Verify the contact, owner, next task and any agreed communication. Record the result before onboarding the next client.

Give each operational handoff an owner

An illustrative launch sheet has five rows: brand owner, domain administrator, communication-provider owner, client operator and support owner. One person may fill several roles, but every row should identify who acts when something needs attention.

For calling and SMS, identify which connected provider account supplies the numbers and usage. For email, identify the sending domain and the person maintaining its records. Test the sender identity the customer will actually see. Your service description should explain the responsibilities that the client needs to carry out.

Agree how your agency enters a client account for support. Chirply's client-access governance can affect whether an agency can enter immediately or needs approval. Verify the arrangement with the client and keep support instructions aligned with it.

Choose a repeatable onboarding record: the client's sign-in URL, account name, approved team roles, required connections, completed tests and support contact. Keep credentials in the appropriate secure connection controls; the handoff document should describe ownership and status.

Run the launch acceptance check

Open the branded destination on desktop and phone. Sign in with the pilot role, locate the intended client account and complete the agreed task. Confirm the operator can reach the features in your service and understands where to ask for help.

If the domain is pending, compare the configured DNS record with the exact instructions shown and check domain and SSL status. If branding appears unchanged, confirm Save branding completed and reopen the actual client destination. If a client cannot see a feature, review its plan access and team role before changing configuration.

After the pilot, give the client the completed handoff record and a first task they can repeat. Record any remaining configuration as an assigned item with a clear completion check. Reuse the verified process as the basis of your next onboarding.

Common questions