Platform
The messaging platform
behind senderZ.
senderZ is what shows up when you stop treating messaging as an endpoint and start treating it as infrastructure. Four pillars hold the platform together.
Pillar 01
Agent-native messaging
senderZ treats AI agents as first-class clients. Every tool the MCP server exposes — send_message, list_contacts, check_optout — is auditable, scoped to a single tenant, and safe to put in front of a human approval. Auto-reply personas, suggested replies, and human-in-the-loop controls are built into the same primitives your developers use. This is what separates a messaging endpoint from a platform that an agent can operate.
Pillar 02
Tenant-first architecture
Every message, contact, template, and webhook belongs to exactly one tenant. Phone pools, API keys, and subaccounts map cleanly onto the boundaries your customers already think in. Agencies and resellers get isolation that stops at the right layer — customers can see their own data, never anyone else's, while operators retain a single pane of glass. The tenant model is not a feature bolted on top; it is how the platform is built.
Pillar 03
Compliance by default
STOP, START, HELP keywords are processed before they ever reach a tenant webhook. Quiet hours are enforced per-recipient with time zone awareness. Every inbound message carries a consent log entry. None of this is optional, and none of it requires custom code. The platform ships safer operational rails than most teams would build on their own.
Pillar 04
Transparent economics
Plans are priced on new contacts, not per message. Messages to customers you have already reached are unlimited. Trials are fourteen days, no credit card required, and there are no per-message overage fees. The number on the pricing page is the number on the invoice. Operators get a predictable cost model; developers get a billing surface that does not require a calculator.
Architecture
How a message
travels.
Six stages, one round trip. Compliance, routing, and webhooks all happen between your call and the recipient's screen.
- 01
Your app
Calls the senderZ API with destination, channel, and body.
- 02
senderZ API
Authenticates, validates, and enqueues the job — returns a message ID.
- 03
Queue
Durable, idempotent, retry-safe — never drops a message.
- 04
Router
Resolves the tenant phone pool, runs compliance checks, picks a channel.
- 05
Delivery
iMessage first. RCS or SMS fallback. All measured under 200 ms.
- 06
Webhooks
Delivery, reply, and status events flow back to your tenant URL.
Path
Your app
↓
senderZ API
↓
Queue
↓
Router
↓
iMessage / RCS / SMS
↓
Webhooks