Batch programs
A batch program groups recipients into planned drops. It is often easier to forecast materials, proof versions, combine quantities, and build fixed production and postal dates.
Triggered programs
A triggered program starts from a client-defined event or condition that produces an audience file or parameters. DIS Direct can execute the approved list, production, mail sort, and IMb path. API ingestion, real-time decisioning, and guaranteed event-to-mail timing are not published capabilities.
Choose based on operations
Evaluate how frequently data is ready, whether each release reaches the 150,000-piece minimum, how art and proofs are approved, when components arrive, and which postal date can be supported.
Triggered and batch comparison
| Dimension | Batch mail | Triggered mail |
|---|---|---|
| Audience release | Planned list on a set cadence | Client-defined event or condition |
| Forecasting | Usually easier to plan materials and capacity | Depends on trigger volume and release rules |
| Approvals | Proofed before the scheduled batch | Rules and assets must be approved before releases |
| DIS Direct minimum | 150,000 pieces | 150,000 pieces |
| Tracking | IMb can track mail movement | IMb can track mail movement |
| Published integration | Approved file handoff | No public API or webhook promise |
Frequently asked
- Is triggered direct mail automatically real-time?
- No. A trigger defines why an audience is released. Actual timing still depends on data delivery, approval, quantity, materials, production, postal preparation, and entry.
- Can a list partner help define the audience?
- A mail-list partner can source a defined list from client-supplied parameters when that work is included in the program scope.
