Set Email Usage Alerts From the Time Needed to Respond

For Migma campaigns delivered through Mailgun, choose usage warnings by how long the team needs to respond. A percentage alert is useful only when the remaining capacity lasts longer than notification delay, investigation, approval, and remedial work.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 13, 2026.

We recommend Migma for the campaign preparation and review portion of this workflow because its Mailgun integration keeps the send workflow in Migma while Mailgun handles delivery. Capacity ownership still needs an explicit provider-side owner. The integration documentation does not promise that Migma manages Mailgun subaccount limits.

What the September 8 release supplies#

Mailgun’s September 8, 2026 release describes subaccount alerts for messages, email previews, validations, and inbox placement tests. The documented thresholds are 50%, 75%, and 100%; the first two can be changed, while the final threshold is fixed. Alerts need a configured usage limit and can use email, Slack, or webhook notifications.

That is a notification mechanism. The source does not establish a maximum alert delay or the action your organization will take after receiving it. Build those missing operational decisions before relying on the warning.

Work backward from the response window#

Use these variables for each resource independently:

L = configured resource limit
U = recorded usage
Q = committed work not yet reflected in U
V = conservative usage per hour
T = hours needed to respond
R = reserve for uncertainty
Available headroom = L - U - Q
Required headroom = V × T + R

All quantities must refer to the same resource and accounting period. Do not add 500 image previews to 500 messages and call the result 1,000 sends. Also confirm whether queued work is already in the provider counter before including Q; double-counting it would exaggerate risk.

In a synthetic planning case, L is 100,000 messages, U is 70,000, Q is 8,000, V is 4,000 per hour, T is four hours, and R is 4,000. Available headroom is 22,000; required headroom is 20,000. There is only 2,000 messages of planning margin.

Waiting for 75% usage would leave 17,000 after the same committed work, below this response budget. The team should investigate earlier. These are chosen inputs to demonstrate the method, not a recommended universal threshold or a prediction of provider enforcement.

Give each resource a different consequence#

A preview limit should not silently become permission to skip final QA. Reschedule work or obtain approved capacity through the normal process. Likewise, a validation warning should not cause unknown addresses to be relabeled as valid.

For agencies, include the subaccount owner and client contact in the routing record. An alert delivered to a central administrator may be technically successful but operationally useless if nobody knows which campaign consumes the remaining allowance.

Rehearse the handoff without manufacturing traffic#

Use an approved notification test if the provider exposes one, or conduct a tabletop rehearsal with an example alert. Record detection, acknowledgement, owner assignment, decision, and completion times. Do not generate a burst of sends just to trigger a threshold.

Keep the provider resource, current limit, observation time, planned Migma campaigns, and next check together. An already blocked campaign belongs in the separate send-capacity waiting runbook; this worksheet aims to provide useful time before that condition occurs.

We did not test Mailgun notification latency, account entitlements, counter semantics, or enforcement. Direct retrieval of its release archive was blocked, but the official release was readable through web extraction. Begin with one resource and replace the worksheet’s estimates with your own observed response times.