Products · Agency OS
Multi-client messaging for agencies, resellers, and high-volume operators
Agency OS is senderZ's multi-client product. The foundation — tenant isolation, phone pooling, consent logging — runs in production today. The agency-facing surfaces are in active development, with most capabilities landing between Q3 2026 and Q2 2027. Early agency customers onboard through sales while we build the packaged product around them.
Who it's for
For teams running messaging across many clients.
Agencies, lead-gen shops, and SaaS resellers all hit the same wall — many clients, one platform, zero cross-contamination.
Marketing agencies
Run messaging campaigns for 10+ clients without mixing data or budgets.
Lead-gen shops
Deliver SMS follow-ups at scale while keeping each client's compliance trail separate.
SaaS resellers
White-label senderZ into your product and sell messaging as a line item to your own customers.
What you get
Live foundations. Honest roadmap.
Agency OS is in active development. Live capabilities are usable today through manual operator provisioning. Planned capabilities carry quarter-precision ETAs so you know exactly what is real versus what is on the roadmap.
Subaccounts / tenant-per-client
The senderZ database treats every client as a fully isolated tenant. Phone pools, API keys, templates, webhooks, contacts, and consent logs are all scoped by tenant_id — there is no cross-tenant read path anywhere in the code.
Per-client isolation
assertTenantOwnership() in workers/api/src/guards.ts enforces that no request reaches data outside its tenant. Every query on messages, templates, webhooks, api_keys, contacts, and campaigns carries WHERE tenant_id = ?.
Shared dashboard across clients
Planned — Q3 2026An agency-level dashboard that shows send volume, delivery rates, and active campaigns rolled up across every client you manage. Today the operator dashboard handles this for senderZ staff; the agency-facing view is coming.
Per-client usage caps
Planned — Q3 2026Cap new contacts, API requests, or messages per client from the agency console. Prevents a single client from consuming the agency's pooled capacity.
Per-client billing and invoices
Planned — Q4 2026One Stripe account per client with the agency as the billing contact. Invoices itemize each client separately so your reconciliation team does not hate you.
Delegated team access with roles
Planned — Q4 2026Invite account managers, campaign builders, and read-only analysts with distinct permissions. Audit who did what, when, from the activity log.
White-label portal
Planned — Q1 2027Your brand, your domain, your logo on the tenant-facing UI. Customers see your agency name, not senderZ.
Managed 10DLC registration
Planned — Q1 2027senderZ handles brand and campaign registration with US carriers on behalf of your agency and each client. Removes the single most tedious step of onboarding a new SMS client.
Agency margin markup
Planned — Q2 2027Set your own retail price for each senderZ plan and keep the difference. A clean reseller economics model without spreadsheets.
How you use it
Hands-on onboarding until self-serve ships.
Until the self-serve agency dashboard ships in Q3 2026, onboarding is hands-on. Here is the workflow.
Step 01
Sales call
We scope your agency size, client count, SLA expectations, and commercial terms.
Step 02
Agency tenant creation
We provision your agency-level account and the first batch of client subaccounts.
Step 03
Onboard a client
Each client becomes a tenant with its own API key, phone pool, and templates. Your team logs in with delegated access per subaccount.
Step 04
Monitor and scale
The operator dashboard gives you a live view of send volumes, delivery rates, and consent logs across clients. As new agency capabilities ship, we migrate you onto them automatically.
How it compares
Why not just spin up many Workspaces?
Agency OS compared to running many separate Workspace accounts.
| Feature | Agency OS | Workspace |
|---|---|---|
| Clients supported | Many, isolated subaccounts | One |
| Billing separation | Per-client invoices (planned) | Single tenant invoice |
| White-label | Planned Q1 2027 | Not available |
| Custom onboarding | Agency-managed | Self-serve |
| SLA | Custom per contract | Plan-tier support |
Agency OS GA schedule: shared dashboard and per-client caps Q3 2026; billing separation Q4 2026; white-label Q1 2027.
Pricing
Custom annual contract.
Agency OS is a custom annual contract. We price based on client count, message volume, and the agency capabilities you need today versus the ones you can wait for. Contact sales for a quote.
FAQ
Frequently asked questions
Is Agency OS generally available today?
No — Agency OS is in active development. The underlying multi-tenant infrastructure runs in production, so we can provision individual subaccounts for agency customers manually today. The packaged product with agency dashboard, billing separation, and white-label surfaces is planned for Q3 2026 through Q1 2027. If you are an agency ready to start, contact sales and we will provision your first few clients by hand.
How do subaccounts work in practice?
Each client becomes a senderZ tenant with its own API keys, phone assignments, templates, webhooks, contacts, and consent logs. No cross-tenant data leak is possible — every query in the API is scoped by tenant_id.
Can I resell senderZ at my own margin?
Reseller economics are on the Q2 2027 roadmap. Until then, agencies work with us on custom commercial terms — we'll discuss margin, payment terms, and SLA on the sales call.
When will white-label ship?
Planned for Q1 2027. The tenant-facing portal will accept custom branding, custom domain, and custom email sender so your agency name fronts the experience.
What is the minimum commitment?
Agency OS engagements today are custom annual contracts. We have no self-serve tier for agencies yet — that lands alongside the shared dashboard in Q3 2026.
Can I migrate existing Workspace customers into Agency OS?
Yes. Existing Workspace tenants can be converted to Agency OS subaccounts during onboarding without data loss. Phone assignments and contact history carry over.
Start the conversation.
Agency OS is early but the infrastructure is real. We onboard serious agencies by hand while we build the packaged product.