Event-triggered, not schedule-triggered
Journeys fire on what actually happened: a form submitted, a stage changed, an invoice overdue, a meeting booked. A schedule sends to people whose situation has already changed; an event does not.
Safety rails as a first-class feature
Quiet hours, per-customer frequency caps, and an immediate stop when a customer replies. A messaging policy is enforced centrally rather than remembered per campaign.
WhatsApp through your own BSP
Provider-agnostic: connect the WhatsApp Business provider you already use. Templates are synced and their approval status is visible before a journey goes live.
