Q: Dashboard visibility for agencies & other Qs
Hi Sohaib ,
1) As an agency, can I see conversion data across all client sub-accounts in one dashboard?
2)On a Q on Meta's Oct'26 proposed pricing changes to be "per message basis", you said " yet to hear from twilio ". Can you proactively let know the impact on our business model & mitigation plans
3) on BYOK, do we have flexibility to (a) allow each client to BYOK (b) Use centralized API key & passing on the cost to client (c) Use your max plan (buying credits) & allocating them to each client once & it auto debits us every month & auto allocates to clients, including monthly changes.
4)can you explain on the phone number ? should clients buy Phone numbers from us through you with a markup /passthrough ? Do we need to do KYC for clients or twilio does ? pls list KYC compliance risk if any ?
5)will you be in appsumo for another month ?
sohaib.dmchamp
Jul 22, 2026A: Hi,
1) Partly. Your agency dashboard rolls up all sub-accounts in one place: number of clients, messages sent, campaigns live/paused/draft, and credit usage per client. The conversion-level numbers (replies, bookings) live on each client's own dashboard today, and you can jump straight into any sub-account from your list with Sign In, no password needed. If you want everything in one combined view, the API returns analytics per sub-account using your agency key, so you can pull them into your own reporting. A combined conversion view in the agency dashboard is a fair request, post it in the community and I'll prioritise it if more agencies want it: https://skool.com/dm-champions
2) On Meta's pricing change, our partner has not told us anything yet, so I can't give you numbers that would actually be true. What is clear is the direction: the official WhatsApp API is going to get more expensive. The mitigation is already in the product. You don't have to use the API at all, you can run clients on the WhatsApp Web connection instead, which is a flat 50 credits per month ($5) per connection with no per-message fee. For most use cases that's the more convenient option anyway, and it's insulated from whatever Meta does with API pricing. The moment we get concrete numbers from our partner I'll send them out.
3) All three models work today.
a) Each client brings their own key. They connect their own Anthropic key inside their sub-account under Settings, Advanced, BYOK API Keys. A client's own key always takes priority over yours, and their AI replies then cost 0 credits.
b) You use one central key. Connect your Anthropic key at agency level and it runs the AI for every client that doesn't have their own. Those clients still burn credits at the normal rate, which is exactly what you want, because it gives you a per-client meter to bill against while your own credit pool is not charged for those AI actions. You can also set a monthly dollar figure per client to see what each one is running up on your key. That figure is a tracker, not a hard cut-off.
c) You hold the credits and allocate them. This is the default setup. You set a monthly credit allowance per client once, and it renews automatically on the 1st of every month, so you don't re-allocate by hand. Client usage draws from your agency pool, and you can turn on auto-recharge so your card is charged automatically whenever your pool drops below a threshold you set. You can adjust any client's balance or allowance at any time from the Edit Sub Account screen. One tip: put client campaigns on the Max tier, that's 0.25 credits per AI action instead of 1, so the same pool goes four times further.
You can mix all three across your client base, it's set per client.
4) Numbers are bought inside the platform, no Twilio account needed. Your client picks a country and a number and it's activated for WhatsApp automatically. We pass the carrier price through at cost with no markup from us: a one-time purchase charge plus a monthly fee (most standard numbers are around $1.50 a month), both shown before you click Buy. Buy the number while you're in the client's sub-account and the cost comes out of that client's credit balance, so your margin is whatever markup you've set on the credits you sell them. There's no separate per-number markup setting.
On KYC: most countries, including the US, UK, Canada and most of the EU, need nothing at all, you just buy the number. A handful, Germany, France, Australia, Japan and some others, require a business registration form, which opens automatically at the moment of purchase and is reviewed in 1 to 2 business days. It asks for standard business details only, legal name, registration number, website, and in a few countries a registration document such as a KBIS. We never ask for a passport, driver's licence or any personal ID. Meta's ownership verification for WhatsApp is handled automatically, no phone call or 6-digit code.
The one compliance point worth planning for: the number is registered to whatever business details sit on the account you buy it from. So fill in each client's own business name and address on their sub-account and buy the number there. Then the number is registered to your client's business and they're the responsible entity for how it's used. If you buy every client's number on your own agency account instead, all of them are registered to you, and you carry the responsibility for every client's messaging. Same applies to WhatsApp's own rules on opt-in and content, that sits with whichever business is on the sender. A small number of countries only allow numbers registered to a private individual, and since we don't handle personal ID documents we arrange those case by case, just contact support.
5) We're planning our exit for August.
Sohaib
Verified purchaser
Yo man.. I appreciate your clarity of thought & patience to write detailed responses. Thats a great attitude for a founder. I got T5 , not sure if I will to T6 WL /T3 for own use. Once I activate , will update "combined conversion view in the agency dashboard". in skool. Appreciate willingness to accommodate this. This feature would let us charge clients on per lead basis too isnt it ?
Yes, that's definitely possible