# White-label, per client. Never pooled.

URL: https://callhush.com/for/agencies
Last updated: 2026-10-28

We work your clients' webinar registrant lists with texts and calls, sold white-label. Your clients never see our name, permission is captured in each client's own name rather than pooled under yours, every client runs on their own number, and one client's data can be exported or deleted without touching the rest of your book.

**We work your clients' webinar registrant lists with texts and calls, to lift their show-up rate and their post-webinar sales.** Sold white-label, that means two separate things and only one of them is about branding. The branding half is straightforward: client-facing, our name does not appear: not in a caller ID, not in a message footer, not on a report. The half that decides whether you can actually resell this is that the things which must not be pooled are not pooled: permission is captured in each client's own name, each client runs on their own number, and one client's data can be exported or deleted without touching the rest of your book.

## Whose name is the permission captured in: mine, yours, or my client's?

Your client's. This is the question an agency should be asking first, and it has one correct answer: permission runs to the specific business named on the form. Someone who agreed to hear from Coach A has not agreed to hear from your agency, and has not agreed to hear from Coach B.

So a vendor who registers your whole book under your agency because it is less paperwork for them has quietly made you the named party for tens of thousands of people who have never heard of you. That is not a technicality you can paper over in an MSA later. It is the reason the whole arrangement has to be built per client from the first day.

