Skip to main content

SMS limits and costs

MonoPbx counts the SMS and MMS your company sends and receives, lets you set caps that stop runaway sending, and estimates what the messages cost from your own price list.

Open Admin > Messaging > SMS (/admin/sms) and choose the tab Limits and costs (/admin/sms/metering) or Prices and invoices (/admin/sms/pricing). The counts need messaging:read. Seeing caps and prices needs integrations:read. Changing them needs integrations:write.

Counts​

The message log is the meter. The report groups messages for a range of UTC days:

  • By number: outbound messages by the sending number, inbound by the receiving number.
  • By sender: outbound messages by who sent them: a user, an API key or a background job.
  • A total.

SMS are counted in messages and in segments (what carriers bill). MMS are counted in messages. Outbound messages that failed are not counted. The API is GET /api/v1/sms/usage/report?from=&to=.

Caps​

A cap limits the messages (SMS and MMS together) for one scope and period. Under Sending caps, add a cap with:

SettingOptions
DirectionMessages sent (default) or Messages received
ScopeWhole company, One number, One user, Each recipient, One API key, One background job
PeriodPer day, Per month, Rolling hour, Rolling 24 hours
LimitA whole number. 0 blocks every send.

Setting a cap again for the same direction, scope and period changes its limit. Each cap shows the messages counted in the current period. Days and months are UTC.

  • Each recipient limits the messages to any one destination number, every destination counted on its own.
  • A cap on received messages applies to the whole company or one number only. It never refuses a message; it only raises the alert.
  • A cap for a user counts that signed-in user's sends. Sends by API keys and jobs count against the company, number and recipient caps, and against a cap for that key or job.
  • Over a cap, a send is refused with 409 and the code MPBX-SMS-CAP-REACHED, and nothing is stored. This holds for the console, the API and integrations. Messages already queued are not stopped, and automatic replies to STOP keywords are not capped.

Cap alerts​

The first refusal in a period raises one sms.cap_reached event (topic sms) and one audit record. Later refusals in the same period are silent. Rolling periods alert once per UTC day.

Under Cap alerts by e-mail, list up to 10 addresses, one per line. Write the language of an address's mail after it (for example ana@example.com es-MX); without one the mail uses the company's default language. Each gets a mail the first time a cap is reached in its period. Tick Also mail every active administrator who can manage integrations to include them, in their own language. With no addresses, only the event and the audit record are produced. When that box is ticked, the administrators who have the MonoPhone app also get a notification, "SMS limit reached", on their phones; tapping it opens the app's alerts. It carries no number, message or count. The text of a mail names the cap and never a phone number.

Prices and cost estimates​

Under Price list, enter your own prices per SMS segment and per MMS, sent and received, in the company currency. The report multiplies the counts by your prices. The result is an estimate: your carriers' invoices decide. MonoPbx ships no price data of its own.

On the Prices and invoices tab:

  • Prices per destination: a rule sets four prices (SMS sent, SMS received, MMS sent, MMS received) for numbers that start with a prefix of 1 to 8 digits, such as 44 or 1415. The longest matching prefix wins; other numbers use the base price list. Paste or upload a rate sheet (CSV or text, up to 256 KB), at most 500 rules. Saving replaces all rules.
  • Carrier invoices: enter an invoice total for a range of days (at most 400) with its currency and, when it is not the company currency, an exchange rate. Each invoice is shown with the billed total, the estimate for the same days and the difference. A large difference means the price list or the rules are out of date. One line per invoice: label, first day, last day, billed total, currency, exchange rate.

Limits​

  • At most 500 caps and 500 price rules per company.
  • Alerts are the event, the audit record and e-mail.
  • The estimate is only as good as the prices you enter.