What to look for in a white-label CRM

Decide what the CRM is for

Agencies use a white-label CRM for two different jobs, and many products are better at one than the other. The first is running your own agency: leads, pipeline, proposals and invoices. The second is giving each client a branded system for their own leads, bookings and messages, sold as part of the retainer.

Write down which job matters more for the next twelve months. If clients will log in every day, ease of use and support carry the most weight. If the CRM mainly serves your team, depth of pipeline and reporting matters more.

Write down which job matters more for the next twelve months.

How deep does the white label go?

“White label” can mean anything from a logo in the corner to a product the client never connects with the vendor. Check each place a client might see the vendor’s name, and ask which of them are available today and which are on a roadmap.

• Login page and app on your own domain or subdomain
• Your logo, colors and favicon throughout the dashboard
• Emails to clients and their customers sent from your domain
• Reports and PDFs with your branding only
• Mobile app under your name, or at least without the vendor’s
• Help articles and support messages that do not reveal the vendor
• Invoices to clients issued by your agency, not by the vendor

Client accounts and permissions

Each client should have its own account, with its own contacts, pipeline and settings, so data never mixes between clients. Your team should be able to switch between client accounts from one login, and each client should only see its own data.

Test the permission model with a real scenario: a client’s office manager should be able to work leads but not delete the account or export every contact; your contractor should see two clients but not the rest. If the system only knows “admin” and “user”, that will become a problem as you grow.

• Separate account per client or per location
• Agency-level login with access to all or selected client accounts
• Roles for client staff with limits on export and deletion
• Audit log of who changed what
• Templates you can copy into new client accounts

Email and SMS sending

A CRM that sends email and texts on behalf of your clients puts deliverability in your hands. Gmail’s sender guidelines require SPF or DKIM for all senders and ask that spam rates stay below 0.3%. Senders of more than 5,000 messages a day to Gmail also need DMARC and one-click unsubscribe for marketing messages. Check that the CRM supports authentication on each client’s own domain, not only on a shared one.

Texting is regulated more tightly than email. Messaging providers such as Twilio state that anyone sending texts from an application to US numbers over a standard 10-digit number must register for A2P 10DLC, with a brand and a campaign. Marketing texts also need the recipient’s consent. Ask the vendor how registration works for each client, who pays for it, how long it takes, and how opt-outs such as “STOP” are handled. When in doubt about consent rules for a specific use, ask counsel.

Texting is regulated more tightly than email.

Data ownership and leaving

Your clients’ contacts and history are their data, and your agency is responsible for them. Before you sign, find out how to get everything out again.

• Full export of contacts, deals, notes and messages in a standard format
• Export per client account, not only for the whole agency
• What happens to data after you cancel, and for how long
• Where data is stored and who at the vendor can access it
• A data processing agreement if you serve clients with privacy obligations

Price it at your future size

White-label CRMs are priced in different ways: a flat fee for unlimited client accounts, a fee per client account or location, a fee per user, or add-ons for features such as white-label apps, phone numbers and email volume. The model that is cheapest at five clients is often not the cheapest at fifty.

For example, compare a flat $300 a month with $30 per client account. At five clients the flat fee costs more; at ten they are equal; at twenty the per-account model costs $600. Then add usage costs such as SMS segments, phone minutes and email sends, which many platforms charge separately. Ask for a written quote at your expected size a year from now.

Our own partner model is a monthly membership plus a fee per client location; the pricing page lists what each tier includes and the current numbers. Whatever you choose, compare total cost per client, not the headline price.

The model that is cheapest at five clients is often not the cheapest at fifty.

Support, reliability and who answers the phone

With a white-label CRM, your clients call you when something breaks, not the vendor. Find out exactly how fast the vendor answers your agency, through which channels, and whether there is a way to escalate an outage.

Ask for the vendor’s status page and its history of incidents, how updates are announced, and whether features are removed or changed without notice. A change in the interface that you learn about from a client is a support problem with your name on it.

• Support channels and response times for agencies
• Status page and incident history
• Release notes and notice before changes clients will see
• Sandbox or test account for training your team
• Documentation you can rebrand or rewrite for clients

Run a two-week trial with one real client

Demos show the best path through the product. A trial with one friendly client shows the rest. Pick a client with a moderate amount of data and a patient owner, and tell them what you are testing.

• Day 1–2: import contacts and pipeline; check what was lost
• Day 3–4: set up the branded login, domain and sending authentication
• Day 5–7: run the client’s real lead flow: form, call, follow-up, booking
• Day 8–10: send one email campaign and one text sequence with opt-outs
• Day 11–12: open a support ticket with a real problem; time the answer
• Day 13–14: export everything and check it opens correctly elsewhere

Questions