Skip to main content
Every campaign and mailbox on the same sending domain shares the domain’s reputation. Domains → your domain → Sending limits is therefore the control center for total daily volume. It shows the configured limit, the current effective limit, today’s use, mailbox capacity, the next reset, domain age, health, and the exact limiter in effect.

​
The limit cascade

Norbelys evaluates every send against all applicable controls. The smallest available capacity wins. If any layer has no available capacity, the message waits. A campaign with no usable mailbox or mailboxes that are all full sends nothing; that is intentional.
The domain counter is atomic. Ten campaigns launched together cannot each consume the full domain allowance before the others notice. Existing conversations are selected before new first touches, then capacity is distributed toward the least-used campaign.

​
Choose a control mode

​
Legacy

Existing workspaces stay unchanged. The UI shows a recommendation, but no domain budget is enforced until an owner explicitly selects another mode and saves.

​
Manual

You own the configured daily cap. Norbelys measures health and recommends changes, but it never changes or pauses domain traffic automatically.

​
Norbelys Autopilot

You still own the configured cap. Autopilot computes a separate, visible effective cap inside the minimum, maximum, and maximum daily growth percentage you set. It may lower the effective cap when mailbox reputation degrades and ramps it gradually after recovery. It never rewrites the configured cap. Two independent switches grant additional authority:
  • Pause new first touches — existing conversations may continue, but new outreach waits while the domain is degraded or critical.
  • Pause all sends — a critical domain may stop all messages. This does not enable itself when Autopilot is selected; it must be granted separately.
When a degraded or critical domain returns to healthy, Norbelys sends a deliverability email and resumes only according to the mode, limits, growth bounds, and permissions saved in the UI.

​
How the recommendation is calculated

The recommendation uses active mailbox capacity, registration age when RDAP publishes it, and the date Norbelys first observed a successful send. A newly registered domain or one with little sending history starts lower. Missing RDAP data never invents an old age; the sending history remains the conservative signal. The recommendation is advice in Legacy and Manual. In Autopilot it is used only when you leave the configured cap empty, and the visible Autopilot bounds still apply.

​
Configure it through the API

Policy is part of the existing Domain resource. Use PATCH /v1/domains/{id}; there is no second sending-policy endpoint.
Operational fields such as current health, usage, recommended cap, and effective cap are read-only. This prevents an API client from disguising observed state as customer consent.

​
Safe launch pattern

For several new campaigns on one domain:
  1. Set the domain budget first.
  2. Give each campaign a realistic newPerDay; it is a first-touch target, not permission to bypass the domain.
  3. Use a wider send interval and useful jitter instead of launching every campaign on the same three-minute cadence.
  4. Stagger campaign windows.
  5. Watch the domain health, complaints, bounces, and provider dashboards before increasing the cap.
Changing a cap takes effect on the next claim. It does not rewrite thousands of scheduled lead rows, so large campaigns stay developer-friendly and predictable.