Stage 7 of 12
Pricing Plans and Sending Limits for Your ESP in Octeth
In Octeth, each pricing plan is a user group. The group holds the plan's sending limits, permissions, SMS limits and delivery server. This guide covers how to set up each plan as a group and a plan and limits matrix you can copy.
By Cem Hurturk, founder of Octeth Updated 9 min read
- Octeth user groups
- Permissions
- Sending limits
On this page
The user group sets what an account may send, which features it may use and which IPs its mail leaves from. Billing only decides which group an account is in. Stage 1, business planning, chose your tiers and prices. This stage builds them.
One user group per plan
Octeth billing links each plan to a user group, and the limits on that group are the ones that apply. Billing also names lifecycle groups: one for new accounts, one for suspended accounts and one for cancelled accounts. Octeth’s billing setup page covers the screens.
Give each public plan its own group. New signups land in the signup group, usually a free plan. Suspended and Cancelled are groups of their own, with a sending limit of 1. Set the suspended and cancelled groups in the billing settings, not as overrides on each plan. Stage 9 explains why.
Three rules for this setup:
- Do not use group 1 for a plan. Duplicate it once per plan and change the copies. Leave group 1 itself as it is.
- Keep per-plan settings on the group. Billing moves an account to its plan’s default group on every plan change, and an hourly check moves back any account sitting in a group that is not linked to its plan. A group you set up for one account is undone within the hour.
- Put per-account exceptions on the account. A dedicated IP customer gets the per-account delivery server override. The delivery section below covers it.
An agency platform with billing off uses groups the same way. Staff place each client’s account in its plan group by hand.
Set the sending limits
A group’s limits cover emails per month, per day and in the account’s lifetime, campaigns per month, subscribers, lists and email gateway sender domains. In these fields, 0 or empty means unlimited. A suspended group that must not send uses 1.
| Limit | Where it lives | What it caps |
|---|---|---|
| Emails per month | Limits | The plan’s monthly quota |
| Emails per day | Limits | A daily ceiling under the monthly quota |
| Emails per hour | Rate limits, EmailGateway bucket | API and SMTP relay sends |
| SMS per minute to year | Rate limits, SMS bucket | SMS campaigns and journey SMS |
| Subscribers and lists | Limits | Contacts stored |
| Seats per account | Team members | Team members each account can invite |
Seats work differently again: 0 turns team members off for the group and signs every member out, and 0 is the default.
Month and day
The monthly limit is the plan quota. Set it to the plan’s emails a month. If you price by emails sent, leave subscribers unlimited. With the group limit equal to the quota, sending stops at the quota. If a plan bills overage, set the group limit above the billed quota, or sending pauses before any overage is charged. Stage 1 covers the choice between a hard stop and billed overage.
The daily limit caps how much of the monthly quota an account can send in one day. It is also how you pace an account while its IP warms up. Stage 5, sending infrastructure and IP warm-up, has the warm-up schedule. For campaigns, the daily limit is the finest pacing control on the group.
Hour and minute
Hourly and per-minute caps sit in the group’s rate limits. The rate limits are a JSON document with an EmailGateway bucket and an SMS bucket, each with a limit per minute, hour, day, week, month and year:
{
"EmailGateway": {"Minute": -1, "Hour": 5000, "Day": -1, "Week": -1, "Month": -1, "Year": -1},
"SMS": {"Minute": 240, "Hour": -1, "Day": -1, "Week": -1, "Month": -1, "Year": -1}
}
The 5,000 and the 240 are placeholders, not recommendations. In rate limits, -1 means unlimited and 0 allows nothing. That is the opposite of the limit fields, where 0 means unlimited. An account can also carry its own rate limits that override its group’s, so check both when an account cannot send.
Grant permissions per plan
The group’s permissions decide what its accounts can do, section by section. Set them before you open signups.
Check that each plan group has these four permissions an ESP’s customers need:
| Permission | What it allows |
|---|---|
EmailGateway.AddDomain | Add a sender domain |
EmailGateway.ManageDomain | Manage a sender domain |
SMSCampaigns.Get | See SMS campaigns |
SMSCampaigns.Manage | Create and send SMS campaigns |
We recommend duplicating group 1 for each plan and adding these four. Leave List.ExternalMySQL off on every plan.
Two more settings sit next to the permissions:
- Plan features. Octeth billing gates journeys and transactional email per plan, in the new interface. Decide which plans get each. Tick them in the plan, save, and check them again: they start unticked.
- Custom headers. A customer could pick another IP on a shared MTA by sending an
X-Virtual-MTAheader. The fix is on the MTA: each plan’s SMTP user ignores that header and sends only from its own IP or pool. Stage 5 covers the MTA side of this. Also remove the header in every plan group, as a second layer.
Upgrades can change permissions. After each upgrade, compare each group’s permissions with your plan design.
Set up SMS
SMS needs three things before the first campaign:
- A gateway. Add the SMS provider in the staff area. A gateway is either available to every account or assigned to chosen accounts. It holds the sender numbers and optional short link domains. Octeth’s SMS gateways page has the fields.
- Permissions. The two
SMSCampaignspermissions on each plan group that sells SMS. - Group SMS limits. Check the
SMSbucket of every group’s rate limits. Set a real limit or -1 for each interval. A 0 holds every SMS campaign of that group in the queue and drops every journey SMS. Removing the twoSMSCampaignspermissions blocks SMS campaigns only. To block journey SMS as well, do not make the gateway available to every account. Assign it to the accounts that bought SMS.
Then pace the sending. Carriers set 10DLC limits per registered campaign and per brand. On 10DLC numbers with a low vetting score, AT&T allows 240 SMS a minute, and T-Mobile caps messages per day per brand (Telnyx 10DLC rate limits). Set the Minute value of the group’s SMS bucket, or the account’s own rate limits, to the strictest carrier limit, so it holds across all of that account’s SMS campaigns and journey SMS. A campaign that reaches the limit waits. A journey SMS that reaches it is not sent and not retried, so leave room above your journey volume. The bucket counts per account. If several accounts share one gateway and one registration, set the gateway’s own rate limit as well. An SMS campaign’s send speed in Octeth is per campaign, and the sender can change it. From 6.0.5, also set the default send rate in the staff SMS settings, and run one Octeth campaign at a time per carrier registration. Size the segment to stay under each carrier’s daily cap.
Assign a delivery server per plan
Each group has a delivery server for each channel: marketing campaigns, transactional email and autoresponders. An account sends from its group’s servers unless something overrides them.
Octeth picks the server in this order, each step overriding the one before:
- The user group’s server for the channel.
- A recipient MX route, which sends mail for matching recipient domains through another server.
- The per-account override, set on the account’s settings in the staff area. Before 6.0.7 it replaces all three channels at once. From 6.0.7 staff can set it per channel.
- Segment routing, for campaigns only.
Give each plan its own delivery server, and each server its own IP. Let the Free plan share its IP with the Suspended and Cancelled groups, so a new or stopped account never sends from a paid plan’s IP. Stage 5, sending infrastructure and IP warm-up, covers the pools, the MTA users behind each server and the transactional split.
Use the per-account override for a dedicated IP customer. Do not clone the plan’s group for that account. Billing checks group membership every hour and moves an account in a group that is not linked to its plan back to the plan’s default group, and its mail goes back to the plan’s IPs. A group you link to the plan as a member group in the catalog is left alone until the account changes plan.
The plan and limits matrix
A template for a self-serve ESP that prices by emails sent. “Set per plan” marks a value you choose for your own plans, from the tier table in stage 1.
| Plan | Price a month | Emails a month |
|---|---|---|
| Free | $0 | Set per plan |
| Plan A | Set per plan | Set per plan |
| Plan B | Set per plan | Set per plan |
| Plan C | Set per plan | Set per plan |
The other settings, on every plan:
| Setting | Value |
|---|---|
| Base group | A duplicate of group 1 |
| Subscribers | Unlimited |
| Campaigns per month | Unlimited |
| Emails per day | Set per plan |
| Email gateway sender domains | Set per plan |
| Email gateway rate limits | Set per plan |
| SMS rate limits | Set per plan |
| Seats per account | Set per plan |
| Overage | None. Sending stops at the monthly limit |
| Journeys and transactional email | On, or set per plan |
| Extra permissions | The four sender domain and SMS permissions above |
List.ExternalMySQL | Off |
| Email footer | Plan footer with unsubscribe link. Free can add a badge for your brand |
| Billing interval | Monthly |
Lifecycle groups:
| Group | Emails a month |
|---|---|
| New accounts, which join Free | Same as Free |
| Suspended | 1 |
| Cancelled | 1 |
Every new signup also starts Untrusted, so its campaigns wait for staff approval whatever its plan allows. Stage 8, Acceptable use and abuse prevention, covers that review. Stage 9, Stripe billing, connects these plans to prices.
Octeth versions this stage relies on
| Feature | Octeth version |
|---|---|
| Billing plans linked to user groups | 6.0.0 |
| Email gateway and SMS rate limits per group | 6.0.0 |
| Monthly and daily limits also stop API and SMTP relay sends | 6.0.1 |
| New-interface signups start Untrusted, and Untrusted accounts cannot send through the gateway or journeys | 6.0.1 |
| User group screens in the new staff area | 6.0.2 |
| Per-account delivery server in the new staff area | 6.0.2 |
| Seats per account on the user group | 6.0.5 |
| Send speed (rate per minute) on SMS campaigns | 6.0.5 |
Build on 6.0.5 or later. The group and delivery screens are in the new staff area from 6.0.2, and seats and the SMS send speed arrive in 6.0.5. Then run the checks in this guide against the version you install. Stage 4 covers the install.
Before you move on
- Each plan has its own user group, duplicated from group 1, and no plan uses group 1.
- Every plan group has the four sender domain and SMS permissions.
- Each plan group's monthly limit matches the plan, or sits above the billed quota if the plan bills overage.
- The suspended group has a sending limit of 1, not 0.
- Every group's SMS rate limits are real numbers or -1, never 0. Plans without SMS lack the SMS permissions, and the SMS gateway is assigned only to accounts that bought SMS.
- The Minute value of each group's SMS bucket is at or below the strictest carrier limit for its senders.
- Each plan group has a delivery server set for marketing, transactional and autoresponder mail.
- Every SMTP user Octeth uses ignores the X-Virtual-MTA header, and every plan group also removes it.
- Team seats are set on each plan group.
- Dedicated IP accounts use the per-account delivery server override, not a cloned group.
- You review every group's permissions after each Octeth upgrade.
What we've seen go wrong
An SMS campaign faster than the carrier allowed
On another install we run, an SMS campaign with no send rate set went past the carrier's per-minute limit for the sender's 10DLC numbers within minutes. Carriers set 10DLC limits per registered campaign and per brand, and a campaign's send rate in Octeth is a setting the sender can change. Set the Minute value of the group's SMS bucket to the strictest carrier limit, so it holds across all of that account's SMS campaigns. Journey SMS over the limit is dropped, not delayed.
Related glossary terms
We build ESPs
Rather have us build this?
We configure your plans as Octeth user groups, with permissions, sending limits and a delivery server per plan.
Running it yourself?
Get the Octeth license
Pick the license tier that fits your customer count.