ReaderMagnet

How-To Guides

ARC Email Sequences That Don't Nag

October 5, 2026 · By ReaderMagnet Editorial Desk

How-To Guides indie authors reader magnets

A short ARC sequence: invite, deliver, mid-window help, close. What to say, when to stay quiet, and how to keep reviews optional and honest.

An ARC email sequence has four jobs: invite the right people, deliver a file that opens, help the ones who are stuck, and close the window. It does not have a fifth job called "extract a review from anyone who has gone quiet." Silence is often a life, not a verdict. The sequence that respects that fact is shorter than the one most authors draft at midnight before a launch.

Reviews stay optional. That is not a tone preference. It is how you keep the ask legal and how you keep your storefront accounts out of trouble. The public version of that rule is on ReaderMagnet's honest review policy. If you want language you can paste onto your own site, use An honest review policy you can publish and then edit it until it sounds like you.

Who is this sequence for, and who should not automate it?

Use a sequence when you are inviting more people than you can personally write to, and when those people already expect a book. Twenty newsletter readers who asked for the next ARC can get four plain emails. A street team that lives in a chat does not need a marketing automation clone of the same chat. A list you bought needs to be deleted, not sequenced.

Skip the sequence entirely if the book is not finished. Emails about a file you cannot send yet are how you spend trust before you have a file. Also skip it if you cannot answer a reply for two weeks. Automation that invites people into a room you will not staff is worse than a short personal note to twelve readers.

The campaign around these emails is described in How to run an ARC campaign. This page is only the mail. The page they land on is a separate problem, covered in Landing pages for ARCs that reduce support.

What does the invite say, and what does it refuse to say?

The invite goes to people who can still say no. Send it before the file, not as a surprise attachment.

Say what the book is, how long it is in pages or words you actually counted, when the window closes, and that a review is welcome and not required. Name the genre the way a reader would, including the parts that cause returns: on-page violence, explicit sex, a bleak ending, heavy faith content, or a cliffhanger if the book is mid-series.

A usable invite looks like this. It is an example, not a script you must copy:

"I'm sending advance copies of North Ferry on Monday. It's a 320-page coastal mystery. The window runs four weeks. If you want the EPUB, reply or use the claim page. A review is optional. If you don't finish, you don't owe me anything. If you know you hate books where the dog is in danger, skip this one. The dog is fine, but the book spends time making you worry."

Do not say "in exchange for a review." Do not say "I need twenty reviews by Friday." Do not offer a second book, a gift card, or a shout-out for a star rating. Those sentences turn a favor into a transaction. Amazon's own review guidance, and ReaderMagnet's ARC compliance notes, are there because storefronts treat required praise as manipulation. You do not need a lawyer to avoid the obvious version. You do need to read the current retailer page before you invent a cleverer version.

Also say how to get out. One line: "If you don't want ARC mail, say so and I won't offer the next one." People who decline are doing you a favor. They will not clutter your "maybe" pile.

What belongs in the delivery email, and what can wait?

Send the delivery note when the file is actually available. If the claim page generates the message, read it before you open the campaign. A default that buries the download under your biography will create tickets.

The delivery email needs:

  • The download, once, in the format you promised.
  • The title and the date the window closes.
  • The review links, labeled optional, for the stores you actually care about. The review links tool is a place to gather those URLs so you are not hunting them on launch morning.
  • A support line: what to do if the file will not open, and where to write. ARC support is the public door for ReaderMagnet readers. If you are delivering from somewhere else, name that inbox.
  • Nothing else that competes with the file. No newsletter signup pitch to people who just signed up. No request to follow you on three networks. No excerpt. They have the book.

Subject lines should look like mail from a person who has their file. "Your copy of North Ferry" is enough. "Last chance" is a lie on day one. "I can't wait for you to love this" asks for a feeling they have not had.

Wait a week before you write again, longer if the book is long. The reader has not failed you by having a job.

What is the mid-window note allowed to do?

One note, in the middle, not a drip of three. The purpose is help, not guilt.

Thank the people who already posted, without quoting their stars in a way that tells everyone else which rating you prefer. Offer a format swap if you have one: "If the EPUB is a mess on your device, I can send the PDF." Remind them of the close date. Repeat that a review is optional.

You may ask a question that a stuck reader can answer in one line: "If the file failed, tell me the device." You may not ask "Why haven't you reviewed yet?" That question has no good reply. The honest answers are "I haven't started," "I hated it," and "My parent is in the hospital." You do not want any of those answers produced for your benefit.

