SapaganDocs sapagan.com

Concepts

Quiet hours and caps

When marketing messages wait, and how often one person can be messaged.

Quiet hours#

Marketing messages are not sent between 22:00 and 07:00 in the workspace's time zone (Jakarta time by default). A campaign scheduled inside that window moves to the end of the window, and the response says so in scheduleShiftedTo. A send that reaches the window while running waits until it ends.

Not held by quiet hours:

Frequency caps#

Caps stop one person from receiving too much. They count and limit store sends in a marketplace: by default 2 push messages per store and 4 across stores in a rolling 7 days. Caps are checked at reservation under a lock, so two campaigns planned at the same time cannot both pass the same cap.

Transactional messages have their own per-person limits: at most 10 messages a minute and 100 an hour reach one person, and at most 60 are accepted per person per minute (429 recipient_rate_limited, with Retry-After).

Store caps#

A marketplace store also has a reach cap per campaign (by tier, and lower while the store is new), monthly campaign quotas and a daily campaign limit. GET /v1/scope/policy and GET /v1/scope/usage show them.

Environments#

A development workspace sends only to the test list and fails closed when the list is empty. A production workspace sends to everyone eligible. Its test list only limits who "Send a test" may reach.

Kill switches#

PUT /v1/workspace/sending turns all sending in a workspace on or off, always with a reason. Stores can be paused one by one. Kill switches stop campaigns, journeys and transactional messages. A transactional message dispatched while sending is off ends as failed and is not resent when sending comes back.

Email warm-up#

A new sending domain ramps up over 20 stages, starting at 100 emails a day, with engaged recipients first. Marketing email over the day's allowance waits for the next day. Transactional email is never held back. See Email sending domain.