Open Email and choose Templates, Campaigns, or Senders. The Inbox keeps your existing conversations. Templates and workflows extend your sheets: select the records and views you already use instead of maintaining another contact list.
Build a reusable design#
- Choose New template and start with a layout or a blank canvas. Add headings, text, buttons, images, columns, dividers, a footer, or a record table. Drag to arrange blocks, or use the keyboard move controls.
- Choose a sheet in Data and map fields using stable field identities. Add conditional sections when the content depends on a record value.
- Preview a real record, then check desktop, phone, dark appearance, and plain text. Missing values stay visible before sending.
- Ask Ralti to create or refine an editable layout. Review the proposed content before applying it. AI does not publish or send the message.
- Save a version, then publish it when ready. Existing campaign recipients retain the exact saved version and compiled content.
Set up sending inside Ralti#
Open Senders → Set up sending. Choose service messages or consent-based campaigns, then use a connected Gmail, Microsoft or supported inbox, or set up a dedicated campaign sender. The designer, personalization, sheet audiences, review, scheduling and workflow blocks stay the same; actual sending limits and delivery evidence depend on the provider.
- For a connected inbox, connect the account through Ralti’s normal account journey and select its sender. Ralti shows the sending and event capabilities actually available.
- For a managed campaign sender, enter your name, a from address on a domain you own, an optional reply-to address and sensible limits. No separate provider account or API key is required in the ordinary setup.
- Add the exact DNS records Ralti displays at your domain host, then check again. Keep existing inbox mail records intact. You can save progress and return while verification finishes.
- Send one verification message to your signed-in address through Ralti’s normal queue. Finish when the provider has accepted it and the sender is ready. A successful test does not prove inbox placement.
- If setup began from a campaign, return to the same unsent draft. One managed sender identity is supported per sending domain; use a dedicated subdomain when appropriate.
Managed delivery-event handling is configured by Ralti. If you bring your own provider account, Advanced connection keeps encrypted credentials and event setup available. Domain availability, workspace allowance and shared platform allowance are checked before sending; a capacity limit preserves your work rather than upgrading a plan.
Prepare a campaign from a sheet or view#
- Choose a published template version, ready sender, and actual marketing or transactional purpose.
- Select a sheet, optional view, recipient email field, and name field. Preview recipients, missing data, duplicates, and permission exclusions. Marketing sends require recorded subscription permission.
- Review the frozen audience and compiled messages. Approve sending now or schedule a time. A later sheet edit does not silently rewrite an approved campaign.
- Optionally compare two to four published variants. Recipients receive a deterministic assigned variant; results show actual observed events without inventing a winner.
- Cancel pending work or pause the sender when needed. Messages already accepted by a provider cannot be recalled.
Use the same blocks in workflows#
The existing Workflow builder includes Send email, Wait for email reply or event, verified email-event starts, and Update email permission. Bind record fields, use an authorized finalized document version as a PDF attachment, branch on an outcome, and update your sheet. A workflow can default to human review or use an explicitly authorized automatic policy. Template publishing and automatic sending permission are separate choices.
Reply waits persist between worker runs and have a visible timeout branch. Delivery events are durably recorded and deduplicated before starting workflows. Saved causal history prevents a chain from repeatedly triggering the same email workflow.
Read the result accurately#
| Status | What it means |
|---|---|
| Queued | Approved and waiting for dispatch; cancellation and current permissions are still checked. |
| Accepted | The sending provider accepted the submission. This is not proof it reached the inbox. |
| Delivered | Verified provider evidence reports delivery to the receiving system. It does not prove a person read it. |
| Unknown | A send may have succeeded. Inspect provider evidence before retrying; mailbox sends are never blindly repeated. |
| Bounced or complained | Verified evidence has blocked further sending to the address. |
Open a record to see your associated Studio deliveries and actual events alongside the conversations you can access. A signup welcome acknowledges a request; an access invitation is a separate action and the welcome does not grant access.