---
title: "How do you send email and SMS for your customers from a SaaS app?"
description: "Multi-tenant email and SMS for SaaS: one workspace per customer, with its own domain, suppression list, keys, usage and texting brand, set up by API."
url: https://www.unitpost.com/blog/concepts/send-email-sms-for-your-customers
section: Blog
updated: 2026-11-17
---
# How do you send email and SMS for your customers from a SaaS app?

Give each customer its own workspace, the sub-account other providers call a subuser or server. It keeps that customer's domain, contacts, suppression list, keys and usage apart, so one customer's bounces never block another's receipts. On Unitpost an organization key creates the workspace with your own customer id, mints a key that reaches only it, sends every workspace's events to one webhook and reports usage per workspace for rebilling.

## How do you send email and SMS for your customers from a SaaS app?

> Multi-tenant email and SMS for SaaS: one workspace per customer, with its own domain, suppression list, keys, usage and texting brand, set up by API.

A SaaS product that sends email or texts for its customers is a multi-tenant sender: one integration, many businesses behind it. The easy start is one account with one key. It works until the first customer uploads a bad list.

### Why not send everything from one account?

On a single account, everything your customers do is pooled:

- One suppression list. An address that complained about customer A's newsletter is blocked for customer B's password resets.
- One reputation. Mailbox providers and the sending service judge the account by its bounce and complaint rates, so one careless customer can slow everyone's mail, or get the whole account paused.
- One rate limit and one bill. A customer's burst slows the others, and you can't tell from the invoice who sent what.
- One place to leak. A key that can send for every customer is a key that can send as any of them.

### What does a workspace per customer give you?

A workspace is where mail is sent from. Giving each customer one keeps apart:

- domains: each customer verifies its own, with its own DNS records;
- contacts, segments and the suppression list;
- API keys that reach that workspace and nothing else;
- templates, webhooks, numbers and SMS consent records;
- plan, usage and limits, and any pause or suspension.

The organization above them holds what's shared: the people who run your platform, the card, and the keys that create workspaces.

### How do you set it up by API?

- Ask for API access. On Organization → API, request access; Unitpost approves each organization. An Owner then makes an organization key (`ok_live_…`) and sets its rules: which plans it may pick, the highest price and how many new workspaces a month.
- Create a workspace when a customer signs up, with your own id for them:

```bash
curl -X POST https://www.unitpost.com/api/v1/organizations/$ORG_ID/workspaces \
  -H "Authorization: Bearer $UNITPOST_ORG_KEY" \
  -H "Idempotency-Key: create-cust_8421" \
  -H "Content-Type: application/json" \
  -d '{"name": "Acme Dental", "external_id": "cust_8421"}'
```

- Mint a workspace key with `POST …/workspaces/{workspace_id}/api-keys` and store it with the customer. It reaches only that workspace and is shown once.
- Add the customer's domain with that key (`POST /email/domains`) and show them the DNS records it returns. The domain checker (/tools/domain-checker) tells them what's missing.
- Register one organization webhook (up to five) instead of one endpoint per customer. Each delivery names the `workspace_id` and your `external_id`, so you route it straight to the right customer.
- Read usage per workspace (`GET /organizations/{id}/usage`) each period and bill each customer by its `external_id`.

Every step is also an MCP tool and a CLI command, so an agent with the organization key can run the setup (what an agent can do (/guides/organizations#org-agent)).

### Whose domain should the mail come from?

- Your domain (`notifications@yourapp.com`): no setup for customers, but every customer shares your name and your domain's reputation. Fine for system mail about your own product.
- The customer's own domain (`hello@acmedental.com`): mail that looks like theirs and builds their reputation, not yours. They add a few DNS records once. Use this for anything their own customers receive.
- A subdomain of yours per customer (`acme.mail.yourapp.com`): a middle ground when customers can't touch DNS, but replies and brand recognition suffer.

Whichever you pick, the From domain has to be the one the workspace verified, so SPF, DKIM and DMARC line up.

### What changes for SMS?

In the US, every business texts under its own registered brand. You can't register your platform once and text for all your customers: each one needs its brand, a use case that matches what it sends, and its own number. Opt-outs belong to that sender too.

A workspace per customer gives each one that: its own brand, number, consent records and STOP list. The brand, the use case and the 10DLC or toll-free registration can all be filed by API, with the price quoted before anything is bought and a monthly cap on what a key may spend (SMS setup by API (/docs/sms/start#sms-start-agents)).

### How do you bill customers for what they send?

Pick per workspace: the customer pays for its own plan, your organization's card pays for each workspace's plan, or, on request, several workspaces share one plan's allowance. The organizations guide (/guides/organizations#org-three-ways) compares the three. Whichever you choose, the usage endpoint gives each workspace's sends, SMS and spend for its own billing period, keyed by your `external_id`, so rebilling doesn't need a spreadsheet.

### What stays with a person?

Approving API access, adding a card, buying the shared plan, making the organization key and inviting people all happen in the dashboard. The day-to-day work (creating workspaces, keys, domains, webhooks and sends) is the API's.

## FAQ

### Are workspaces the same as sub-accounts?

In function, yes: other providers call them subusers, subaccounts, servers or tenants. On Unitpost each workspace has its own domains, keys, contacts, suppressions, plan and usage, and an organization groups them, holds the card and owns the keys that create them.

### Does one customer's bad list hurt the others?

Much less than on one shared account. Suppressions, sending limits, quality reviews and suspensions are per workspace, and each workspace is tracked as its own sender, so a customer whose list bounces is paused on its own while the rest keep sending.

### What do you need before creating workspaces by API?

Creating workspaces by API needs an organization that Unitpost has approved (Organization → API → Request access) and a card on the organization. The Owner sets which plans a key may choose and how many new workspaces it may create a month.

## Related

- [SMS deliverability: registration, consent, quiet hours and carrier filtering](https://www.unitpost.com/blog/deliverability/sms-deliverability): Why US business texts get blocked and how to avoid it: 10DLC and toll-free registration, consent and STOP handling, quiet hours, and content carriers filter.
- [What is an SMS MCP server?](https://www.unitpost.com/blog/agents/sms-mcp-server): An SMS MCP server gives an AI assistant tools to send and read text messages. What the tools are, what it needs first, and the rules it enforces.
- [How to fix an SPF record that isn't found](https://www.unitpost.com/blog/troubleshooting/spf-record-not-found): Why an SPF lookup returns nothing even after you've added the record, and how to diagnose it: propagation, wrong host, quoting, and the one-SPF-record rule.
