Plans and billing

How coss.com plans, usage credit, volume pricing, add-ons and invoices work, and what happens when you reach a limit.

Every organization is on a plan. A paid plan's monthly fee is usage credit: it is spent on usage of any coss.com product, so a month costs the larger of the fee and your usage (plus any add-ons). The Free plan has no credit but includes a monthly allowance.

See what your volume would cost on the pricing page.

Enterprise plans are sold as annual contracts: custom rates, committed volumes, invoicing with payment terms, and direct debit. Contact sales.

Usage

Usage is counted per product and billed at these rates:

  • Email is counted per recipient handed to the email provider: every address in to, cc and bcc once, except suppressed addresses. Emails that fail before sending, or are canceled, cost nothing. Sandbox environments are never billed.
  • Email attachments are counted in MB, past the first 1 MB of each email's attachments and rounded up, for each recipient the email is billed for: 3.5 MB of attachments to 2 recipients is 6 MB.
  • Received email is counted per message stored, once for each environment it reaches (sandbox environments too: they receive real mail). Mail flagged as spam or carrying a virus, mail dropped over a limit and the dashboard's test emails cost nothing.
  • Received email data is counted in MB, past the first 1 MB of each raw message and rounded up, once for each environment it reaches. What's free above is free here too.
  • Inboxes are counted per day each live inbox exists, starting when it's created: 30 inbox-days are an inbox for a month. Sandbox inboxes are free. See inboxes.
  • SMS is counted per segment, by destination country, once a message reaches a carrier; received messages by the receiving number's country. Phone numbers and US carrier registration fees are passed through at cost. SMS needs a paid plan: see countries and pricing.
  • Volume pricing is graduated: each band is priced at its own rate, so there's no cliff. With 2,000,000 emails in a month, the first 1,000,000 cost $0.40 per 1,000 and the next 1,000,000 $0.30 per 1,000: $700.
  • Usage is counted in calendar months (UTC), and the bands start over each month.

How a month is billed

Your plan's fee is charged at the start of each month, and becomes that month's credit. At the end of the month, its usage is rated, the credit is applied, and anything beyond it is charged on the next month's invoice with the next fee.

For example, on Pro with 2,000,000 emails in October:

Over the month you paid $700: the larger of the fee and the usage.

Charges during the month

Usage beyond your credit doesn't always wait for the month's end. When usage not invoiced yet reaches your billing threshold, it's charged to your payment method right away, as an invoice of its own (threshold), and comes off the month's invoice, which still shows the whole month's usage. You pay for it once, at the same rates.

New accounts start with a threshold of $100. It's a fifth of your credit limit, up to $5,000, so it rises with the limit. Contracts and net terms aren't charged this way.

Add-ons

Add-ons are charged on top of your plan, and aren't paid by its usage credit:

Add one on the dashboard's billing page (owners): you pay for the rest of the month at once and it applies as soon as that's paid. Removing it takes effect at the end of the month, and can be undone until then. Add-ons stay when you upgrade; downgrade to a plan that doesn't offer one only after removing it. On a contract, add-ons are part of the contract.

Changing plans

  • Upgrades take effect as soon as they're paid: you pay the difference for the rest of the month, and get the same difference as extra credit.
  • Downgrades and cancellations take effect at the end of the month, and can be undone until then. Remove what the lower plan doesn't include first (for example, single sign-on or log drains): a downgrade is refused while you still use it.
  • If a month starts on Free and you upgrade, Free's allowance still covers its first emails.

