How Repli email works: verify a sending domain, build a template, send a campaign or automation to consenting contacts, and read sends, bounces and unsubscribes.
Add the DNS records Repli shows you at your domain provider. Repli checks them before your domain can send.
Choose the address on your verified domain that emails come from. Connecting your own mailbox is still being built.
Write it yourself or ask AI for a draft. An AI draft is only used after you review and accept it, and it uses AI credit.
Pick a one-time campaign audience, or an automation trigger with its steps.
Suppressed, unsubscribed and non-consenting contacts are skipped before anything is sent.
Emails go out from a queue at a steady pace. Sends, bounces, complaints and unsubscribes are recorded.
Everyone in the chosen audience who is allowed to receive it.
Something happens to a contact: new lead, signup, tag added, inactivity, a schedule, a webhook, or a store or payment event.
Repli shows signing (DKIM) and SPF records, then checks them.
Automations cannot be switched on until a domain and sender address are verified.
Still being built. Sending and receiving through a connected mailbox has not been fully tested, so use a verified domain for now.
AI drafts use AI credit. You can send yourself a test first.
Repli removes unsubscribed, suppressed and non-consenting contacts before sending.
Marketing emails need recorded consent. Audiences are lists, not automatic filters.
New lead, signup, a tag added, a schedule, a webhook, or a store or payment event.
Needs at least one send step. Contacts already enrolled, unsubscribed or suppressed are skipped. Older contacts are not added when you switch it on.
Repli retries temporary failures up to 3 times with growing waits. Emails over your limit wait instead of being dropped.
A per-minute workspace limit applies, and new senders start with lower daily limits.
Unsubscribed contacts are skipped for everything except your own tests.
Repli records sends, opens, bounces, complaints and unsubscribes.
Link clicks are not tracked yet. Opens are approximate, because many mail apps block tracking.
No. Verifying your domain or mailbox only lets Repli send as you. You still need each contact’s permission. Marketing emails are only sent to contacts with recorded marketing consent.
Not fully yet. Zoho Mail and IMAP/SMTP mailbox connection is being built, but sending and receiving through it has not been fully tested. Today, emails send from an address on your verified domain.
Repli shows the exact records for your domain: signing (DKIM) records and an SPF record. Sending from the domain starts once Repli confirms they are in place.
Every email can carry an unsubscribe link. Once a contact unsubscribes, Repli stops sending them campaign and automation emails. Bounced and complaining addresses are also added to a suppression list.
No. Lead and signup automations only include contacts added after the automation is switched on.
No. Mailbox providers decide where an email lands. Verified records and clean lists help, but there is no guarantee of delivery, opens or sales.
Email is currently in private beta and not open to all accounts yet.
What each email feature does today, what starts it and what limits apply. Email is in private beta.
You verify the domain you send from, write a template, and choose a one-time audience or an automation trigger. Before each email goes out, Repli checks the contact can receive it. Then it sends from a queue and records what happens.
A domain you control, with Repli’s DNS records added and confirmed.
Contacts who agreed to receive your emails. Marketing emails need recorded consent.
Bounced or complaining addresses go on a suppression list and are skipped.
Each workspace sends at a steady pace, and new senders start with lower daily limits. Emails over the limit wait in the queue. They are not dropped.
Illustration only. Fictional studio and contact, not real results.
1. A yoga studio switches on a “new lead” automation for contacts tagged
2. Neha (fictional) signs up for a free class and agrees to receive emails. She is added with the trial tag.
3. Step 1 sends a welcome email right away. Step 2 waits two days, then sends a class timetable.
4. Neha clicks unsubscribe after the first email. The second email is skipped.