> **What we do not answer on this page:** Who ends up named as a defendant, and what an indemnity clause between an agency, a vendor and a client should say, are real questions and they deserve better than a paragraph on a sales page. They have their own page: [who is liable](https://callhush.com/compliance/who-is-liable). What your clients' registration forms need to say is on [what your opt-in form must say](https://callhush.com/compliance/what-your-opt-in-form-must-say).

- **Per client**: Whose name permission is captured in. Consent runs to the named business and can never be pooled across your book
- **10 business days**: The window to honour a revocation: which means one opt-out ledger across everything we run, not one per client (Source: [47 CFR 64.1200](https://www.law.cornell.edu/cfr/text/47/64.1200))
- **8:00am–9:00pm**: Calling hours, in the recipient's local time: a rule that binds regardless of what anyone consented to (Source: [47 CFR 64.1200](https://www.law.cornell.edu/cfr/text/47/64.1200))

## What has to be per client, and what should an agency refuse to let anyone pool?

Seven things. Every one of them is cheap to get right at setup and expensive to unpick once a book of clients is live, which is why this table exists rather than a paragraph of reassurance.

*Pooled across your book vs isolated per client*

|  | Pooled, refuse this | Per client, how we build it |
| --- | --- | --- |
| Whose name permission is captured in | Your agency, once, covering everybody | Each client's own business, on their own form |
| The number calls and texts come from | One shared pool covering every client | One per client, in their own area code |
| Transcripts and recordings | One store, no way to separate them | Siloed, exportable and deletable one client at a time |
| An opt-out | Honoured only inside the campaign it arrived in | Honoured everywhere we operate, and that client's list leaves with them |
| Branding your client sees | A vendor name in a footer, a caller ID or a report | Yours or none: with the responsible business still named on the call, as required |
| Switching it off | A support ticket to somebody else's queue | Yours, per client, without asking us |
| Adding your next client | A fresh custom build every time | The same setup shape as the ones before it: and a fair thing to make us prove in a pilot |

The kill switch is the row people test hardest, and rightly. How it works, what the assistant is allowed to say before anyone reaches for it, and the script-approval process that sits in front of the whole thing are on [what it says](https://callhush.com/what-it-says).

## Does my client ever see your name?

No. There is one exception and it is not a branding decision: every call carries an identification of the business responsible for placing it, stated at the start. [47 CFR 64.1200(b)(1)](https://www.law.cornell.edu/cfr/text/47/64.1200) requires the caller to “state clearly the identity of the business, individual, or other entity that is responsible for initiating the call” at the beginning of the message.

On a white-label deployment that name is your client's, which is the right answer anyway: the registrant signed up for your client's webinar and would be confused to hear anyone else. The assistant also says that it is an assistant. That is settled, it is not a concession, and it is published word for word rather than described.

> **Why disclosure helps you resell it:** Across the whole AI-calling advertising market, our own Meta Ad Library sweep in July 2026 found exactly one advertiser claiming compliance as a selling point. Being the agency whose vendor discloses, honours the hours and honours the opt-outs is a differentiated position with your clients, not a weakness to manage around.

- **~470**: Active US ads pairing “free training” with an agency-owner audience at capture (CallHush Meta Ad Library sweep, 2026-07)
- **~8,400**: Same sweep, coach audience: the client type most of these funnels serve, and the largest niche by roughly 5×
- **~55**: Ads mentioning “webinar show-up rate” found globally, all statuses, all of history. Nobody is selling this to your clients yet

## What happens when one of my clients leaves me?

Their data comes out and their suppression list goes with them. Transcripts, recordings and opt-outs for that client can be exported and then deleted without touching your other clients, and the list of people who asked not to be contacted travels to whoever runs their marketing next.

That last part is the one agencies get burned on. If a client walks away and then texts somebody who had already opted out, the audit trail still runs through the arrangement you set up. A suppression list that stays behind with the vendor is not a retention feature, it is a liability you left in someone else's account.

> **The number question, answered narrowly:** Each client runs on their own number rather than a shared pool. Who owns a number, and what happens to it at the end of a contract, is a term to settle in writing before the first message sends: the general answer for a single operator is on [the sequence](https://callhush.com/the-sequence), and the multi-client version is a first-call conversation.

## What should I insist on before I put any vendor in front of a client's list?

1. **Make them say whose name the permission is in**: Ask it first and listen for a straight answer. If a vendor wants to register your whole book under your agency, they are moving their paperwork onto your name. The correct answer is each client's own business, captured on that client's own form.
2. **Get per-client numbers, in the client's area code**: A shared pool means every angry callback and every 'stop texting me' lands with you, and it means one client's volume can damage an asset that belongs to a different client.
3. **Confirm you can export and delete one client at a time**: Ask specifically whether you can pull one client's transcripts, recordings and opt-outs out and delete them without touching the others. Ask what happens to all of it if the vendor is acquired or folds.
4. **Check that the suppression list travels**: When a client leaves you, the list of people who asked not to be contacted has to leave with them. Confirm it in writing rather than assuming it, because it is the cheapest thing for a vendor to quietly keep.
5. **Hold the off switch yourself**: You should be able to stop everything for one client without opening a ticket in somebody else's queue. Ask to see it, on screen, before you sign anything. A vendor who hesitates on that question has answered it.

We would rather you ran that list against us than against nobody. It also happens to be the list we built the arrangement around, which is a claim worth testing rather than believing.

## Do I buy this per client, or once?

Once at the agency level, then per client after that. Setup is an agency-level event rather than something repeated once per client, because every client after the first is largely the same work as the first and both of us know it. Per-client capacity is bought at a rate you mark up and resell under your own name.

Usage is stated separately and up front rather than discovered in month two. What we will not do is print a number on a web page: not the agency setup, not the per-client rate, not the multiple you resell at. You get all three on the first call, without us asking to see your clients' ad spend first. The reasoning is on [how pricing works](https://callhush.com/pricing).

> **Start with one client, not your whole book:** Pick the client who will tell you straight rather than quietly resent it. One funnel, one cycle, their brand and their number, and the expansion terms for the rest of your book agreed before the test rather than after it. That is the only sequence in which a good result is worth anything to you.

The three things agencies usually check next are the wording, the liability and the platform coverage. The wording is on [what it says](https://callhush.com/what-it-says), the liability question is on [who is liable](https://callhush.com/compliance/who-is-liable), and the honest platform-by-platform answer is on the [platform pages](https://callhush.com/platforms). If one of your clients runs a continuously-running funnel rather than a scheduled one, the fit argument for that shape is on [the course-creator page](https://callhush.com/for/course-creators). When you are ready to test it on one client, [book a call](https://ainora.lt/contact?from=callhush).

## Frequently asked questions

### Can I put my own logo on it, or no logo at all?

Either. Client-facing, our name is absent by default - not in a caller ID, not in a message footer, not on a report, not on an invoice line. What is never absent is the name of the business responsible for the call, because that is a legal requirement rather than a branding choice, and on a white-label deployment that name is your client's.

### People search for “ai sdr white label pricing agency margin”. Why is there no price on this page?

Because we do not publish one anywhere, for anybody. What we will say in public is the shape: agency-level setup happens once rather than once per client, per-client capacity is bought at a rate you mark up, and usage is stated separately so it is never a surprise in month two. The numbers come on the first call, in the sentence after you ask.

### Is one client's list ever used to reach another client's audience?

No, and it could not be. Consent runs to the specific business named on the form, so a registrant who agreed to hear from one of your clients has not agreed to hear from you or from another of your clients. Pooling them would not be a policy failure, it would be the thing that creates the exposure you came here worried about.

### Will you sign something that stops you approaching my clients directly?

It is a fair thing to ask for, so raise it on the first call and get the answer in writing. We would rather negotiate it before you introduce us to your clients than after.

### Can you show me results from other agencies?

Not on this site. No client names, logos or testimonials are published on this site, there is no results dashboard, and we are not going to invent any of those for a segment whose whole job is spotting invented proof. That is why the first thing on offer is one client, one funnel, and a split test on that client's own registrant list.

### My clients are on Zoom, WebinarJam and EverWebinar. Does this work on all three?

The parts that matter most work on all of them, because they run off registration data and our own timer rather than off the webinar platform. What differs is how much of the live session we can see, and that answer varies enough to get its own compatibility matrix.

---

CallHush is operated by AINORA, MB (Vilnius, Lithuania). Book a call: https://ainora.lt/contact?from=callhush