Email automation: Repli private beta

Email automation connects a real contact event to a reviewed message and a defined next step. Repli has email workspace code for templates, campaigns and sequences, but it is not a generally available email product.

Repli Email is an admin-only private beta. Creating an account or upgrading a plan does not unlock email sending. No public email allowance, price or launch date is offered here.

What exists in the private beta

The workspace includes saved templates, email contacts, campaign audiences and per-contact automation runs. Sequence actions include a delay, a saved-template send, a contact-field or tag condition, tag changes and an exit. These are configurable building blocks, not preinstalled welcome, nurture or cart-recovery recipes.

The inspected contact scanner handles new contacts, matching tags, contact-record inactivity and configured schedules. Token-based webhook and event paths are separate. A trigger label in a menu does not establish a connected signup form, commerce system or appointment calendar. Confirm the actual event source before treating a workflow as ready.

Mailbox connection is not automation delivery

A connected mailbox, an automation sender and application notification email are different systems. The inspected automation pipeline checks a verified sender/domain and routes queued mail through its sending pipeline; mailbox connection code is not proof that every campaign uses Gmail, Outlook or Zoho.

Queue acceptance is not delivery, and delivery is not inbox placement. Live provider configuration, active schedules and a received email have not been demonstrated by this page review. Do not rely on the older claim that connecting a business mailbox enables every sequence.

Define permission and the stopping rule

The email send path checks marketing consent, unsubscribes and suppression as well as sender eligibility and sending capacity. Collect the purpose and permission for email separately from permission to answer a chat message. A contact record alone is not authorization for a campaign.

Tag and contact-data conditions need current source data. They do not establish universal stop-on-reply, open, click or purchase behavior. For a supported production product, review the existing Instagram or WhatsApp pages; this beta review is not an email checkout offer.

Illustrative planning example

Event

An authorized form creates the correct email contact and records permission.

Sequence

A reviewed template, chosen delay and explicit contact-field condition define the next action.

Result

Read the send result separately from delivery or the customer’s response; do not infer success from enrollment.

Review checklist

Confirm access

Email is restricted to beta administrators, not unlocked by a paid plan.

Trace the source

Identify the real contact/event path, sender, template and consent record.

Verify operation

An authorized delivery and read-back check is required before relying on a configured workflow.

Frequently asked questions

Can I buy Repli Email today?

Repli Email is an admin-only private beta. Creating an account or upgrading a plan does not unlock email sending. No public email allowance, price or launch date is offered here.

Does connecting Gmail enable automated campaigns?

Not by itself. Mailbox connection and the inspected automation delivery pipeline are distinct. Current provider configuration and delivery must be verified separately.