If you segment, segment on behavior you actually have. People who already clicked a review link do not need the mid-window ask. People who reported a broken file need the fix, not the ask. If you cannot segment, write the note so both groups can read it without feeling scolded. "If you already posted, thank you, you can ignore the links" is plain and sufficient.

Do not add a "behind the scenes" essay in this email. They are in the middle of the book. Your process is not the help they need.

How do you close without a guilt sequence?

The close email happens when you said it would. Send it even if you are disappointed. Moving the date because you want more reviews teaches people that your deadlines are a negotiation.

Say the window for new claims is shut. Say existing download links still work if that is true, so a slow reader is not punished. Repeat the review links once, still optional. Thank them for reading or for trying. Then stop.

A fourth email "just bumping this" is the nag. A fifth email with a sad story about the algorithm is how you lose the list for book two. If the numbers are thin, the remedy is the next book's invite list and the book's fit, not another reminder. How to run an ARC campaign covers what to do when nobody posts. The short version is: count finishes if you can see them, check whether the window matched the length of the book, and do not send a scolding.

If a reader replies to the close with a late review, thank them and do not enroll them in a new sequence as a reward. If they reply with a problem in the book, fix the problem if it is real, and do not ask them to edit the review.

What should you automate, and what should stay a human reply?

Automate the parts that are the same for everyone and boring to mistype: the delivery link, the close date, the optional-review sentence, the support address. Do not automate empathy. If someone writes "this file is blank" or "I lost my spouse this month," that reply is yours. A sequence that answers those with the next scheduled pitch is the fastest way to be marked as spam.

Keep the automation short enough that you can read all four emails in one sitting every time you duplicate the campaign for a new book. If you cannot bear to read them, the readers cannot either.

Turn the sequence off when the campaign ends. Evergreen "ARC reminder" flows attached to a dead book are how old links keep creating mail. On ReaderMagnet, close the campaign when you close the window. If you also run a welcome flow for magnet readers, keep it on a different list or a different tag so ARC readers are not congratulated for joining a newsletter they did not choose. The welcome flow is a separate design: Building an author newsletter welcome flow.

How do you write about stars without coaching the review?

You can tell readers where a review can go. You can tell them it should be honest. You can tell them a free copy is worth disclosing in the review if the store asks for that. You cannot tell them the rating you need, the phrases you prefer, or the sentences to avoid because they might hurt the launch.

If you are afraid of a two-star review, the sequence is not the place to manage that fear. Do not send a "tips for reviewing" guide that is secretly a list of compliments. Readers notice. So do the stores.

A clean paragraph:

"If you finish and want to post, here are the links. Say what you thought, including what didn't work. You don't owe a positive review for the free copy. If you'd rather not post, that's fine."

That paragraph can appear in the delivery and again in the close. It should not grow.

What timing fits the book in front of you?

Match the gaps to the length, not to your anxiety.

  • A novella can use an invite, a delivery the same week, one note a week later, and a close inside two weeks.
  • A 80,000-word novel wants a week of quiet after delivery before the mid-window note, and a close at four to six weeks.
  • A long fantasy wants the longer window you already promised in the invite. Do not "check in" every Sunday because the book is long. The length is why you gave them time, not why you get more emails.

Send on a day you can answer replies. Monday morning mail that sits until Thursday is a sequence that looks automated and unhelpful. If you write at night, schedule the send for the hour you will be awake the next day.

Time zones matter less than you think for a four-email arc. They matter a lot if you promise "the file arrives at 9 a.m." and then deliver at 9 a.m. on a coast the reader is not on. Promise the day, not the minute.

How do you keep the sequence from drifting into your newsletter voice?

ARC mail is logistical. Newsletter mail can be warmer, longer, and about the work. When you mix them, the ARC note becomes a story about your week, and the download link sinks. Write ARC mail in short paragraphs. Use the book's title in the subject. Avoid a personal essay until the campaign is over and you are writing to the people who asked to stay.

If you want to tell the story of the research, do it after publication, to the list that asked for author notes. The readers holding an unfinished file need the file.

Read the sequence once as if you did not know the sender. If any email would embarrass you when forwarded to another author, cut that sentence. The usual candidates are the apology for "bothering you again," the claim that the book will change their life, and the hint that future ARCs depend on a five-star review. Delete all three.

Then send the four notes, answer the humans, and go back to the next book. The sequence worked if the right people got a clean file and nobody was chased. The reviews, if they come, are a side effect of that, not a quota the emails were built to collect.