Your clients should experience the service as yours. White-label covers the surfaces they actually touch: the portal they sign into, the reports they receive, and the person they contact when something is wrong. It is included on every deployment (managed cloud, in-Kingdom hosted and on-premise) at no additional charge.

​
What your clients see

A portal under your brand

Your name, logo, and colours on the client-facing console, so the workspace reads as your product.

Reports from you

Call volumes, outcomes, and summaries presented as your reporting rather than a third party’s export.

Support through you

Your team is the client’s first line. Voho supports you, not your clients, unless you agree otherwise.

Your commercial relationship

You contract with your client, set the price, and issue the invoice. See Commercial model.
The exact branding scope is agreed per partner engagement. Confirm which surfaces are covered before you show a client a mockup, that conversation is cheap early and expensive after a pitch.

​
What stays shared

Some things are the platform, not the skin on it. Being straight with clients about this avoids a bad conversation later:
  • Voice and dialect behaviour is the same platform capability across every partner. See Voices.
  • Capacity is drawn from the deployment you and Voho sized together, and one client’s peak affects the pool your other clients draw from.
  • Release timing follows the platform, not each client’s change window, on the managed service. An on-premise deployment gives you control of that.

​
Isolation between clients

Each client workspace is separate: agents, numbers, call records, transcripts, and users. One client cannot see another’s calls, and a user belongs to the workspace you put them in. Your agency team is the exception by design, administrative access spans your clients so you can operate the estate. Decide deliberately who on your team holds it.
You are handling your clients’ customer conversations, which makes you a processor in your own right. Your contracts with your clients need to say what is retained, for how long, and where it is processed, and those answers have to match what you have agreed with Voho. See Security and data handling.

​
Before you put your name on it

Agree the branding scope

Which surfaces carry your brand, in writing, before it is in a pitch deck.

Settle data handling

Retention, processing location, and what happens at contract end: for your clients, not just for you.

Define the support path

What your client can raise with you, what you escalate, and the response times each side commits to.

Fix the billing model

Whether Voho bills you or your clients, and how usage is reconciled against what you invoice.

Talk to us about a partner arrangement

Start with Agencies and resellers for what to bring.