Limits and paused sending

  • On Free, live sends past the month's allowance are refused with a 402 billing_error (usage_limit_exceeded) until the next month or an upgrade, and so are new live inboxes past its inbox-days and new live Scheduling hosts past its host-days. Received mail past its allowance is dropped (and counted on Received emails). Once only an attachment or received data allowance is used up, emails within their included 1 MB still go through.
  • If an invoice can't be collected, we retry it and email your billing contacts. Once it's overdue past the grace period (14 days unless your contract says otherwise), live sending is paused (402, billing_hold) until it's paid. So are new live bookings, Scheduling hosts, signature requests and inboxes, and hosted forms stop accepting submissions. Sandbox keys keep working, scheduled emails wait rather than fail, and bookings already made stay. Mail still arrives, and monthly charges for inboxes, hosts and phone numbers you keep continue.
  • Owners can set a spend limit: when usage beyond your credit reaches it, live sending pauses until the next month or until the limit is raised. Usage alerts go out at 80% and 100% of your credit (owners can change the thresholds).
  • Every self-serve account has a credit limit. Over it, live sending pauses (402, billing_hold) until it's back under.
  • Owners can also set monthly budgets for members' personal API keys, projects and single API keys: over a budget, only its live sending pauses (402, budget_exceeded). See Spend and budgets.

Credit limit

The credit limit caps what coss.com carries for your organization: usage not invoiced yet, unpaid invoices, and threshold charges from the last 30 days (a card payment can still be disputed by then). Your plan's fee doesn't use it up, and usage its credit covers isn't counted.

  • A new account's limit is $500.
  • It rises on its own to twice your settled payments (paid more than 30 days ago), up to $100,000. Payments for your plan's fee count towards this.
  • Billing settings show your limit and what's in use, and owners get an email at 80%.
  • If you need more sooner (say you're moving a large volume over), ask support to raise it: a limit they set replaces the automatic one.
  • A threshold charge that fails pauses live sending right away until your first payment has settled; after that, only reaching the limit (or the grace period above) does. Paying the charge resumes sending within a minute. A payment disputed as fraud pauses it until support has looked at it.

Contracts and net terms have no credit limit unless one is agreed.

Credits

Besides your plan's credit, coss.com support can add credits, in dollars or as free units of a product (for example, 50,000 free emails). Credits that apply to one product are used before general ones, and those expiring soonest go first. Your billing settings list every credit with what's left of it, including threshold charges waiting to come off the month's invoice.

Invoices and payment

Invoices are in US dollars. By default they're charged to your card; contracts can be invoiced with payment terms (bank transfer) or charged by direct debit. Billing settings show your invoices and their PDFs, and let owners update the payment method and billing details.

Prices exclude tax. Where coss.com is registered to collect it, tax is calculated from your billing address and added to the invoice. Add a VAT or other tax ID under Manage billing details so it appears on your invoices and is taken into account.

Billing API and events

Read the organization's billing with any API key (billing is organization-wide, so every environment's key sees the same). Plan changes, payment methods and spend limits stay in the dashboard.

const { :  } = await ..();
// The plan, this month's usage and what it would cost so far (cents), standing and limits.
.(?.plan, ?.., ?.);
Billing.plan: PlanKey | undefined

The plan in effect now (free without a contract).

// Usage per day and environment, oldest first. const { : } = await ..({ : "day", : "environment" }); // This month's usage per member (`user_id`: whose personal API key caused it; `null`: the rest). const { : } = await ..({ : "month", : "user" }); // Invoices (newest first) and credits. const { : } = await ...({ : "open" }); const { : } = await ...();

group_by also takes project and api_key. Usage recorded before coss.com kept its source has null there.

Amounts are integers in cents; unit prices are dollar strings ("0.0004"). Lists page with after (the last id) while has_more is true. Usage covers up to 400 days per request (7 by hour) and is kept for 400 days.

Subscribe a webhook endpoint to the billing.* events to follow invoices, payments, plan changes, usage alerts and paused sending as they happen:

const  = await (, , ..!);
if (. === "billing.invoice_payment_failed") {
  (`${...}: ${...}`);
} else if (. === "billing.usage_threshold_reached") {
  .(`${..}% of this month's ${..} used`);
}

Billing events go to live environments' endpoints only. billing.plan_changed is sent when a change is decided, with the moment it applies in effective_at (a downgrade's is the start of next month); change is reverted when a scheduled change is undone.

Last updated