Deliverability

Healthy mailboxes, sending done with restraint.

FluenzR sends from your own addresses and looks after them: it warms up new mailboxes, caps sending, spreads the load, checks your domain before launch and adds the unsubscribe line itself. No tool can promise the inbox, but you avoid the mistakes that cost the most.

Demo with made-up data.

Mailbox warm-up

A new mailbox gets ready before it prospects.

An address that has never written and suddenly sends dozens of emails looks like a spammer. Warm-up has mailboxes exchange warm-up emails, open them and reply, so your address builds a good reputation before your first campaign.

  • Three paces to choose from: Conservative (10 to 50 warm-up emails a day over about 20 days, for a new domain), Standard (15 to 100 over about 16 days, recommended) and Fast (30 to 200 over about 10 days, for an established mailbox).
  • Warm-up emails go out 30 minutes to 2 hours apart, get automatic replies, and any that land in spam are pulled out.
  • They stay away from your prospects: filed in a "Warmup" folder in the mailbox, and absent from your FluenzR Inbox.
  • The dot next to each mailbox turns green, "Inbox ready", when warm-up is stable, bounces stay under 3% and no spam has been reported. It turns red at 5% bounces or 3 spam reports.
  • If no warm-up email goes out any more (refused credentials, for instance), the step does not advance and a "Warm-up halted" banner says so, instead of showing a fake "day 14 of 16".
  • Warm-up is for SMTP/IMAP mailboxes (OVH, Infomaniak and others). A Gmail mailbox connected in one click is not warmed up: the app notes that it already has an established reputation.
  • Launching a campaign from a mailbox under 14 days old without active warm-up is still possible, with a warning and sends capped at 10 a day the first week, 20 the second.
Curves computed with the app’s rules.

Limits and rotation

Every mailbox has its cap, the load is shared.

Even a warm mailbox should not send in bursts. FluenzR caps each mailbox per day and per hour, spaces sends out, and shares the work among all the mailboxes you put in the campaign.

  • With no setting from you: 30 emails a day and 6 an hour per mailbox. You change them in the mailbox settings; your plan’s cap applies if it is lower.
  • A mailbox that is starting ramps up: 10 emails a day the first week of campaign sending, 20 the second, then your cap.
  • Sends are spread over the hour: at 3 an hour, an email leaves about every 20 minutes, with a bit of randomness, never three at once on the hour.
  • A contact’s first email leaves from the least busy mailbox of the day among the campaign’s. A mailbox that has to wait lets another one take over.
  • Follow-ups leave from the mailbox of the first email: the person always sees the same sender.
  • A mailbox refused by its sending server (credentials, SPF or DKIM) is disabled and drops out of the rotation. Contacts go out again within the hour from another mailbox, and a banner tells you.
Explanatory diagram, made-up data.

Domain check

Your domain is checked before the first send.

Three records prove to inboxes that the email really comes from you. SPF lists the servers allowed to send for your domain, DKIM signs your emails, DMARC tells the recipient what to do with a suspicious one. FluenzR reads them for real, with a DNS query, at launch time.

  • SPF missing or DMARC missing on the domain of a sending mailbox: the launch is refused, with what to do next. You publish the records at your domain host, then try again.
  • DKIM not found: a simple warning. FluenzR tries the usual names used by the big mail providers; if it finds none, it asks you to check with your host, without claiming you have none.
  • Consumer mail addresses (gmail.com and the like) are not checked: their DNS is not yours.
  • The same warnings show on the "To approve" screen when a campaign prepared by your AI is waiting for your go-ahead.
  • The free diagnostic on the site, no account needed, applies the same logic: the verdict is the same in the tool and on the site.
Made-up data.

Unsubscribe and sending without trace

The footer is added by the tool, never by you.

Every campaign email ends with an unsubscribe line, in the campaign’s language. FluenzR adds it by itself under your signature: you write nothing, and the AI that drafts your emails is told never to slip one into the text.

  • Standard sending: one sentence with an "unsubscribe here" link, then your postal address if you filled it in. Links in your emails go through click tracking.
  • Sending without trace, on paid plans: links left as they are, no pixel, and a single sentence without a link, "just reply stop". The mail apps’ unsubscribe header then works by email.
  • A "stop" on the first line, a subject "unsubscribe" or a clear written request ("no longer receive", "remove me from your list") unsubscribes the contact. Any other reply stops their sequence without unsubscribing them.
  • Open tracking is off by default: the French data regulator treats the pixel as a tracker that needs consent. If you turn it on, the footer mentions it and offers a way to object.
Made-up data.

Safeguards that work without you

  • A test batch of 20

    The first 20 recipients of a campaign go out alone. FluenzR waits 48 hours, measures bounces, and pauses the campaign if more than 10% bounced. You get an email.

  • Outages show up

    A disabled mailbox, a campaign with no usable mailbox or a broken reply sync appears in a banner and in the bell. Otherwise follow-ups would go to people who already replied.

  • The spam folder is watched

    Every hour, FluenzR looks in the spam folder of your Gmail mailboxes for emails from your contacts, and the home page flags any it finds.

  • Your mailboxes, not ours

    Gmail in one click, or any SMTP/IMAP mailbox, at OVH, Infomaniak or elsewhere. Credentials and tokens are encrypted. Emails leave from your addresses, in your name.

  • An honest counter

    Warm-up only advances if emails really go out. A day with no send does not count, and the "Warm-up halted" banner names the server’s last error.

  • No empty promises

    FluenzR reduces the risks, it cannot guarantee an email reaches the inbox: that also depends on your list, your copy and your domain’s reputation.

Frequently asked questions

Do I need to warm up my Gmail mailbox?

No. Warm-up is for SMTP/IMAP mailboxes. A Gmail mailbox connected in one click already has an established reputation, and the app does not warm it up. It still follows the daily and hourly caps.

How long does warm-up take?

Between 10 and 20 days depending on the pace: about 20 days in Conservative, 16 in Standard and 10 in Fast. One step is one day, and it only advances if warm-up emails actually went out.

Can I launch a campaign during warm-up?

You can, with a warning: during the first 14 days of sending, a mailbox is limited to 10 emails a day the first week and 20 the second. For better results, wait until the mailbox’s dot turns green.

What does FluenzR check on my domain?

SPF, DKIM and DMARC, with a DNS query at launch time. A missing SPF or DMARC blocks the launch and tells you what to publish; a DKIM not found among the usual names gives a warning. gmail.com addresses and the like are not checked.

Do I have to write the unsubscribe link myself?

No. FluenzR adds the line under your signature, in the campaign’s language, and the AI is told not to write one in the text. With sending without trace it is a single sentence without a link: the recipient replies "stop".

Does FluenzR guarantee my emails reach the inbox?

No, nobody can. FluenzR applies good practice and warns you when something is off, but the result also depends on your list, your copy and your domain’s reputation.

Ready to get started?

Email and LinkedIn in the same sequence, with a CRM. 14 days included to try it.

Start my 14-day trial

14 days included, no card for email; a card is requested only to connect LinkedIn, and nothing is charged before the end.