Wallet
The monthly sending allowance on a paid plan. Email and SMS draw it, and sending pauses once overage hits the cap.
A paid plan includes a monthly sending allowance: a dollar wallet you spend on email and SMS, each at that channel's own rate. It refreshes at the start of each billing period and does not roll over. The unused portion carries into the new plan only when you upgrade. Balance, spend, and overage are on Settings → Usage. The plan itself is on Settings → Billing. Current rates are on Pricing.
Free plan
The free plan has no dollar wallet. It has a monthly email quota and a daily cap, both shown on the usage page. SMS is not included.
What the wallet pays for
- Email is charged at your plan's rate per thousand messages. Marketing and transactional sends use the same rate.
- SMS is charged per segment at the published rate for the recipient's country.
- Number and registration fees for toll-free and 10DLC (the monthly number lease, and one-time carrier fees such as brand registration and vetting) are quoted before you confirm, then taken from the wallet. They are not a separate charge on your card.
After the allowance
When the allowance is spent, sending continues and the extra is billed as overage, at a higher rate than your plan. Overage stops at 25% of the monthly allowance (a $30 plan can go $7.50 over), and you get an email when it's half used. After that, sends pause until the allowance refreshes or you move to a larger plan.
You can't buy extra credit. If the workspace already has purchased credit, that balance is spent after the monthly allowance and does not refresh.
Not everything comes out of the wallet
A dedicated IP is a line item on your card. It is not drawn from the sending allowance.
The same snapshot is on the API. GET /api/v1/usage returns the plan, the period, and on a paid plan the wallet in integer cents: allowance, spend, upgrade carryover, purchased credit, and overage. On the free plan wallet is null.
Paying for several workspaces
Each workspace has its own plan and allowance. When your organization has several workspaces, each one is paid for in one of three ways:
- The workspace pays for itself, with its own card. This is the default.
- The organization's card pays for the workspace's own plan. The workspace keeps its own plan, allowance and limits; only the card changes. Pick the organization's card when you create a workspace, or move one from its Settings → Billing: a free workspace moves at once, one on a paid plan when its current period ends, with its plan and any promotion carried over.
- The workspace shares the organization's plan (on request). The organization buys one Starter or Growth plan, and the workspaces on it share one monthly allowance and one pay-as-you-go band.
Shared usage
On a shared plan, email and SMS from every workspace on it draw on the plan's allowance, and its Ask Unit credits are shared too. Each workspace keeps its own domains, webhooks, team seats and API keys, with the plan's limits in each one. Starter covers up to 3 workspaces and Growth up to 10; support can raise the number (Organization → Billing → Ask for more, once every place is taken).
- Caps. An Owner or Billing member of the organization can cap what each workspace draws in a billing period. At its cap only that workspace pauses.
- Alerts. The organization's Owners and Billing members get an email when the shared allowance is 50%, 80% and 100% used, and when sending pauses. Organization → Billing shows the plan's usage and what each workspace drew.
- Privacy. Each workspace sees only its own usage, against its cap or the shared allowance.
- Invoices. Overage is billed on the shared plan's invoice, and the invoices are the organization's, on Organization → Billing.
Ask for shared usage
Shared usage isn't on by default. To set it up:
- On Organization → Billing, an Owner or Billing member clicks Request access. Unitpost reviews each request.
- Once it's approved, buy the plan in one checkout. A promotion code works there.
- Add workspaces on Organization → Billing, each with an optional cap, or pick the shared plan when you create a workspace. Joining moves a workspace onto the organization's card. A workspace with a paid plan of its own can join once that plan has ended.
To take a workspace off, an Owner or Billing member of the organization removes it on Organization → Billing, or the workspace's own Owner leaves from its Settings → Billing. Its usage this period stays on the shared plan. It then moves to Free if its Owner doesn't already have a free workspace, and otherwise needs a plan of its own.
With an organization key, GET /api/v1/organizations/{id}/shared-plan reads the plan and this period's usage, and PUT, PATCH and DELETE /api/v1/organizations/{id}/shared-plan/workspaces/{workspace_id} add a workspace, set its cap and take it off. POST /api/v1/organizations/{id}/workspaces with shared_plan: true creates a workspace straight onto it. Each of those needs organizations:billing (the create organizations:write too), which only an organization Owner gives a key. Asking for shared usage, buying, upgrading and ending the plan stay in the dashboard.