Platform How-To
Landing Pages for ARCs That Reduce Support Tickets
The fields, FAQ, and file notes that stop repeat emails. Make the page answer the phone questions before they arrive.
An ARC landing page is a set of answers arranged so a reader can claim a book without writing to you first. Every paragraph that is about your feelings, your launch goals, or your other books is a paragraph that pushes those answers down the screen. The reader is on a phone. They are deciding whether this file is for them and whether the download will work. If the page makes them ask you, the page is unfinished.
Support mail is not a sign of a devoted audience. A pile of "where is the file" and "what format is this" means the page failed in public. You can prevent most of that mail with fields, a short FAQ, and file notes written in the same words you would use in a reply. The campaign around the page is in How to run an ARC campaign. This page is the page itself.
What does the reader need to see without scrolling?
The top of the page should settle the decision.
- Title and author, matching the cover.
- One sentence of genre and tone, including the content a mismatched reader needs. "Cozy mystery, no on-page violence, the cat is never in danger" is more useful than "a twisty tale of secrets."
- The format: EPUB, PDF, or both, and which one you recommend for reading on a phone.
- The window: when new claims close, in a date, not "soon."
- The ask: a review is welcome, optional, and unpaid. Link the honest review policy instead of pasting the whole policy here.
- The claim action: an email field and a button that says what happens next. "Email me the EPUB" is clearer than "Submit."
Put the cover where it can be seen, but do not let a giant cover push the format and the date below the fold. A beautiful cover with no file type is how you get "I thought this was a paperback" emails.
If the book is mid-series, say so in the first screen. "This is book three. It spoils the ending of book one." That sentence prevents a kind of ticket that is really a bad review in disguise. Series starters as a free front door are a different product, discussed in Series starters as magnets. An ARC of book three is not a magnet for strangers unless you are honest about the spoilers.
Which fields are worth asking for?
Ask for the email address you will use to deliver the file and to send the few campaign notes. Ask for a name if you will use it. Do not ask for a mailing address, a phone number, a favorite trope survey, or a social handle. Each extra field is a reason to abandon the form, and none of them help the file open.
If you offer two formats, a single choice of "EPUB or PDF" can cut the wrong-file tickets in half. Default to EPUB for a novel. Explain the choice in a line under the control: "EPUB lets you resize the type. PDF keeps the print layout." The work of making those files is in Formatting EPUB ARC files. The page should not offer a format you do not actually have.
Do not ask people to agree to a star rating in a checkbox. A checkbox that says "I will leave an honest review" sounds polite and functions as pressure. The policy says the review is optional. The form should not quietly un-say it. ARC compliance is the short public version of why that pressure is a bad trade.
If you need to know whether someone has read the earlier books, ask in the blurb, not in a required dropdown. A required dropdown that says "I have read the entire series" will be answered by people who have not, because they want the file. You will have collected a lie and still not prevented the spoiler complaint. Better to warn them and let them choose.
What FAQ actually prevents mail?
Write the questions you have already answered twice. If this is your first campaign, write the questions you would ask if you were tired. Five is enough. Twelve is a second website nobody will open.
When does this close? Repeat the date. Say whether the download still works after claims close, if that is true. People begin books late.
What if I don't finish? Say they owe you nothing. Say it in the FAQ even though it is also in the policy. This is the question polite people are afraid to ask, so they ask you by email instead.
What if the file will not open? Give one step, then a person. "Try the EPUB in the reading app you already use. If it is still blank, email support with the device and a screenshot." Link ARC support when the campaign is on ReaderMagnet. Do not attach a twelve-step Kindle manual. The people who need the manual will not follow twelve steps, and the people who do not need it will think the file is fragile.
Which version is this? If you replaced the file, say "Updated on October 6. If you downloaded before that and the old file was broken, use the link again." Silence here creates a ticket per reader.
Where should a review go, if I want to leave one? Name the stores and use the review links tool so the URLs are the real book and not a search page. Say the review is optional in the same answer. Do not bold the word optional and then write three sentences about how much reviews matter. The reader can count.
Is this the full book? Answer yes or no. A "full book" that ends on a cliffhanger with "continued next year" will generate angry mail. If it is a novella, say novella and give a word count or a page count you measured.
Skip the FAQ about your writing playlist, your pets, and your publication history. That is bio. Bio can be one line under the title. It does not answer a ticket.
How should the page sound when someone is annoyed?
Write the file-help sentence as if the reader is already annoyed, because the people who need it are. Short words. No jokes about technology. No "oops, bookworms and their gadgets!" A person who cannot read the file is not in on the joke.
Avoid countdown language unless a real date is attached and you will honor it. "Only a few copies left" on a digital file is not true. Digital files do not run out. False scarcity trains people to distrust the rest of the page, including the format notes.
Avoid a pop-up that asks them to join a newsletter before they have the file. They just gave you an email to get the file. A second ask is how the claim feels like a funnel. If you want them on the ongoing list, say that the campaign notes are separate and they can leave after the book. The design of those notes is in Building an author newsletter welcome flow.
What should you test before you send the link to anyone?
Open the page on a phone, on the connection you have in a hallway, not only on the laptop where you built it. Confirm:
- The title is the book's title.
- The cover is the cover you are publishing, not last month's draft.
- The button works and the confirmation tells them what to check, including spam.
- The file that arrives is the file you tested, in the format the page named.
- The date, the optional-review sentence, and the support link are visible without hunting.
- The page still makes sense if you have never heard of your series.
Ask one person who is not an author to claim a test copy and to tell you where they hesitated. Do not narrate the page to them. Their hesitation is the sentence you should move up.
Then read the page next to the delivery email. If the email contradicts the date or the format, fix the email. The sequence is in ARC email sequences that don't nag. A careful page with a sloppy delivery note still creates tickets. The ticket will quote the note, not your intentions.
How do you keep the page from rotting after launch day?
The page rots when the campaign ends in your head and stays open on the internet. Close new claims when you said you would. If the download remains available for people who already claimed, say that. If it does not, take the link down and leave a sentence: "This advance copy is closed. The book is on sale here." A dead button is a ticket.
When you update the manuscript, update the note on the page the same day. When you change the cover, change the image. When you change the genre description because early readers misunderstood the tone, change the first screen. The page is an instruction sheet. Instruction sheets that drift become fiction, and then the mail starts again.
If you are hosting the campaign on ReaderMagnet, list your book with the title and the file you mean. Open beta does not ask for a card until January 1, 2027. The page still needs your sentences. The software will not invent a clear warning about book three.
What a quieter inbox looks like
You will still get some mail. A device you have never heard of will fail. Someone will ask a question the FAQ answers. Reply once, with the FAQ's sentence, and then consider whether that sentence was actually visible. If three people miss it, it was not visible. Move it up. Do not add a second paragraph that repeats it in a warmer voice. Move the original.
The page is done when a stranger can tell what the book is, how long the window lasts, what file they will get, that a review is not the rent, and where to write if the file is blank. Everything else can wait until they have read the book. That is the courtesy. The courtesy is also the support strategy.
What should the confirmation say after the button, and what should it never say?
The moment after the click is when a lot of tickets are born. The reader is staring at a confirmation and wondering whether they did it right. The confirmation should say three things: the book title, where the file will appear, and what to do if it does not appear within a few minutes. "Check the promotions tab, then write to us with your device" is a complete instruction. "You're in! Watch your inbox for a surprise" is how people write to ask what the surprise was supposed to be.
Repeat the format in the confirmation. If they chose PDF, the confirmation should say PDF. A generic "your book is on the way" restart the confusion the form just solved. Use the same support address as the page. A confirmation that points at a different inbox splits the mail and makes you look like you lost them.
Do not use the confirmation to introduce a new offer. No second magnet, no swap signup, no "while you wait, follow these accounts." They are waiting for a file. The only extra line worth adding is the close date, so they know the favor has a boundary. If the mail is delayed because a tool is slow, say the delay on the page before they click, not in an apology after they have already started to worry.
Keep a test claim on the page the day you invite anyone. If the confirmation you see is an old campaign's text, you duplicated a page and forgot the title. That single mistake produces a thread of "you sent me the wrong book." Fix it before the invite goes out. The invite is in ARC email sequences that don't nag. It should describe the same title the confirmation just showed you.
How do you handle a page that serves more than one edition?
Sometimes the ARC is a paperback proofreader's PDF and an EPUB of the same text, and sometimes an audiobook is not ready and people will ask anyway. The page should list only the editions you can deliver this week. If audio is coming later, do not put a grayed-out button on the form. A dead choice becomes "the audio link is broken" mail. Say "EPUB and PDF only for this window" in the first screen so the absence is a decision, not a defect.
If a retailer edition and the ARC differ by a note, a map, or a corrected name, say which file the reader is holding. "This advance file is the text we intend to publish, minus a map that will be in the print edition" is a specific sentence. It prevents a review that complains about a missing map you never promised them. It also prevents you from "fixing" the ARC three times as the map arrives. Freeze the file. Describe it. Let the print edition be the print edition.
When two editions exist, pick a default in the confirmation email so a reader who ignores the form still gets a readable novel. Then offer the other format in one line they can reply to. Reply-based swaps are more work for you and less work for the dozens of people who were happy with the default. That trade is correct. The page is supposed to reduce tickets, not to demonstrate that you can build a format menu.