Sending safely

Outpulse is built around a simple safety model: you decide what to send, Outpulse decides when to send it. Every campaign send goes through a per-workspace queue that paces sends, enforces daily caps, and respects your posting schedule. You don’t configure modes per monitor anymore — campaigns are explicitly human-driven (you pick leads, you generate drafts, you click Send). Everything below is enforced automatically once you do click Send.

---

​

Daily caps

Outpulse enforces hard daily caps per connected account. The caps are tracked per (workspace × connected account × day) and reset at midnight in your configured timezone. When a cap is hit, remaining queued sends defer to the next day’s posting window automatically. They don’t fail — they wait.

​

Warm-up mode

Accounts under 50 followers, or in their first 14 days of activity, are automatically placed in warm-up mode. Lower caps reduce the risk of X’s spam detection flagging a fresh account that suddenly starts sending at full volume. Warm-up ends automatically once the account ages out (passes 14 days and exceeds 50 followers). No action required from you.

​

DM cap override

In Settings → DM limits, workspace owners and managers can set a custom daily DM cap if they want to send less than the default. You’ll be warned if you try to exceed the recommended ceiling, and asked to acknowledge the risk before saving.

---

​

Human-like pacing

When you click Send DMs in a campaign, Outpulse doesn’t fire all the DMs at once. Each lead gets a scheduledAt timestamp with a randomized human-like delay added on top of the previous one. The queue worker picks each row up only when its time arrives. The result is that a 50-DM batch is spread across hours, not seconds, and looks indistinguishable from a person clicking through their inbox.

---

​

Posting schedule

Each connected account has a posting schedule (start hour, end hour, active days, timezone). Outside of that window, queued sends wait. Default schedule: Monday–Friday, 9 AM – 6 PM in the account’s timezone. → Posting schedule settings

---

​

What gets enforced on every send

Every DM passes these checks before going out:

1. Schedule check — within your active posting window?
2. Daily cap check — under the per-account DM cap for today?
3. Account health — is the connected account active and not paused?
4. Per-message delay — has the scheduled time arrived?

If any check fails, the send is deferred (not failed). Failed status is reserved for hard errors like an X API rejection or a revoked token.

---

​

Compliance