Create campaigns, use email steps in visual automations and send transactional messages through the API.
Solutions
One audience. More ways to reach them.
Email is available today. SMS, RCS and WhatsApp describe the planned direction of the platform and are not presented as current capabilities.
SMS
SMS
PlannedIntended for short, time-sensitive messages. SMS sending is not currently available in the public product.
RCS
PlannedIntended for richer mobile messages with media and actions. RCS sending is not currently available.
Intended for approved business messaging. WhatsApp sending is not currently available.
Available now
Email is the working channel.
The current product supports email across campaigns, automations and application-triggered messages. These are the channel capabilities a customer can evaluate today.
Campaigns
Choose an audience, template, sender and schedule, then review the campaign plan before sending.
Automation messages
Select a saved template and sender for each email node inside the visual automation builder.
Transactional API
Send receipts, account notices and other application-triggered email through the supported API workflow.
One template system
Use the same responsive builder, media library, brand settings and preview workflow across reusable email content.
Audience context
Use lists and saved segments in campaigns and as supported entry points or conditions in automations.
Email reporting
Review sent, opened, clicked and unsubscribe activity for campaigns. Tracking results depend on recipient client behavior.
Planned channels
Planned is a status, not a launch announcement.
The labels on this page are intentionally conservative. They separate product direction from something a customer can buy and use now.
No implied release date
Planned identifies direction, not a published launch date or a promise that a channel ships in a particular order.
Not selectable today
SMS, RCS and WhatsApp should not be treated as available campaign or automation actions until their status changes.
No pricing assumption
Channel pricing, regional coverage and provider requirements will be stated when the implementation is ready.
Consent stays channel-specific
Permission to email does not automatically become permission for SMS, RCS or WhatsApp. Future workflows must preserve that distinction.
The product direction
Keep customer context together without pretending every channel is the same.
The intended model is a shared customer record and automation structure with channel-specific message content, consent and reporting. Today, the executable path below ends with email.
Audience event→Wait or condition→Email→Future channel, once released
Use the channel that exists today.
Build the audience, template and automation around email now. Future channels will be described as available only when they can be configured and sent from the product.
Monthly or annual billing · cancel anytime · no long-term contract