Communications
Orchestration (Beta)
BetaBeta Feature
Orchestration is currently in Beta. Features and behavior may change between releases. Enable it from the /beta opt-in page. Feedback is welcome — use the feedback button in the Orchestration panel.
Orchestration is a governed send-scheduling layer that sits on top of the individual sends you already schedule (Manual, Scheduled, Recurring, and registration-triggered). Rather than a workflow builder, it prioritizes, deduplicates, and caps sends across your whole portfolio so recipients aren't over-mailed when several scheduled sends would otherwise land on the same people at once.
Core Concepts
| Concept | Definition |
|---|---|
| Priority tier | An integer assigned by source type — transactional sends default to priority 100, event-driven sends to 80 — used to resolve conflicts, not a per-workflow setting |
| Comms class | A logical communication category (e.g. 'event_reminder') used for conflict detection and deduplication between scheduled jobs |
| Overlap / conflict | Two scheduled send jobs that target an overlapping set of recipients around the same time; recorded with an estimated recipient-overlap count and a resolution of deferred, cancelled, allowed, or pending |
| Send slot | A capacity allocation used to spread large sends and enforce daily caps |
Governance Settings
Configured per tenant under the Orchestration settings panel:
| Setting | What it controls |
|---|---|
| Daily cap (per channel) | Maximum sends per day for email, SMS, and push independently |
| Max sends per recipient per day | Caps how many communications a single recipient can receive across all channels in a day |
| Quiet hours | A start/end time window during which non-urgent sends are held rather than delivered; both must be set together or left both unset |
| Priority rules | The priority integer applied to transactional vs. event-driven sends when an overlap is detected |
Overlap Detection
Before a scheduled send job runs, Forge checks whether another scheduled job for the same tenant targets an overlapping set of recipients around the same time. Detected overlaps are recorded with an estimated recipient-overlap count and can be resolved as deferred, cancelled, or explicitly allowed.
Calendar, Queue, and Report Views
- Calendar — a portfolio-wide view of every scheduled send across all events, for spotting clustering before it becomes an overlap
- Queue — the list of pending send jobs with their priority, comms class, and any detected conflicts
- Report — historical send volume and conflict-resolution outcomes over time
Governance only applies to marketing steps
Daily caps, quiet hours, and overlap detection apply to scheduled and recurring sends. Registration-triggered transactional emails (confirmations, cancellations, waitlist) are always delivered regardless of governance settings.